<a id="reference-package-specific-notes"></a>

# Package-specific notes

See also: [Explanation → Non-standard Processes → Package-specific
non-standard processes](https://documentation.ubuntu.com/project/SRU/explanation/non-standard-processes.md#explanation-package-specific-non-standard-processes)

The [Technical Board resolution on
Landscape](https://lists.ubuntu.com/archives/ubuntu-devel-announce/2009-March/000550.html)
provides a general rationale for the types of special cases that may be
approved here in future. Most exception approvals are now handled
directly by the SRU team.

To obtain a new ongoing exception such as those documented below:

1. Draft an exception page, like the ones referenced below, outlining what
   you believe should be the exception.
2. Submit it to the SRU team for approval via a PR to this repository.
   To discuss further see [Howto → Contact](https://documentation.ubuntu.com/project/SRU/howto/contact.md#howto-contact)

Note that the SRU team’s delegation from the Technical Board is limited
to accepting SRU uploads that meet the [policy criteria](#When)
above. The SRU team maintains documentation for standing exceptions here
to keep individual interpretations of the policy criteria consistent.
Departing from the policy criteria above still requires approval from
the Technical Board.

<a id="reference-sru-interest-team"></a>

# Groups of SRU interest

Many packages are commonly used in various important production environments
but as the exceptions show, some updates can be quite complex. In addition to
the tests outlined in the individual exception document we’d ask the
[SRU driver](https://documentation.ubuntu.com/project/who-makes-ubuntu/roles/SRU.md#explanation-role-expectations)
to please inform the SRU Interest Team about upcoming updates.

If defined, the package specific notes will refer to this paragraph and
to the group that shall be subscribed.

* **When**: Please do so as early as you know can predict what will be changed,
  document that in the bug and then act. No need to wait until it hits -proposed.
* **How**: Please add the referred Interest group as subscriber to the
  the related SRU bug that you are preparing.

These people/teams might do additional testing, but are not hard committed
for anything. Therefore we will not gate on their positive reply to set a
case to “verified”. But if they come back:

* with a good regression report => we expect it to be considered
* with a pass from their tests => more confidence in the proposed change

*Known constraints/imperfections:*
As of today there is no tooling yet ensuring an interested group has been added.
It - for now - only a social/policy request to the driver of the SRU.
Therefore, until this is fully automated, there might be mistakes which we can
not be too upset about - if you are, help to develop the tooling please :-)

# Defined Exceptions

## Kernel

Because of the way updates to the kernel work, it will follow a slightly
different process which is described on [KernelUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-Kernel-Updates.md#reference-exception-kernelupdates).

## Landscape

The landscape-client source package may be uploaded according to the
procedure documented in [LandscapeUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-Landscape-Updates.md#reference-exception-landscapeupdates).
See the [Technical Board resolution](https://lists.ubuntu.com/archives/ubuntu-devel-announce/2009-March/000550.html)
for details and rationale.

## Snapd

The snapd source package may be uploaded according to the procedure
documented in [SnapdUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-Snapd-Updates.md#reference-exception-snapdupdates).
Per Technical Board discussion regarding delegation of these decisions
to the SRU team, this stable release exception has been approved by
SteveLangasek for the SRU team as of 2016-05-12.

## Snapcraft

Related to the preceding snapd exception, the snapcraft source package
may be uploaded according to the procedure documented in
[SnapcraftUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-Snapcraft-Updates.md#reference-exception-snapcraftupdates).
This stable release exception has been approved by
SteveLangasek for the SRU team as of 2016-05-16.

## Ubuntu-image

Also related to snapd, the ubuntu-image package may be uploaded
according to the procedure documented in [UbuntuImageUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-UbuntuImage-Updates.md#reference-exception-ubuntuimageupdates).
This stable release exception has been approved by SteveLangasek for the SRU team as
of 2016-10-19.

## Docker.io group

The source packages docker.io, containerd, and runc may be uploaded
according to the procedure documented in [DockerUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-Docker-Updates.md#reference-exception-dockerpdates).
Per Technical Board discussion regarding delegation of these decisions to the SRU
team, this stable release exception has been approved by BrianMurray for
the SRU team as of 2016-09-20, with changes through to revision 19
further approved by RobieBasak for the SRU team on 2025-04-30.

## gce-compute-image-packages

The source package gce-compute-image-packages may be uploaded according
to the procedure documented in
[gce-compute-image-packages-Updates](https://documentation.ubuntu.com/project/SRU/reference/exception-gce-compute-image-packages-Updates.md#reference-exception-gce-compute-image-packages-updates).
Per Technical Board discussion regarding delegation of these decisions
to the SRU team, this stable release exception has been approved by
BrianMurray for the SRU team as of 2017-03-10. Further amendment to this
exception for vendored dependencies approved by LukaszZemczak for the
[SRU team as of
2023-04-11](https://lists.ubuntu.com/archives/ubuntu-release/2023-April/005606.html).

## google-compute-engine

The source package gce-compute-image-packages may be uploaded according
to the procedure documented in
[google-compute-engine-Updates](https://documentation.ubuntu.com/project/SRU/reference/exception-google-compute-engine-Updates.md#reference-exception-google-compute-engine-updates).
Per Technical Board discussion regarding delegation of these decisions
to the SRU team, this stable release exception has been approved by
SteveLangasek for the [SRU team as of
2022-09-01](https://lists.ubuntu.com/archives/ubuntu-release/2022-September/005479.html).
Further amendment to this exception for vendored dependencies approved
by LukaszZemczak for the [SRU team as of
2023-04-11](https://lists.ubuntu.com/archives/ubuntu-release/2023-April/005606.html).

## google-compute-engine-oslogin

The source package google-compute-engine-oslogin may be uploaded
according to the procedure documented in
[google-compute-engine-oslogin-Updates](https://documentation.ubuntu.com/project/SRU/reference/exception-google-compute-engine-oslogin-Updates.md#reference-exception-google-compute-engine-oslogin-updates).
Per Technical Board discussion regarding delegation of these decisions
to the SRU team, this stable release exception has been approved by
SteveLangasek for the [SRU team as of
2022-09-01](https://lists.ubuntu.com/archives/ubuntu-release/2022-September/005479.html).
Further amendment to this exception for vendored dependencies approved
by LukaszZemczak for the [SRU team as of
2023-04-11](https://lists.ubuntu.com/archives/ubuntu-release/2023-April/005606.html).

## google-guest-agent

The source package gce-compute-image-packages may be uploaded according
to the procedure documented in
[google-guest-agent-Updates](https://documentation.ubuntu.com/project/SRU/reference/exception-google-guest-agent-Updates.md#reference-exception-google-guest-agent-updates).
Per Technical Board discussion regarding delegation of these decisions
to the SRU team, this stable release exception has been approved by
SteveLangasek for the [SRU team as of
2022-09-01](https://lists.ubuntu.com/archives/ubuntu-release/2022-September/005479.html).
Further amendment to this exception for vendored dependencies approved
by LukaszZemczak for the [SRU team as of
2023-04-11](https://lists.ubuntu.com/archives/ubuntu-release/2023-April/005606.html).

## google-osconfig-agent

The source package google-osconfig-agent may be uploaded according to
the procedure documented in
[google-osconfig-agent-Updates](https://documentation.ubuntu.com/project/SRU/reference/exception-google-osconfig-agent-Updates.md#reference-exception-google-osconfig-agent-updates).
Per Technical Board discussion regarding delegation of these decisions
to the SRU team, this stable release exception has been approved by
SteveLangasek for the [SRU team as of
2022-09-01](https://lists.ubuntu.com/archives/ubuntu-release/2022-September/005479.html).
Further amendment to this exception for vendored dependencies approved
by LukaszZemczak for the [SRU team as of
2023-04-11](https://lists.ubuntu.com/archives/ubuntu-release/2023-April/005606.html).

## curtin

The source package curtin may be uploaded according to the procedure
documented in [CurtinUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-Curtin-Updates.md#reference-exception-curtinupdates).
This stable release exception has been
approved by SteveLangasek for the SRU team as of 2017-04-05.

## walinuxagent

The source package walinuxagent may be uploaded according to the
procedure documented in
[walinuxagentUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-walinuxagent-Updates.md#reference-exception-walinuxagentupdates).
This stable release exception has been approved by SteveLangasek for the
SRU team as of 2017-04-05.

## azure-proxy-agent

The source package azure-proxy-agent may be uploaded according to the
procedure documented in
[azure-proxy-agent-Updates](https://documentation.ubuntu.com/project/SRU/reference/exception-Azure-Proxy-Agent-Updates.md#reference-exception-azure-proxy-agent-updates).

## GNOME

GNOME has a microrelease exception excepting it from the normal QA
requirements of the microrelease policy, [documented here](https://documentation.ubuntu.com/project/SRU/reference/exception-GNOME-Updates.md#reference-exception-gnomeupdates).
This was [granted by the technical board on
2012-06-22](https://lists.ubuntu.com/archives/technical-board/2012-June/001327.html).

## OpenStack

OpenStack packages can be updated according to the procedures
documented in [OpenStackUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-OpenStack-Updates.md#reference-exception-openstackupdates),
which includes a list of
source packages covered by the MRE. This stable release exception has
been approved by LukaszZemczak for the SRU team as of 2017-08-07.

## Certbot

The Certbot family of packages can be updated according to the
procedures documented in [Certbot](https://documentation.ubuntu.com/project/SRU/reference/exception-Certbot-Updates.md#reference-exception-certbotupdates).
This stable release exception was
[discussed](https://lists.ubuntu.com/archives/ubuntu-release/2017-July/004176.html)
and subsequently revision 10 of that document was approved by RobieBasak
for the SRU team on 2017-08-08.

## cloud-init

The source package cloud-init may be uploaded according to the procedure
documented in [CloudinitUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-Cloudinit-Updates.md#reference-exception-cloudinitupdates).
Per Technical Board discussion regarding
delegation of these decisions to the SRU team, this stable release
exception has been approved by BrianMurray for the SRU team as of
2017-10-06 with subsequent updates approved by RobieBasak on 2020-07-15.

## DPDK

The dpdk source package can be uploaded according to the procedures
documented in [DPDK](https://documentation.ubuntu.com/project/SRU/reference/exception-DPDK-Updates.md#reference-exception-dpdkupdates) for supported LTS
releases of Ubuntu. This stable release exception has been approved by
LukaszZemczak for the SRU team as of 2017-08-07.

## ubuntu-release-upgrader and python-apt

The packages ubuntu-release-upgrader and python-apt both contain files
with listings of Ubuntu mirrors. To facilitate upgrades to new releases
ubuntu-release-upgrader should be updated (particularly for LTS
releases) so that the list of mirrors is accurate. With that in mind and
given that it is just a text file with urls for mirrors it is okay to
SRU only mirror changes for these packages without an SRU bug.

## apt and python-apt

Not a policy exception, but see [AptUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-Apt-Updates.md#reference-exception-aptupdates)
for details of unusual SRU versioning.

## rax-nova-agent

The source package rax-nova-agent may be uploaded according to the
procedure documented in
[rax-nova-agent-Updates](https://documentation.ubuntu.com/project/SRU/reference/exception-rax-nova-agent-Updates.md#reference-exception-rax-nova-agent-updates).
This stable release exception has been approved by SteveLangasek for the
SRU team as of 2018-08-15.

## livecd-rootfs

The livecd-rootfs package is a frequent target of SRUs as part of
development of changes to image builds for the target series, and is not
intended for general installation on end-user systems. The risk of
user-affecting regression is lower as a result, because the impact of
changes to this package to end users is mediated by way of image builds.
Therefore, the requirement for per-change bug reports and test cases is
relaxed, as long as there is at least one linked bug with a test case.

## fwupd and fwupdate

The source packages fwupd and fwupdate may be uploaded according to the
procedure documented in
[firmware-updates](https://documentation.ubuntu.com/project/SRU/reference/exception-firmware-updates.md#reference-exception-firmware-updates). This
stable release exception has been approved by BrianMurray for the SRU
team as of 2019-01-15.

## snapd-glib

The source package snapd-glib may be uploaded according to the procedure
documented in [snapd-glib updates](https://documentation.ubuntu.com/project/SRU/reference/exception-SnapdGlib-Updates.md#reference-exception-snapdglibupdates).
This stable release exception has been approved by BrianMurray for the
SRU team as of 2019-02-19.

## netplan.io

The source package netplan.io may be uploaded according to the procedure
documented in [netplan updates](https://documentation.ubuntu.com/project/SRU/reference/exception-Netplan-Updates.md#reference-exception-netplanupdates).
This stable release exception has been approved by BrianMurray for the
SRU team as of 2019-04-01 (no really!).

## ec2-hibinit-agent

The source package ec2-hibinit-agent may be uploaded according to the
procedure documented in [ec2-hibinit-agent updates](https://documentation.ubuntu.com/project/SRU/reference/exception-ec2-hibinit-agent-Updates.md#reference-exception-ec2-hibinit-agent-updates).
This stable release exception has been approved by SteveLangasek for the SRU
team as of 2019-09-06.

## NVIDIA driver

NVIDIA driver (source packages nvidia-graphics-drivers-\*,
nvidia-settings, fabric-manager-\*, libnvidia-nscq-\*) may be uploaded
according to the procedure documented in [NVIDIA
updates](https://documentation.ubuntu.com/project/SRU/reference/exception-NVidia-Updates.md#reference-exception-nvidiaupdates). This stable release
exception has been approved by ChrisHalseRogers for the SRU team as of
2019-09-17.

## wslu

The wslu package may be uploaded according to the procedure documented
in [wslu Updates](https://documentation.ubuntu.com/project/SRU/reference/exception-wslu-Updates.md#reference-exception-wslu-updates). This stable
release exception has been approved by LukaszZemczak for the SRU team as
of 2019-10-24.

## openjdk-N

We allow providing OpenJDK short term support releases in the updates
pocket, instead of the release pocket to be able to remove those after
their support ends as documented in [OpenJDK
Updates](https://documentation.ubuntu.com/project/SRU/reference/exception-OpenJDK-Updates.md#reference-exception-openjdk-updates). This very specific
stable release exception has been approved by LukaszZemczak for the SRU
team as of 2020-04-30.

## Postfix

The postfix source package may be uploaded according to the procedure
documented in [PostfixUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-Postfix-Updates.md#reference-exception-postfixupdates). See the [Technical Board meeting
minutes](https://lists.ubuntu.com/archives/ubuntu-devel-announce/2011-October/000902.html)
and its
[approval](https://lists.ubuntu.com/archives/technical-board/2012-May/001266.html)
for details and rationale.

## sosreport/sos

The source package sosreport/sos may be uploaded according to the
procedure documented in [sosreport
updates](https://documentation.ubuntu.com/project/SRU/reference/exception-Sosreport-Updates.md#reference-exception-sosreportupdates). This stable
release exception has been approved by LukaszZemczak for the SRU team as
of 2020-06-25. This was updated for the source package sos and [approved
by Robie
Basak](https://lists.ubuntu.com/archives/ubuntu-release/2025-February/006325.html).

## oem-\*-meta

Source packages of the form oem-\*-meta may be uploaded according to the
procedure documented in
[OEMMeta](https://documentation.ubuntu.com/project/SRU/reference/exception-OEMMeta-Updates.md#reference-exception-oemmetaupdates). This
stable release exception has been approved by AndyWhitcroft for the SRU
team as of 2021-07-15. New packages are acceptable under the same
exception.

## ubuntu-dev-tools

The source package ubuntu-dev-tools may be uploaded according to the
procedure documented in
[UbuntuDevToolsUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-UbuntuDevTools-Updates.md#reference-exception-ubuntudevtoolsupdates).
This stable release exception has been [approved by Robie
Basak](https://lists.ubuntu.com/archives/ubuntu-release/2023-May/005640.html).

## OpenLDAP

The OpenLDAP source package may be uploaded according to the procedure
documented in [OpenLDAPUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-OpenLDAP-Updates.md#reference-exception-openldapupdates).
This stable release exception [has been
approved](https://lists.ubuntu.com/archives/ubuntu-release/2022-June/005403.html)
by SteveLangasek for the SRU team as of 2022-06-02.

## HAProxy

The haproxy source package may be uploaded according to the procedure
documented in [HAProxyUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-HAProxy-Updates.md#reference-exception-haproxyupdates). This stable release
exception [has been
approved](https://lists.ubuntu.com/archives/ubuntu-release/2022-June/005417.html)
by LukaszZemczak for the SRU team as of 2022-06-27.

## Intel Graphics

The source packages for the Intel graphics stack may be uploaded according to
the procedure documented in [IntelGraphicsUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-Intel-Graphics-Updates.md#reference-exception-intel-graphics-updates).

## autopkgtest

The autopkgtest source package may be uploaded according to the
procedure documented in [autopkgtest-Updates](https://documentation.ubuntu.com/project/SRU/reference/exception-autopkgtest-Updates.md#reference-exception-autopkgtest-updates).
This stable release exception [has been
approved](https://lists.ubuntu.com/archives/ubuntu-release/2023-January/005530.html)
by SteveLangasek for the SRU team as of 2023-01-30.

## squid

The squid source package may be uploaded according to the procedure
documented in [SquidUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-Squid-Updates.md#reference-exception-squidupdates). This stable release
exception [has been
approved](https://lists.ubuntu.com/archives/ubuntu-release/2023-April/005589.html)
by SteveLangasek for the SRU team on 2023-04-03.

## bind9

The bind9 source package may be uploaded according to the procedure
documented in [Bind9Updates](https://documentation.ubuntu.com/project/SRU/reference/exception-Bind9-Updates.md#reference-exception-bind9updates). This stable release
exception [has been
approved](https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005647.html)
by SteveLangasek for the SRU team as of 2023-06-06.

## virtualbox

- - THIS IS OUTDATED !!! \*\*\*

The virtualbox source packages may be uploaded according to the
procedure documented in
[VirtualboxUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-Virtualbox-Updates.md#reference-exception-virtualboxupdates). This
stable release exception [has been
approved](https://lists.ubuntu.com/archives/technical-board/2015-November/002177.html)
by Martin Pitt for the SRU team as of 2015-11-04.

## ubuntu-advantage-tools

The ubuntu-advantage-tools source package may be uploaded according to
the SRU procedures documented in
[UbuntuAdvantageToolsUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-UbuntuAdvantageTools-Updates.md#reference-exception-ubuntuadvantagetoolsupdates). This
stable release exception [has been
approved](https://lists.ubuntu.com/archives/ubuntu-release/2023-October/005810.html)
by RobieBasak for the SRU team part as of 2023-10-04.

## open-vm-tools

The open-vm-tools source package may be uploaded according to the
procedure documented in [OpenVMToolsUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-OpenVMTools-Updates.md#reference-exception-openvmtoolsupdates).
This stable release exception [has been
approved](https://lists.ubuntu.com/archives/ubuntu-release/2024-January/005900.html)
by ChrisHalseRogers for the SRU team as of 2024-01-25.

## postgresql

The currently supported postgresql source package (as determined by the
dependency of the postgresql metapackage) for each stable release may be
uploaded according to the procedure documented in
[PostgreSQLUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-PostgreSQL-Updates.md#reference-exception-postgresqlupdates). This stable release exception
[has been
approved](https://lists.ubuntu.com/archives/ubuntu-release/2024-January/005915.html)
by ChrisHalseRogers for the SRU team as of 2024-01-31

## MariaDB and Galera

The ‘mariadb’ and ‘galera’ source packages, including source package variants
with version suffixes, may be uploaded according to the proceedure documented in
[MariaDB-Galera-Updates](https://documentation.ubuntu.com/project/SRU/reference/exception-MariaDB-Galera-Updates.md#reference-exception-mariadb-galera-updates).

## multipath-tools

The `multipath-tools` source package may be uploaded for their stable releases, as documented in [multipath-tools-Updates](https://documentation.ubuntu.com/project/SRU/reference/exception-multipath-tools-Updates.md#reference-exception-multipath-tools-updates).

## Valkey

The valkey source package may be uploaded according to the procedure
documented in [Valkey-Updates](https://documentation.ubuntu.com/project/SRU/reference/exception-Valkey-Updates.md#reference-exception-valkeyupdates).
This stable release exception [has been
approved](https://github.com/ubuntu/ubuntu-project-docs/pull/314) by
RobieBasak for the SRU team as of 2026-01-22.

## GRUB

GRUB related packages require a special SRU process due our EFI signing
pipeline, documented at
[Grub updates](https://documentation.ubuntu.com/project/SRU/reference/exception-Grub-Updates.md#reference-exception-grubupdates).

## OpenVPN

Updates including upstream OpenVPN microreleases should follow the
special case documentation at [OpenVPNUpdates](https://documentation.ubuntu.com/project/SRU/reference/exception-OpenVPN-Updates.md#reference-exception-openvpnupdates).
This is not a standing approval or policy exception, but a general pattern to
update OpenVPN upstream microreleases consistently under existing SRU
policy.

## Language Packs (language-pack-\*)

There is some documentation at:
[https://git.launchpad.net/langpack-o-matic/tree/doc/operator-guide.txt](https://git.launchpad.net/langpack-o-matic/tree/doc/operator-guide.txt)

## cd-boot-images-<arch>

These packages have a strict build-dependency on specific versions of
grub and others. It can happen that these build-dependencies are no
longer satisfied since the package was uploaded to unapproved, because
the build-dependencies were updated themselves in the meantime. While
this would just create a failure to build, it would also waste a version
number if accepted into proposed in this state, so it’s a recommendation
to check the availability of the build dependencies before accepting the
package into proposed.

For a concrete example, see
[https://bugs.launchpad.net/ubuntu/+source/cd-boot-images-riscv64/+bug/2104572/comments/9](https://bugs.launchpad.net/ubuntu/+source/cd-boot-images-riscv64/+bug/2104572/comments/9)

## Data Packages Kept in Sync with Security

Some data packages must always be kept in sync between -updates and
-security to avoid behaviour or functionality regressions when using
only the security pocket. Because they are pure data, and contain no
compiled code, these packages are safe to build in -proposed and then
copy to both -updates and -security.

## tzdata

The tzdata package is updated to reflect changes in timezones or
daylight saving policies. The verification is done by adding a test case to
debian/tests/python. One timezone that gets changed in the updated package
is checked via the added test case. If the package builds (with running the
tests) and the autopkgtest are green the verification is considered done.

| Feature     | 16.04 LTS   | 18.04 LTS   | 20.04 LTS   | 22.04 LTS and later   |
|-------------|-------------|-------------|-------------|-----------------------|
| icu-data    | No          | No          | Yes         | Yes                   |
| SystemV tzs | Yes         | Yes         | Yes         | No                    |

The version of tzdata in Ubuntu 20.04 LTS and later includes icu-data
(see the update-icu rule in debian/rules) and the verification of it can
be done by adding a test case to debian/tests/python-icu (similar to the
one in debian/tests/python). There can be a
slight lag between the tzdata release and the matching icu-data release,
we usually wait for the latter to be released before uploading the
update.

The version of tzdata in Ubuntu 20.10 removed supported for SystemV
timezones, however SRUs of tzdata to Ubuntu 20.04 LTS and earlier
releases should still include the SystemV timezones. This is tested
by test_systemv_timezones in debian/tests/python.

Because tzdata’s packaging has changed subtly from release to release,
rather than just backporting the most recent release’s source package,
we just update the upstream tarball instead. You then need to edit
debian/changelog to add bug closures, and make sure to use a version
number consistent to the previous numbering scheme (e. g.
2012e-0ubuntu0.12.04). Uploads should also be made to any releases
supported via ESM.

Due to the potentially disastrous consequences of having localtime
differ between systems running -updates and systems running only
-security, this package is always kept in sync between the two pockets.
However, the package can be built with -updates and then copied from
-proposed to -updates and -security after the security team has signed
off on the SRU bug e.g. [Bug 1878108](https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1878108).

## distro-info-data

Many tools behave drastically differently based on the contents of
ubuntu.csv in distro-info-data. As such, information for new releases is
always backported to -updates, and should always be copied to -security
to avoid behaviour skew between the two pockets.

This package should be updated as soon as possible after the new
release’s name is known. If only the adjective is known, it should be
updated even with this partial information (use XANIMAL for the animal
where X is the first letter of the adjective). The aging requirement is
not applied for releasing to -updates / -security. A tracking bug is
still required for SRUs. Verification is still required. The testing
section should contain:

```default
[ Test Plan ]

Verify that the following subcommands of `distro-info` print information about the new devel and current stable releases:

* `--devel`
* `--supported`
* `--stable`

and try the same commands with these modifiers:

* `--date=<1 day after release>` along with the above
* `--fullname`
* `--release`
```

## linux-firmware

linux-firmware in stable releases is kept in sync with new driver features and
lts-hwe kernel updates. linux-firmware follows the normal SRU process (with
bugs filed and regression tests performed), and when ready to release, it
should be copied to the -security pocket. This is needed because the vast
majority of kernel SRUs are also copied to the -security pocket, and care must
be taken to not leave the kernel with a mismatched firmware package.

However, it is a very large package (over 500MiB in size), and making it
instantly available in the -security pocket to all Ubuntu users in the world
via unattended-upgrades causes a lot of strain on the archive network and
servers. Ubuntu 26.04 LTS has split the linux-firmware package into multiple
smaller packages, but for older releases we need to mitigate the impact to all
users.

Therefore, for now, once the verification is done and linux-firmware is ready
to be (SRU) released we have to stagger the release to spread the load.

* First it should be released to the updates pocket - allowing mirrors to sync
  it and anyone running explicit updates to pick it up.
* After the phasing has completed and we are ready to copy it to the security
  pocket, first we need to notify Canonical IS, so that they can put mitigation
  measures in place and prepare for the increased load on the archive.
* After Canonical IS has given the go-ahead, the linux-firmware packages must
  be copied to the security pocket by either an archive admin, or a security
  team member. That copy should also be spread out over Ubuntu releases, one at
  a time. The suggested delay in-between is 4 days, which combined with the
  “avoid Friday” rule suggests Mon,Thu,Mon,… until all are fully released.

Note that this release process described above only applies to SRUs. Actual
security updates to this package are not handled through the SRU process
but will also need to follow the staged release until properly mitigated.

## wireless-regdb

Much like linux-firmware, wireless-regdb follows the usual SRU process,
including a bug and regression testing, however it is another package
that needs to be kept in sync between -updates and -security pockets to
avoid potential local legal issues for -security users who would
otherwise not get the local regdb updates.

## Toolchain Updates

Due to the nature of the various Ubuntu toolchain packages (gcc-\*,
binutils, glibc), any stable release updates of these packages should be
released to both the -updates and -security pockets. For that to be
possible, any updates of those should be first built in a reliable
security-enabled PPA (without -updates or -proposed enabled) and only
then **binary-copied** into -proposed for testing (that is a
hard-requirement for anything copied into -security). After the usual
successful SRU verification and aging, the updated packages should be
released into both pockets.

Toolchains:

* Java: [Java updates PPA](https://launchpad.net/~openjdk-r/+archive/ubuntu/ppa)
* Go: [Go updates PPA](https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/golang)
* Python: [Python updates PPA](https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/python)

## Crash And Makedumpfile

The crash and makedumpfile source packages may be uploaded according to the
procedure documented in [CrashMakedumpfile-Updates](https://documentation.ubuntu.com/project/SRU/reference/exception-CrashMakedumpfile-Updates.md#reference-crash-and-makedumpfile-updates).