KernelMaverickVersion
|
Size: 2753
Comment:
|
Size: 1811
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 21: | Line 21: |
| == User stories == | == Assumptions == Based on the cadence of previous upstream releases, I'd anticipate 2.6.34 being released around June 2010, 2.6.35 being released around Sept 2010, and 2.6.36 being released around Dec 2010. |
| Line 23: | Line 24: |
| == Assumptions == == Design == You can have subsections that better describe specific parts of the issue. == Implementation == This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like: === UI Changes === Should cover changes required to the UI, or specific UI that is required to implement this === Code Changes === Code changes should include an overview of what needs to change, and in some cases even the specific details. === Migration === Include: * data migration, if any * redirects from old URLs to new ones, if any * how users will be pointed to the new way of doing things, if necessary. == Test/Demo Plan == It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage. This need not be added or completed until the specification is nearing beta. |
Kernel freeze for Maverick is Oct 14, 2010 |
Launchpad Entry: kernel-maverick-version-decision
Created:
Contributors:
Packages affected:
Summary
The purpose of this spec is to choose the mainline kernel that will become the base for the Maverick kernel development cycle.
Release Note
This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)
It is mandatory.
Rationale
Every release cycle we must choose a kernel that is as recent as possible while still remaining stable. Typically the decision is simply the most recently released kernel prior to the Ubuntu release. As Maverick will be the successor of an LTS release, we will likely try to push for the bleeding edge.
Assumptions
Based on the cadence of previous upstream releases, I'd anticipate 2.6.34 being released around June 2010, 2.6.35 being released around Sept 2010, and 2.6.36 being released around Dec 2010.
Kernel freeze for Maverick is Oct 14, 2010
Unresolved issues
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.
KernelTeam/Specs/KernelMaverickVersion (last edited 2010-05-19 00:00:46 by c-76-105-148-120)