Ubuntu Wiki

Stable Release Updates for the Ubuntu Cloud Archive

The SRU process for the Ubuntu Cloud Archive follows the same process as Ubuntu Stable Release Updates. Most of the points that are highlighted here are covered in further detail in the previous link, and are condensed and reiterated here.

SRU Expectations

• 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 must present a low risk of regression.
• Minimizing risk tends to be well-correlated with minimizing the size of the change. 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:

  • New upstream stable point releases for OpenStack core packages which group several bug fixes together.

  • High-impact bugs (e.g. security vulnerabilities, severe regressions, loss of user data).
  • Bugs that are not high-impact, but have an obviously safe patch.

• SRUs must have an accompanying bug with well-documented sections for [Impact], [Test Case], and [Regression Potential]. These sections must contain details as described in the Ubuntu Stable Release Updates procedure.

• Bugs must be fixed in the following order, when possible:

  1. Upstream in the latest OpenStack release [1]

  2. Then in the corresponding Ubuntu release [2]
  3. Then in the corresponding UCA

  4. After that, the bug can be fixed in the same order for the prior OpenStack release.

• [1] Landing a fix upstream may not be possible once the upstream branch is in critical-fix or security-fix only mode, or once it has reached EOL. See the OpenStack upstream stable branch policy, which specifies the various phases of support for stable branches, which are typically supported for 12 to 18 months. This case must be handled with extreme caution, as fixes would be released directly to the corresponding Ubuntu release without having landed upstream first.

  [2] Landing a fix in a corresponding Ubuntu release may not be possible once the Ubuntu release has reached EOL. This case must also be handled with extreme caution, as fixes would be released directly to the corresponding UCA without having first landed in the corresponding Ubuntu release, and possibly without having first landed in the upstream OpenStack release.

Getting Package Source

Depending on the package and the release, there are different ways to download the package source:

• Core OpenStack packages for Liberty+ are maintained in git on Launchpad. The process for working with these repositories is documented here.

• Core OpenStack packages prior to Liberty can be found maintained in Bazaar on Launchpad. The process for working with these branches is documented here.

• UCA packages that correspond to a supported Ubuntu release can be retrieved with the pull-lp-source tool:

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

• UCA packages that correspond to an unsupported (EOL) Ubuntu release can be retrieved from the corresponding UCA staging PPA:

  • For example, see the Mitaka staging PPA.