KernelNattyStableProcessReview

Revision 2 as of 2010-10-18 16:48:09

Clear message

Summary

The purpose of this spec is to go over the current stable process (including the SRU policy) to see how we are doing and to see which parts can be improved or documented better.

Release Note

The impact on users would be to have a place which well documents what changes can be made to stable releases, how to ask for inclusion and why decision will be made the way they are done. This is less likely to go into the general release notes but should be linked from a prominent place on the kernel wiki page.

Rationale

Over time we changed our preferences on how or what we take for stable releases. But it seems the presentation on this is still distributed over too many places to give a simple and easy start. Also there are likely a few places where we could improve the work-flow of the whole process.

Assumptions

  • Upstream stable should get into the master branch as quickly as possible.
  • Regression testing needs to be done in proposed.
  • While security may delay the actual uploads to proposed but the repo (and by that pre-proposed) should always be as advanced as possible.

Design

tbd

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

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.


CategorySpec