31,028
edits
Category:RoadMap: Difference between revisions
Jump to navigation
Jump to search
m
→Why 2 releases per year ? The limitation of FDKs/Mainteners ?
Tag: 2017 source edit |
Tag: 2017 source edit |
||
| Line 44: | Line 44: | ||
So what is blocking the integration of more features today is the instability that each feature merge generates, and the stabilization phase that is necessary to “digest” a Pull Request for evolution. This time and workload to stabilize integrated developments is exponential with the number of integrated PRs, thus: | So what is blocking the integration of more features today is the instability that each feature merge generates, and the stabilization phase that is necessary to “digest” a Pull Request for evolution. This time and workload to stabilize integrated developments is exponential with the number of integrated PRs, thus: | ||
*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 (so slower). | ||
*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 (so less efficient). | ||
*Or again, | *Or again, for 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 (so lower quality). | ||
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). | ||