Skip to Content
  2. Mailing Lists
  3. Contributors
  4. Re: Status of different branches and reasoning to choose

Archives

Contributors

Re: Status of different branches and reasoning to choose

Re: Status of different branches and reasoning to choose

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 <notifications@odoo-community.org> 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).

Regards.

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe



--
Raphaël Valyi
Founder and consultant

by "Raphaël Valyi" <rvalyi@akretion.com> - 05:35 - 22 Feb 2024

1 attachments 1 attachments

2024-02-22_13-27.png

Reference

  • Status of different branches and reasoning to choose 
    Hi,

oca hosts a lot of repositories whith branches for the different 
versions of odoo (..14,16,17). What's missing for me is a big picture of 
the overall state of the different versions... Is community still most 
complete/stable on 14, 16 oder 17 (or maybe even 12)?

What version would you suggest to start with?

What's also missing for me is a good big picture on the difference in 
code/features beetween odoo enterprise, odoo open-source and oca on the 
different versions.

thx for any feedback,
Peter
    by Peter Niederlag - 01:16 - 18 Feb 2024

    3 replies 3 replies

    • Re: Status of different branches and reasoning to choose
      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 <notifications@odoo-community.org> 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).

      Regards.

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe



      --
      Raphaël Valyi
      Founder and consultant

      by "Raphaël Valyi" <rvalyi@akretion.com> - 05:35 - 22 Feb 2024

      1 attachments 1 attachments

      2024-02-22_13-27.png
    • Re: Status of different branches and reasoning to choose
      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 customer 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).

      Regards.
      by Pedro M. Baeza - 01:36 - 22 Feb 2024
    • Re: Status of different branches and reasoning to choose 
      Le 18.02.2024 13:18, Peter Niederlag a écrit :

> Hi,

> oca hosts a lot of repositories whith branches for the different

> versions of odoo (..14,16,17). What's missing for me is a big picture 

> of

> the overall state of the different versions... Is community still most

> complete/stable on 14, 16 oder 17 (or maybe even 12)?

> What version would you suggest to start with?

> What's also missing for me is a good big picture on the difference in

> code/features beetween odoo enterprise, odoo open-source and oca on the

> different versions.

Because of rigorous OCA policy, the code is allways in a very good 
state. All OCA modules are stables (some are in alpha or beta version 
but it is told in the Readme). Obviously, Odoo extend its 
functionlitiezs and some OCA modules become obsoletes -- but some of 
them are still there for various reasons (like a different workflow).

Regarding versions, I had the same questions years ago. The answer 
depends of what you really need instead of which version has more 
functionalities. First of all, Odoo tends to be more stable in pair 
versions and OCA is run by volunteers who are not allways using a recent 
version of Odoo. Some modules are also very generic because OCA members 
use them as a base for their need.

Also, you have to understand that OCA's modules are useful for both Odoo 
Enterprise and Odoo Community Edition. OCA doesn't intend to complete 
the Odoo CE, it share module or libs that are useful for integrators.

If you need a big picture, it help to browse apps.odoo.com (both free 
and paid modules) using categories to understand what is missing in 
Odoo.

Finally you allways have to wait some months before choosing an Odoo 
version because a lot of bugs are fixed during the year (for example, 
Odoo 16 has 4 "dot realases").

I will advice the Odoo 16 CE version from the OCB repository (see OCB 
faq in the corresponding wiki). A lot of modules are already migrated. 
If you need some other modules, wait a bit or choose the 14 version -- 
or better, help the migration (money, code, ...).

Hope it help
regards
---
Librement,
Xavier Brochard xavier@alternatif.org
La liberté est à l'homme ce que les ailes sont à l'oiseau
(Jean-Pierre Rosnay)
      by xavier - 03:25 - 18 Feb 2024