StableReleaseUpdates
|
Size: 6428
Comment: Add kernel exception
|
Size: 6543
Comment: edit kernel bits
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 74: | Line 74: |
| == Kernel Exception == | == Special Cases == |
| Line 76: | Line 76: |
| Because of the way updates to the kernel work, it will follow a slightly different set of rules. The following reasons call for this exception: | === Kernel === Because of the way updates to the kernel work, it will follow a slightly different process. The following reasons call for this exception: |
| Line 79: | Line 81: |
| * Changes in the kernel cannot be approved wholesale. Each change needs to be approved individually, and on its own merits. * Even though most of the patches are, in general, backports, the -backports channel is not acceptable. * The kernel will never be moved from -proposed to -updates. |
* Kernel packages are not copied from `-proposed` to `-updates` or `-security` * A facility is needed for staging updates to the kernel in bulk, and `-proposed` is the closest fit |
| Line 83: | Line 84: |
| Given these criteria, the kernel will be given slightly less restrictions on uploads to -proposed. Over its lifetime, each patch in the -proposed kernel will be individually approved for inclusion into a -security upload based on testing results and the same approval methods for -proposed/-updates uploads. | Therefore the following differences apply: * Updates for the kernel will be routinely uploaded to `-proposed` with a specially chosen ABI version (and therefore package name) to avoid clashing with any other kernel installed in the field. Users will not be automatically upgraded to this kernel. * No prior discussion and approval is needed for kernel updates to `-proposed` * Individual kernel patches, rather than complete packages, will go through the SRU process above, after having been staged in `-proposed` |
Once an Ubuntu release has been completed and published, updates for it are only released under certain circumstances, and must follow a special procedure.
Why
In contrast to pre-release versions, official releases of Ubuntu are subject to much wider use, and by a different demographic of user. During development, changes to the distribution primarily affect developers, early adopters and other advanced users, all of whom have elected to use pre-release software at their own risk.
Users of the official release, in contrast, expect a high degree of stability. They use their Ubuntu system for their day-to-day work, and problems they experience with it can be extremely disruptive. Many of them are less experienced with Ubuntu and with Linux, and expect a reliable system which does not require their intervention.
Stable release updates are automatically recommended to a very large number of users, and so it is critically important to treat them with great caution. Therefore, when updates are proposed, they must be accompanied by a strong rationale and present a low risk of regressions.
When
Stable release updates will, in general, only be issued in order to fix high-impact bugs. Examples of such bugs include:
Bugs which may, under realistic circumstances, directly cause a security vulnerability
Bugs which represent severe regressions from the previous release of Ubuntu
Bugs which may, under realistic circumstances, directly cause a loss of user data
How
This process is to be followed for all updates except those to fix security updates, which are only released by the Ubuntu security team. Security procedures are documented at SecurityUpdateProcedures.
- Propose
All proposals for stable release updates must be approved by Matt Zimmerman or Colin Watson. SRU proposals must be accompanied by the following information for each bug to be addressed:
A bug number referring to a complete bug report describing the problem and its effect
A statement explaining the impact of the bug on users and justification for backporting the fix to the stable release
An explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix
A patch applicable to the stable version of the package. If preparing a patch is likely to be time-consuming, it may be preferable to discuss the first three items before preparing a patch.
A copy of this proposal and a hyperlink to any prior discussion thread should be added to the bug report as a comment, usually by CCing bugnumber@bugs.launchpad.net.
- Prepare
- Once an update has been discussed and approved in principle, an upload can be prepared. The following criteria apply to any packages modified as part of the update:
The changelog entry and resulting .changes file must include a reference to the corresponding bug report(s)
The bug report must include an approved SRU proposal
The version number(s) must be carefully checked in order to avoid clashing with any other version of the package, past, present or future
The upload target must be release-proposed
Uploads which do not meet these criteria will be rejected by an archive administrator and not published. Once the upload is ready, attach a complete source package diff (debdiff) to the bug report for review.
- Once an update has been discussed and approved in principle, an upload can be prepared. The following criteria apply to any packages modified as part of the update:
- Upload
- The upload will be reviewed by the archive administrators, and approved if it meets the above criteria. Archive administrators should verify that the package delta matches the debdiff attached to the bug report.
- Test
Once the update has been published in -proposed, it can be tested by a wider audience.
Notify the QA team via Simon Law [mailto:sfllaw@ubuntu.com <sfllaw@ubuntu.com>] of the availability of this package for testing
- Test the package yourself
- If the update has the potential for hardware-specific effects, request a hardware support regression test via the QA team (for example, kernel updates)
- Release
After successful testing and a minimum aging period of 7 days, you may prepare a second upload to release-updates:
- Include a changelog entry with:
- A new version number (the same cautions apply regarding the choice of version number)
Confirmation of the above testing, including the name of the tester in each case
Make no other changes relative to the version in -proposed
The archive administrators must verify that uploads to -updates meet these criteria. In the future, the update from -proposed will be copied verbatim instead, once the necessary infrastructure is available.
- Following up
Add yourself as a bug contact for the package in Launchpad, if you are not one already
For 7 days after the update is released, monitor Launchpad for bug reports relating to the update
In the event of a regression, immediately notify the [mailto:technical-board@lists.ubuntu.com Ubuntu Technical Board] via email, and ask for help on #ubuntu-devel in making urgent contact with a member of the Board.
Special Cases
Kernel
Because of the way updates to the kernel work, it will follow a slightly different process. The following reasons call for this exception:
- The kernel is uploaded frequently to -security, so uploading to -updates is not possible due to frequent version skew in the kernel and supporting packages (linux-restricted-modules, linux-meta, etc).
Kernel packages are not copied from -proposed to -updates or -security
A facility is needed for staging updates to the kernel in bulk, and -proposed is the closest fit
Therefore the following differences apply:
Updates for the kernel will be routinely uploaded to -proposed with a specially chosen ABI version (and therefore package name) to avoid clashing with any other kernel installed in the field. Users will not be automatically upgraded to this kernel.
No prior discussion and approval is needed for kernel updates to -proposed
Individual kernel patches, rather than complete packages, will go through the SRU process above, after having been staged in -proposed
(This section is based on discussions between AdamConrad, MattZimmerman and BenCollins)
StableReleaseUpdates (last edited 2024-02-15 13:33:43 by racb)