ReleaseManagement

Differences between revisions 12 and 13
Revision 12 as of 2010-07-21 12:28:00
Size: 2309
Editor: 193
Comment:
Revision 13 as of 2010-07-22 14:19:31
Size: 2311
Editor: 193
Comment:
Deletions are marked like this. Additions are marked like this.
Line 37: Line 37:
http://patchwork.ozlabs.org/project/ubuntu-kernel/list/ <<Include(Kernel/FAQ/GeneralPatchHandling,,from="==.*")>>

** WORK IN PROGRESS **

The intention of this handbook is to outline the role of the Ubuntu Kernel Release Manager. For general developer information such as building a kernel, please refer to the the Kernel/Dev area of the wiki.

Role of the Ubuntu Kernel Release Manager

Every release cycle, a member of the Ubuntu kernel team is selected as the Ubuntu Kernel Release Manager. They are responsible for all aspects of the delivery of the Ubuntu kernel for that release. These responsibilities include, but are not limited to:

  • Opening the release
  • Maintaining the release
  • Uploading the kernel package(s)
  • Patch Review
  • Weekly Release Meeting
  • UDS Responsibilities
  • Vendor Relationships

Opening the Release

One of the first responsibilities for the Ubuntu Kernel Release Manager is to open and prepare the git tree for the upcoming release. The following wiki outlines the steps for starting this new git tree.

Kernel/Dev/OpeningRelease

Maintaining the release

An ongoing responsibility of the Ubuntu Kernel Release Manager is to maintain the master git repo and any subsequent branches and/or packages. The following wiki details the general process for maintaining the git repo's.

Kernel/Dev/MaintainingRelease

Uploading the Ubuntu kernel package(s)

In addition to maintaining the git repo's, the Ubuntu Kernel Release Manager is also responsible for building and uploading the linux kernel package(s). The following wiki describes this process.

Kernel/Dev/KernelPackaging

Patch Review

Patches are submitted to the Ubuntu kernels via the kernel-team mailing list. We use this list as the primary record of the discussions, acceptance, or rejection, of each patch (see Kernel/FAQ/GeneralMailingList). We use the patchworks patch tracking system to aid in this process http://patchwork.ozlabs.org/project/ubuntu-kernel/list/. See Kernel/Handbook/Patchworks for documentation on how we use patchworks within the team.

Weekly Release Meeting

https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick

UDS Responsibilities

  • Ubuntu Kernel Patch Delta Review
  • Ubuntu Kernel Config Review
  • Ubuntu Kernel Version
  • Managing Blueprints
  • Kernel Track Scheduling

Vendor Relationships

  • Tracking feature requests from partner vendors

Kernel/Handbook/ReleaseManagement (last edited 2011-04-15 15:06:44 by c-76-105-148-120)