Rolling

Differences between revisions 3 and 4
⇤ ← Revision 3 as of 2012-05-10 23:29:25 →
Size: 2271
Editor: leannogasawara
Comment:
← Revision 4 as of 2012-05-10 23:44:05 → ⇥
Size: 2473
Editor: leannogasawara
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== Rolling Kernel Updates == The following is describing our suggested policy and package naming conventions for newer kernels in previous LTS releases.

== The 10.04 Lucid Scenario ==
For Lucid, we are currently backed into a corner, eg the 10.10 Maverick release will EOL and leave users stranded. We will issue a USN and MOTD to the effect that the 10.10 Maverick kernel is falling out of support. It will suggest they install the linux-image-hwe-<flavor> rolling meta package to ensure they are always upgraded to a newer supported kernel.

== The 12.10 through 14.04 Scenario ==
As it is today at UDS-Q it's been decided that we will provide a backports kernel per Q, R, S, and T. And these will be upgraded directly to T once T is released. We will need to create the following suggestedly named meta packages:

 * linux-image-hwe-<flavor> -> rolling release meta package. It will point to one of the linux-image-<version>-<flavor> meta package.
 * linux-image-12.10-<flavor> -> 12.10 meta package
 * linux-image-13.04-<flavor> -> 13.04 meta package
 * linux-image-13.10-<flavor> -> 13.10 meta package
 * linux-image-14.04-<flavor> -> 14.04 meta package

== 14.04 and Newer - Proposed Scenario ==
Line 7: Line 21:
 * linux-image-generic will continue to reference the GA 3.2 kernel for 5 years.
 * linux-image-12.04-generic will reference the current release kernel until the 14.04 release inclusive.

== Current Situation @ UDS-Q ==
As it is today at UDS-Q it's been decided that we will provide a backports kernel per Q, R, S, and T. And these will be upgraded directly to T once T is released. We will need to create the following suggestedly named meta packages:

 * linux-image-hwe-<flavor> -> rolling release meta package. It will point to one of the linux-image-<version>-<flavor> meta package
 * linux-image-12.10-<flavor> -> 12.10 meta package
 * linux-image-13.04-<flavor> -> 13.04 meta package
 * linux-image-13.10-<flavor> -> 13.10 meta package
 * linux-image-14.04-<flavor> -> 14.04 meta package

== The Lucid Scenario ==
For Lucid, we are currently backed into a corner, eg the M will EOL and leave users stranded. We will issue a USN and an MOTD to the effect that the M kernel is falling out of support. It will suggest they install the linux-image-hwe-<flavor> rolling meta package to ensure they are upgraded to a supported kernel.		  * linux-image-hwe-<flavor> will always point to the latest supported kernel version meta package below.
 * linux-image-<version>-<flavor> will reference the current supported kernel version.

The following is describing our suggested policy and package naming conventions for newer kernels in previous LTS releases.

The 10.04 Lucid Scenario

For Lucid, we are currently backed into a corner, eg the 10.10 Maverick release will EOL and leave users stranded. We will issue a USN and MOTD to the effect that the 10.10 Maverick kernel is falling out of support. It will suggest they install the linux-image-hwe-<flavor> rolling meta package to ensure they are always upgraded to a newer supported kernel.

The 12.10 through 14.04 Scenario

As it is today at UDS-Q it's been decided that we will provide a backports kernel per Q, R, S, and T. And these will be upgraded directly to T once T is released. We will need to create the following suggestedly named meta packages:

  • linux-image-hwe-<flavor> -> rolling release meta package. It will point to one of the linux-image-<version>-<flavor> meta package.

  • linux-image-12.10-<flavor> -> 12.10 meta package

  • linux-image-13.04-<flavor> -> 13.04 meta package

  • linux-image-13.10-<flavor> -> 13.10 meta package

  • linux-image-14.04-<flavor> -> 14.04 meta package

14.04 and Newer - Proposed Scenario

The kernel team is considering the adoption of a rolling kernel upgrade policy for 14.04. This means that the 14.04 GA kernel will not be supported for 5 years. Rather, only the current release kernel is actively supported with bug fixes and CVEs. We propose some overlap while the new release kernel is being tested for regressions, but eventually users will be required to upgrade in order to continue to receive support. This, of course, is predicated on our ability to thoroughly Q/A the next release kernel for regression.

For the 12.04 LTS we are proposing to prototype this concept by introducing a new kernel meta package that will be updated periodically to reference the current release kernel. When 12.10 is released, this meta package will be updated to depend on the 12.10 backport kernel. We are also considering not offering a meta package that directly references a release backport kernel as we have for 10.04, e.g., anyone that installs a backport kernel will get automatically upgraded when new backport kernels are released )(12.10, 13.04, 13.10, 14.04),

  • linux-image-hwe-<flavor> will always point to the latest supported kernel version meta package below.

  • linux-image-<version>-<flavor> will reference the current supported kernel version.

Kernel/Release/Rolling (last edited 2013-10-11 17:07:36 by mail)