28,967
edits
Changes
m
→Why 2 releases per year ? The limitation of FDK ?
Line 45:
Line 45:
* If we release 2 times less often (so 1 every year), the time and efforts to “stabilize” is multiplied by 4.
* If we release 2 times less often (so 1 every year), the time and efforts to “stabilize” is multiplied by 4.
* Seen another way, for an identical result in terms of evolution in the same time, the workload for developers is multiplied by 2.
* Seen another way, for an identical result in terms of evolution in the same time, the workload for developers is multiplied by 2.
−* Or again, to an identical result in terms of evolution and an identical workload, the quality of stabilization is divided by 2 by releasing 2 times less often.
+* Or again, to an identical result in terms of evolution and an identical workload, the quality of stabilization is divided by 2 if we release 2 times less often.
Today the integration of new PRs is currently deliberately slowed down (this does not prevent Dolibarr from being one of the opensource projects with a highest pace of integrated PR), in order to be able to digest the integrated PRs. Indeed, the bottleneck is mainly in the number of contributors who “correct and stabilize” the integrated PRs. Let's recall the figures, evaluated during a former devcamp: On Dolibarr, for 1 PR of integrated evolution, you need to obtain approximately 2 PR of stabilization fix (2022 evaluation made on Odoo: 2.5, on ERPNext: 7).
Today the integration of new PRs is currently deliberately slowed down (this does not prevent Dolibarr from being one of the opensource projects with a highest pace of integrated PR), in order to be able to digest the integrated PRs. Indeed, the bottleneck is mainly in the number of contributors who “correct and stabilize” the integrated PRs. Let's recall the figures, evaluated during a former devcamp: On Dolibarr, for 1 PR of integrated evolution, you need to obtain approximately 2 PR of stabilization fix (2022 evaluation made on Odoo: 2.5, on ERPNext: 7).