Special types of SRU¶

This section is for the special types of SRU listed at Reference → Special types of SRU.

Request a package-specific non-standard process¶

This hasn’t been transferred into the new documentation yet. See https://wiki.ubuntu.com/StableReleaseUpdates#Documentation_for_Special_Cases for now.

Stage an upload¶

Follow the usual process but additionally add a block-proposed-<series> tag to at least one of the SRU bugs together with a comment explaining the reason for the staging. Staging can also be added retrospectively simply by adding the tag; this can be done at any time before an SRU is released. If you do so, please make sure that you add a bug comment that explains the reason.
Ensure that you perform SRU verification as normal as soon as the package is accepted into proposed.

Land an upload blocked by staging¶

In principle the block-proposed-<series> tag should be removed by an SRU team member when accepting a newer upload not planned for further staging. But if they overlook this, it’s appropriate for whoever notices it (SRU team, or uploader) to remove the block-proposed-<series> tag with a suitable comment when it no longer applies.

Remove a package¶

Steps for the uploader¶

If appropriate depending on the reason for the removal, ensure that the package is also removed in the development release and any releases subsequent to the release being targetted.
Construct an essentially empty package with an appropriate explanation in NEWS and a corresponding critical debconf note. Follow the pattern used previously (see the list of historical removals).
Create an SRU tracking but with an appropriate explanation.
Write to the technical board for approval.
Upload as normal

Steps for the SRU reviewer:¶

Check the above list has been performed correctly, and that the Technical Board has approved
Document in the list of historical removals.
Process the SRU as normal.