MicroReleaseExceptions
Differences between revisions 8 and 10 (spanning 2 versions)
Size: 1022
Comment:
|
Size: 1060
Comment: links
|
Deletions are marked like this. | Additions are marked like this. |
Line 9: | Line 9: |
* The technical board will have the responsibility to maintain and review the list of packages that are exceptions to the SRU rule, as well as approve package additions. * Changes to the exception list must be brought to the TB via email. The request is expected to include justification against the above criteria. |
* The [[TechnicalBoard|technical board]] will have the responsibility to maintain and review the list of packages that are exceptions to the SRU rule, as well as approve package additions. * Changes to the exception list must be brought to the TB via email ([email protected]). The request is expected to include justification against the above criteria. |
Line 15: | Line 15: |
* postgresql-8.1, postgresql-8.2 | * postgresql-X.Y |
This was ratified by the Tech Board on 2007-08-14.
SRU micro version update exception
Allow for an exception in SRUs to the "patch must be as small and unintrusive as possible" requirement for specific packages that meet the criteria:
- upstream supports micro-version updates to stable releases
- upstream has a sufficiently high level of regression testing for their stable releases
- regression tests are enabled in the package's build
The technical board will have the responsibility to maintain and review the list of packages that are exceptions to the SRU rule, as well as approve package additions.
Changes to the exception list must be brought to the TB via email ([email protected]). The request is expected to include justification against the above criteria.
- Changes can be approved via any single TB member
- Approved exceptions:
- firefox
- mozilla-thunderbird, thunderbird
- postgresql-X.Y
- clamav (approved on 2009-01-09)
StableReleaseUpdates/MicroReleaseExceptions (last edited 2015-09-29 16:25:28 by pitti)