28,967
edits
Changes
→Maintenance definition
Line 49:
Line 49:
* 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.+
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.
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).
* 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.
+* Following things are allowed:
+- Change code to fix "blocking", "annoying" or "security".
+- Increasing size of a field
+- Adding a performance index
+* Following changes are not allowed:
+- Adding or removing fields or tables is not allowed
+- Adding a foreign key or unique key.
* There is an exception: We can add backported code of version x.y+1 into a maintenance branch to prepare transition for modules developper, but only if code added is a complete new method or new fonction, with no other change.
* There is an exception: We can add backported code of version x.y+1 into a maintenance branch to prepare transition for modules developper, but only if code added is a complete new method or new fonction, with no other change.