ExtendedStable

Differences between revisions 15 and 16
Revision 15 as of 2012-04-11 15:47:05
Size: 5400
Editor: 177
Comment:
Revision 16 as of 2012-04-11 18:02:17
Size: 5469
Editor: 177
Comment:
Deletions are marked like this. Additions are marked like this.
Line 45: Line 45:
The maintenance process is more of interest for the person currently maintaining an stable tree, so it's not detailed here. If you are a maintainer, go to <TODO>. Generically, the process should be like this: The maintenance process is more of interest for the person currently maintaining an stable tree, so it's not detailed here. If you are a maintainer, go to [[Kernel/Dev/StableUpstream/Maintenance|Stable Kernel Updates Maintenance]]. Generically, the process should be like this:

Stable Kernel Updates

The Ubuntu Kernel Team provides a git repo available to the greater Linux community which provides stable patches for certain versions of the Linux kernel.

Repository

The repository probably will be available at git://kernel.ubuntu.com/ubuntu/linux-stable.git, for now an example repository is set up at git://kernel.ubuntu.com/herton/linux-stable.git

master

tracks the Linus master tree

linux‑<version>.y

stable tree for linux <version> release, final patches releases go to this

linux‑<version>.y‑queue

last release of stable tree for <version> release, with patches on top that are to be released with next <version> stable update

linux‑<version>.y‑review

last release of stable tree for <version> release, with patches on top ready to be released with next <version> stable update, but which are on release candidate status (waiting any complaints or potential fixes before being released)

<version> is the linux stable series the Ubuntu Kernel Team provides stable patches for. See the Version Matrix section for more information.

Builds

We will be hooking the stable tree up with our automated build and testing infrastructure. The built binaries will be available for download and installation.

New Releases

New releases of stable patches will be announced at kernel-team@lists.ubuntu.com, the linux kernel mailing list (lkml) and the stable mailing lists.

We will have a cadence of 1 to 3 weeks for new releases (that is, each 1/2/3 weeks if there are patches in the queue they will be put into a release candidate status, and if nothing is wrong after 2/3 days they will be released). For the release/maintenance process, see Maintenance below for more information.

Contributing

All patches for the stable releases maintained by the Ubuntu kernel team should be submitted upstream, following the stable upstream acceptance rules (see Documentation/stable_kernel_rules.txt in the upstream kernel source tree for more information). The Ubuntu Kernel Team should monitor and pick the relevant stable patches automatically once they are released with upstream stable. In case that not happens, or the change/patch is only applicable to one of the maintained versions by the Ubuntu kernel team (in the case the patch isn't relevant to any of the current stable kernel versions being maintained by upstream, for example when a Cc: stable@kernel.org isn't applicable anymore), you can contact the Ubuntu kernel team at kernel-team@lists.ubuntu.com requesting the patch to be applied. Of course the patch must conform to the stable upstream acceptance rules in the second case.

Version Matrix

This is the table with status of linux kernel versions that Ubuntu Kernel Team (UKT) provided, provides or plan to provide with stable patches support

Linux Version

Last Upstream Stable

Start of UKT support

End of UKT support

Maintainer

3.2

3.2.?

when upstream stable drops 3.2.y series

April 2017

-

2.6.32+drm33*

2.6.32.?/2.6.33.20

when upstream stable drops 2.6.32.y series/already on lookout for drm fixes for 2.6.33 as it's unsupported upstream now

April 2015

Stefan Bader

* Currently 2.6.32+drm33 is maintained as a special case and the repository and other details diverge from what is described in this page

Maintenance

The maintenance process is more of interest for the person currently maintaining an stable tree, so it's not detailed here. If you are a maintainer, go to Stable Kernel Updates Maintenance. Generically, the process should be like this:

  1. Patches not yet included on stable version and marked for stable* are picked up from master Linus tree, and we try to apply them to the linux‑<version>.y‑queue branch:

    • Patches which apply cleanly, should be reviewed. If something shouldn't have been applied/added, discard/remove from the branch.
    • Patches which fails to apply, should be reviewed. If they are applicable to stable linux‑<version>.y, it must be fixed or a request sent out for help with backporting/fixing. The fixed version should be applied to the branch

    • Patches marked for stable but with a restriction for a specific kernel version, should only be applied if they are intended for stable linux‑<version>.y being maintained, in case the patch isn't applicable for it should be discarded.

  2. After the cadence period, push the patches from the linux‑<version>.y‑queue to the linux‑<version>.y‑review branch, and announce a review cycle on the mailing lists.

  3. After the review period, and with any problems found in review process fixed, push the patches from review to to linux‑<version>.y branch, close and tag the new release with same versioning as upstream, and rebase/sync both queue/review branches. Then Announce the new release.

* marked for stable means the patch has Cc to stable, or was requested/should be included following the rules on the Contributing section. The same upstream stable rules apply.

Kernel/Dev/ExtendedStable (last edited 2016-07-13 18:58:46 by kamalmostafa)