28,967
edits
Changes
→Maintenance definition
Line 63:
Line 63:
** Code or performance optimizing
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 necessarily 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 necessarily be fixed. It 's just a feature not yet ready into this branch, it will be available with next branch.
* The following things are allowed:
* The following things are allowed:
+** Any change of code for performance optimizing
** Change code to fix "blocking", "annoying" or "security".
** Change code to fix "blocking", "annoying" or "security".
** Change for translation (language files only or error of key in code, not changing key into language files).
** Change for translation (language files only or error of key in code, not changing key into language files).
Line 74:
Line 75:
** Adding a foreign key or unique key.
** Adding a foreign key or unique key.
** Adding new features, even isolated components or scripts.
** Adding new features, even isolated components or scripts.
−* There is an exception: We can add backported code of version x.y+1 into a maintenance branch to prepare transition for developers of external modules, but only if code added is a complete new method or new function, 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 developers of external modules, but only if code added is a complete new method or new function, with no other change.