Contributors mailing list archives

Browse archives


Re: Status of different branches and reasoning to choose

by "Raphaël Valyi" <> - 22/02/2024 17:32:41
More on this:

First about stability: as Pedro explained today there is no difference in stability between pair and odd versions. The thing is there is a resonance happening where pair versions are a bit more popular among skilled integrators and have more OCA modules. This can be observed by looking at the number of modules OCA by version in the attachment.

Usually in the 1st year after the release around 90 modules per month are migrated in the OCA and it slows down after some 3 years. For some reason, the situation with v17 isn't as good today yet the version is reputed "stable". Note that this is only "merged" modules, there are a lot more modules with a valid migration Pull Request proposition that is just not merged yet (there a lot of such PRs for v17).

I would add: you can choose a recent version both for large and small projects because small projects will need just a few modules and large ones might have money to migrate whatever is required. Mid sized projects however might be tricky if you choose a version that is too recent like version 17 today.

On Thu, Feb 22, 2024 at 9:37 AM Pedro M. Baeza <> wrote:
Good summary from Xavier. Just one clarification: the question about even versions being more stable is a myth propagated by some interested parties. You may find the same number of problems in even or odd versions (as in any software), and nowadays, they have been reduced a lot thanks to the maturity the software has. Anyway, any just released version is expected to have some of them, requiring a bit of time to get the proper coverage. But I also want to distinguish here the scope of these bugs: most of the time they are really edge cases or special use cases that are uncovered or not tested when a refactoring is done, and only after someone faces such use case, it's discovered and fixed. We are now discovering some of them in 15.0 2 years after their release with a special case with stock packages while having dozens of customers without problem because they don't use that specific flow with the packages.

You have to analyze the cust omer requirements, and see the gap between them and:

- Odoo core features in that version.
- Already migrated OCA modules to that version.

and always trying to push to the latest version if possible, as it can be considered always the best version released. Only if the gap can be covered with a lot of OCA modules that are not migrated, then you may think about putting a prior version, but I invite you to reverse the thing: dedicate a bit of budget to migrate that modules to the latest version, and you will save having a lot of features including by Odoo S. A. itself in that version (they have more than 300 developers investing their full time each year to improve the product).


Post to:

Raphaël Valyi
Founder and consultant