MicroReleaseExceptions

Differences between revisions 12 and 60 (spanning 48 versions)
⇤ ← Revision 12 as of 2010-11-02 15:25:13 →
Size: 1282
Editor: c-76-105-168-175
Comment: chromium
← Revision 60 as of 2015-09-29 16:25:28 → ⇥
Size: 142
Editor: pitti
Comment: obsolete page
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
'''This was ratified by the Tech Board on 2007-08-14.'''

=== SRU micro version update exception ===

 * Allow for an exception in [[StableReleaseUpdates|SRU]]s 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 [[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 (technical-board@lists.ubuntu.com). 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)
  * bzr (approved on 2010-09-21); conditions: test suite running during package build; SRU verification should run test suite in installed sytem
  * chromium-browser, chromium-codecs-ffmpeg, gyp (approved on 2010-11-02)		 /!\ This page is obsolete now. The current StableReleaseUpdates policy generally allows new upstream microreleases under certain conditions.

Warning /!\ This page is obsolete now. The current StableReleaseUpdates policy generally allows new upstream microreleases under certain conditions.

StableReleaseUpdates/MicroReleaseExceptions (last edited 2015-09-29 16:25:28 by pitti)