KernelVersion

Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2007-10-29 13:46:00 →
Size: 2109
Editor: 12
Comment:
← Revision 2 as of 2007-10-29 15:50:11 → ⇥
Size: 2517
Editor: 12
Comment: Initial draft from BoF
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
Which kernel version to use for 8.04 Decision on whether to use 2.6.24 or 2.6.23 for Hardy 8.04 LTS release. Decision
will be based on:
Line 12: Line 13:
== Release Note ==  * Features in 2.6.23 that may be too new or unstable for use in an LTS.
 * Features in 2.6.24 ""
 * Features in 2.6.24 that are desirable enough to warrant its usage even given other undesirable features/bugs.
 * What other distributions are using (gives us more effort to long term support)
 * UbuntuMobile concerns (ABI bumps, third-party module support)
Line 14: Line 19:
TBD == Changes in upstream ==

 * 2.6.23 changes - http://kernelnewbies.org/Linux_2_6_23
 * 2.6.24 changes - http://lwn.net/Articles/254559/, http://lwn.net/Articles/255327
Line 18: Line 26:
This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified. Reasons for 2.6.24:
 * Full mac80211 stack being merged
 * SDIO merge, required for lpia
 * Lots of wireless drivers being merged: 3945/4965
 * b43 driver (replaces bcm43xx) sucks less
 * Dynamic tick support for x86_64
 * cpuidle
 * Follows our past kernel version selection
 
Reasons for 2.6.23:
 * We like physical abuse
 * More time to stabilize
 * Less of a moving target for MID/Mobile
 * Easier to get Xen/RealTime type patches into kernel build sooner
 * Easier for third-party module vendors to start developing/testing for 8.04
Line 22: Line 44:
Booting your computer
Line 24: Line 48:
== Design ==

You can have subsections that better describe specific parts of the issue.		 That 2.6.24 will be released in time for us to stabilize. Based on past release schedules, we expect 2.6.24 to be released mid to late Jan. Latest expectation is around start of Feb.
Line 30: Line 52:
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.		 Using 2.6.23, the kernel source would be immediately based on released source. Using 2.6.24, we would follow upstream as we have before, rebasing on a scheduled basis.
Line 49: Line 56:
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 CD testing, and to show off after release.

This need not be added or completed until the specification is nearing beta.		 We ought to have one of every wireless chipset that is supported in main line kernel.
  - Try to use Rutgers' infrastructure for wireless testing? (Luis Rodriguez?)
Line 55: Line 61:
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. Release schedule depends on this decision.

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

Summary

Decision on whether to use 2.6.24 or 2.6.23 for Hardy 8.04 LTS release. Decision will be based on:

  • Features in 2.6.23 that may be too new or unstable for use in an LTS.
  • Features in 2.6.24 ""
  • Features in 2.6.24 that are desirable enough to warrant its usage even given other undesirable features/bugs.
  • What other distributions are using (gives us more effort to long term support)

  • UbuntuMobile concerns (ABI bumps, third-party module support)

Changes in upstream

Rationale

Reasons for 2.6.24:

  • Full mac80211 stack being merged
  • SDIO merge, required for lpia
  • Lots of wireless drivers being merged: 3945/4965
  • b43 driver (replaces bcm43xx) sucks less
  • Dynamic tick support for x86_64
  • cpuidle
  • Follows our past kernel version selection

Reasons for 2.6.23:

  • We like physical abuse
  • More time to stabilize
  • Less of a moving target for MID/Mobile
  • Easier to get Xen/RealTime type patches into kernel build sooner
  • Easier for third-party module vendors to start developing/testing for 8.04

Use Cases

Booting your computer

Assumptions

That 2.6.24 will be released in time for us to stabilize. Based on past release schedules, we expect 2.6.24 to be released mid to late Jan. Latest expectation is around start of Feb.

Implementation

Using 2.6.23, the kernel source would be immediately based on released source. Using 2.6.24, we would follow upstream as we have before, rebasing on a scheduled basis.

Test/Demo Plan

We ought to have one of every wireless chipset that is supported in main line kernel.

  • - Try to use Rutgers' infrastructure for wireless testing? (Luis Rodriguez?)

Outstanding Issues

Release schedule depends on this decision.

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.

CategorySpec CategoryKernel

KernelTeam/Hardy/KernelVersion (last edited 2008-08-06 16:26:24 by localhost)