ReleaseMeeting
At some point during the development cycle the Release Team will begin holding weekly IRC release meetings. The Ubuntu Kernel Release Manager is required to attend this meeting as a representative on behalf of the Ubuntu Kernel Team. Responsibilities for this meeting include:
- Attend the meeting
- Prepare to speak on items called out in the agenda
- Update the Kernel Team Release Status wiki page
- Make sure the team is on track for completing assigned work items
Meeting Date/Time/Location
This meeting takes place on FreeNode in #ubuntu-meeting every Friday at 1500UTC.
Meeting Agenda Preparation
The agenda for the meeting is emailed out the night prior and is also posted to http://wiki.ubuntu.com/ReleaseTeam/Meeting/Agenda . As the Ubuntu Kernel Release Manager, be sure your email is added to the list of recipients for the agenda so that you can prepare for the meeting in advance (ie so you can cut n' paste the team's status). The meeting is organized such that each team provides a weekly status. This status includes summaries for blueprints/specs and release critical bugs that were highlighted in the agenda. An example of what is posted to the meeting is as follows:
Taken from http://irclogs.ubuntu.com/2010/07/16/%23ubuntu-meeting.txt
[16:12] <robbiew> [TOPIC] Kernel [16:12] <MootBot> New Topic: Kernel [16:12] <ogasawara> Overall Kernel Team status is summarised at the first URL below, including the item(s) called out in the agenda. Our burndown chart for Alpha3 is at the third URL, and our overall burndown chart is at the fourth: [16:12] <ogasawara> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick [16:12] <ogasawara> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick#Milestone maverick-alpha-3 [16:12] <ogasawara> [LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team-maverick-alpha-3.html [16:12] <ogasawara> [LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team.svg [16:12] <MootBot> LINK received: https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick [16:12] <MootBot> LINK received: https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick#Milestone maverick-alpha-3 [16:12] <MootBot> LINK received: http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team-maverick-alpha-3.html [16:12] <robbiew> and here it comes [16:12] <MootBot> LINK received: http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team.svg [16:12] <ogasawara> heh [16:12] <ogasawara> On the items noted in the agenda, spec status is as follows: [16:12] <ogasawara> * kernel-maverick-apparmor: The latest upstream submission was posted yesterday. Development is on going and improvements to file, capability, network, resource usage and ipc mediation are planned. However, With this submission we believe AppArmor is ready for inclusion into the mainline kernel. [16:13] <ogasawara> * kernel-maverick-pv-ops-ec2-kernel: Received confirmation from Amazon contacts that pv-ops based kernels should work in EC2 and that the xsave hypercall needs to be disabled or there will be issues with booting kernels. jjohansen has built a test kernel and should have results shortly. [16:13] <ogasawara> Bug status is as follows: [16:13] <ogasawara> Bug 591941 [16:13] <ubottu> Launchpad bug 591941 in linux (Ubuntu Maverick) "SDHC card not recognized" [High,In progress] https://launchpad.net/bugs/591941 [16:13] <ogasawara> mpoirier is working this issue with TI but there is still no resolution currently. [16:13] <ogasawara> Bug 595489 [16:13] <ubottu> Launchpad bug 595489 in linux (Ubuntu Maverick) "lvm snapshot causes deadlock in 2.6.35" [High,In progress] https://launchpad.net/bugs/595489 [16:13] <ogasawara> A patch has been posted upstream but not yet accepted. [16:13] <ogasawara> Bug 597387 [16:13] <ubottu> Launchpad bug 597387 in Ubuntu Maverick "pv-ops kernel only works in 3 or 4 zones in EC2" [High,Confirmed] https://launchpad.net/bugs/597387 [16:13] <ogasawara> Testing currently underway (See spec notes above). [16:14] <ogasawara> Bug 599450 [16:14] <ubottu> Launchpad bug 599450 in linux (Ubuntu Maverick) "[apparmor] getattr handled incorrectly in 2.6.35-6.7" [High,New] https://launchpad.net/bugs/599450 [16:14] <ogasawara> See security team notes above. [16:14] <ogasawara> As a general status, we've rebased to 2.6.35-rc5 and uploaded. We're also in the process of updating aufs2 and plan to upload today. We are above the trend line in our Alpha3 burndown chart but below the trend line overall. The remaining Alpha3 work items are not release critical. [16:14] <ogasawara> Questions?
Ubuntu Kernel Team Release Status Wiki
The Ubuntu Kernel Release Manager keeps the KernelTeam/ReleaseStatus/<RELEASE> wiki page, eg. https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick up to date on a weekly basis. This page should be a summary of the current status of the Ubuntu Kernel during the development cycle. This page should be updated prior to the weekly Release Team meeting and should reflect any items called out in the Release Team meeting agenda.
Tracking Blueprint Work Items
The Kernel Team's Release Status wiki page has work items broken down by milestone. For example maverick-alpha-2:
https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick#Milestone maverick-alpha-2
This is also represented in a graphical form, ie a burn down chart:
http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team-maverick-alpha-2.html
There also exists a burn down chart which encompasses all the work items for an entire release cycle. For example:
http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team.svg
As the Ubuntu Kernel Release Manager, the goal is to make sure work items are on target to complete on time, ie the team is below the trend line for the burn down chart for each milestone as well as overall. If items begin to slip is it the responsibility of the Ubuntu Kernel Team Release Manager to work with the assigned party and remedy the situation either by re-targeting the work item, finding additional help to complete the work item, or POSTPONE the work item all together.
Note: The tables and graphs are generated directly from the blueprints and are updated on an hourly basis.