29,033
edits
Changes
→Roadmap calendar
Line 30:
Line 30:
All new functionnality have to been push into develop branch.
All new functionnality have to been push into develop branch.
+
+= Freeze definition =
+When we make a freeze of code, it means we start the beta period. It does not means that we must not change the code. It means that we can do some thing, and we can't for some other. This is generic definition of a Freeze.
+* A freeze is done with a goal of a stable version in mind.
+* When a freeze start, all following things are still allowed:
+** Any change of code to fix bugs
+** Any change into translation (language files or adding key implementation)
+** Any change into data reference (stored into table llx_c_*. For example, update of vat rates, adding countries, ...)
+** Any change to finish works that was started before the freeze.
+** Any change into theme or looks (change into HTML to match W3C, or CSS changes)
+* The folloing things are not allowed:
+** Any change into architecture.
+** Adding or removing new external libraries.
+** Adding new features.
+
+= Maintenance definition =
+When a stable version is released, the branch become a maintenance branch. This means, a lot of things can not be done into this branch anymore. This is generic definition of a maintenance branch.
+* A maintenance branch is called x.y.* (* start to 1 and is increased for each new maintenance version).
+* Only changes to fix blocking, annoying or security bugs can be done.
+* Bugs making a new feature not available (when feature was never available) must not necessarly be fixed. It 's just a feature not yet ready into this branch, it will be available with next branch.
= List of past versions =
= List of past versions =