JauntyKernelTeamProcess

Revision 2 as of 2008-11-25 18:21:08

Clear message

Summary

Review of the current kernel team processes for all stages of the release cycle.

Release Note

Rationale

Use Cases

Assumptions

Design

Implementation

UI Changes

Code Changes

Migration

Test/Demo Plan

Unresolved issues

BoF agenda and discussion

pgraner's notes

  • Tree Mgt & Process & Kernel Packaging

    • New release tasks
      • Patch review
        • Need to be sure that when we drop a patch, it's an explicit decision, and coordinated with developers who might be depending on it.
        • next rebase to include a public review of all patches and their fate (e.g. on ubuntu-devel@lists)?
        • Upstreaming of Sauce patches.
    • Kernel Subsystem updates

      • Matching of Kernel -> Userspace components

  • Notification?
    • Review
      • Firmware review
        • What can be deprecated, removed and whats new? License OK.
        • License review procedures.
        • Who is involved? Tech Board? Legal? sabdfl?
  • Kernel Version
    • Checkpoints thought the cycle to ensure we don't hit the 2.6.27 late cycle issue
  • New kernel features
    • Diffing of config
    • What constitutes us turning on a feature?
    • Approval
    • HWDb
    • New 3rd party code/firmware.
    • License review
    • Tracking files
  • ABI (yet one more time)
    • List of symbols that vendors need?
      • VMWare
      • Parallels
      • Others?
  • SRU Release Points
    • Predictable release of SRUs (time baesed)
    • Security as needed
    • Try and schedule ABI security bumpers and bugs at same time
  • Upstream Vanilla Kernel Package
    • Is ths something we can start providing?
    • Beneficial for bug reporters to test the upstream kernel
    • Will also improve the upstream bug reporting process

CategorySpec