OpenStackSRUs

Differences between revisions 5 and 6
Revision 5 as of 2016-05-05 19:16:33
Size: 2535
Editor: corey.bryant
Comment:
Revision 6 as of 2016-05-05 19:17:20
Size: 2542
Editor: corey.bryant
Comment:
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
SRUs for the UCA generally follow the [[https://wiki.ubuntu.com/StableReleaseUpdates|Ubuntu Stable Release process]]. SRUs for the UCA generally follow the [[https://wiki.ubuntu.com/StableReleaseUpdates|Ubuntu Stable Release Update process]].

Overview

This page documents the Stable Release Update process for the Ubuntu Cloud Archive.

Stable Release Updates

SRUs for the UCA generally follow the Ubuntu Stable Release Update process.

Please review the SRU process linked above. The following reiterates some key points, where more details can be found on the SRU process linked above.:

  • Users of official releases expect a high degree of stability.
  • It is critically important to treat SRUs with great caution.
  • SRUs must be accompanied by a strong rationale and present a low risk of regressions.
  • Minimizing risk tends to be well-correlated with minimizing the size of those changes. As such, the same bug may need to be fixed in different ways in stable and development releases.
  • Stable release updates will, in general, only be issued in order to fix
    • High-impact bugs (e.g. security vulnerabilities, severe regresions, loss of user data).
    • Bugs that are not high-impoact, but have an obviously safe patch.
    • New upstream microreleases (e.g. OpenStack stable point releases that group several bug fixes).

  • SRUs must have an accompanying bug with well-documented information for [Impact], [Test Case], and [Regression Potential].
  • Bugs must first be fixed in newer releases starting with the upstream release if possible before being backported to the UCA.
    • For example, a bug must be fixed in the current upstream development release (e.g. Newton) first, before being fixed in the prior stable upstream release (e.g. Mitaka), before being fixed in the prior stable upstream release (e.g. Liberty).

Getting Package Source

* Core OpenStack package repositories can be found here. The process for working with these repositories can be found here.

* For UCA packages that correspond to a supported Ubuntu release:

  • pull-lp-source <package> [release|version] (e.g. pull-lp-source python-oslo.messaging xenial)

* For UCA packages that correspond to an unsupported Ubuntu release:

  • For If the corresponding Ubuntu release has reached end of life, then the package source can be retrieved directly from the UCA staging PPA. For example, for Mitaka look here.

ServerTeam/OpenStackSRUs (last edited 2016-06-07 19:49:15 by corey.bryant)