28,967
edits
Changes
→Maintenance definition
Line 51:
Line 51:
- Change code to fix "blocking", "annoying" or "security".+- Increasing size of a field+- Adding a performance index+- Adding or removing fields or tables is not allowed+- Adding a foreign key or unique key.+
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.
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:
* 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:
* 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.