|Dit artikel is nog maar gedeeltelijk vertaald. Als u mee wilt helpen met vertalen lees dan Wiki vertalen naar het Nederlands.|
The openSUSE maintenance update policy aims to establish a common understanding about what kind of bug qualifies as maintenance update and defines rules for packages to minimize the risk of breaking user systems.
- Security bugs generally qualify for an update unless the bug has very low impact or only affects unusual configurations. The security team triages security bugs and helps deciding whether it's worth an update.
- the following conditions may qualify a bug to be fixed via maintenance update
- data loss in default configuration
- data corruption in a default or common configuration
- regression introduced by a previously released update
- regression compared to a previous openSUSE version
To reduce the risk of breaking user systems, special care has to be taken when preparing a maintenance update.
- fixes should be applied as small, self-contained patches
- an update must not break existing package dependencies
- an update should not introduce new package dependencies
- an update should not introduce new (sub-)packages
In some cases it might be sensible to use the a new upstream version instead of applying a patch. For example if the fix is complicated to backport and upstream also only fixes critical bugs in new versions anyways the risk of taking the new version might be lower than producing a broken patch.
The maintenance team has to be asked to approve version updates.