Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Avatar

Triple discount modules refactor and maturity levels

by
Camptocamp SA, Akim Juillerat
- 10/09/2024 19:02:01
Hello community

A few months ago, I started a big refactor of triple discount modules in v16.0 that ended up with the following PRs:

Since this is a BIG breaking change I'm wondering if these should be merged only in v17.0 instead of 16.0.

We actually have migration PRs for triple discount modules in 17.0:

My feeling is we must probably leverage the maturity levels to define what can be merged in a released version, and avoid such breaking change when the maturity level is stable/mature. But then, if there is no maturity level in manifest, as is the case here, it seems to default to Beta in readme generation. Should we consider this as a rule?

Do we then want to move forward with this refactor in 16.0 or keep it for 17.0 and eventually define a stable maturity level for 17.0?

Please let me know what do you guys think about it.

Best regards.

camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Akim Juillerat
Business solutions
Software architect
+41 62 544 03 78

Camptocamp SA
Leberngasse 21
4600 Olten
Switzerland
+41 21 619 10 10

Follow-Ups