= Meeting Minutes = [[http://irclogs.ubuntu.com/2012/04/10/%23ubuntu-meeting.txt|IRC Log of the meeting.]] [[http://voices.canonical.com/kernelteam|Meeting minutes.]]
== Agenda == [[https://wiki.ubuntu.com/KernelTeam/Meeting#Tues, 10 Apr, 2012|20120410 Meeting Agenda]] === ARM Status === nothing new to report this week === Release Metrics and Incoming Bugs === Release metrics and incoming bug data can be reviewed at the following link: * http://people.canonical.com/~kernel/reports/kt-meeting.txt === Milestone Targeted Work Items === || apw || hardware-p-kernel-delta-review || 1 work item || || ogasawara || hardware-p-kernel-config-review || 1 work item || || || hardware-p-kernel-versions-and-flavors || 1 work item || apw and I are aware of our work items, we'll get them closed before final. === Status: Precise Development Kernel === The Precise kernel is currently frozen and Final Freeze is this Thurs Apr 12. We have coordinated one additional upload scheduled for today (likely to occur after this meeting). At this point in time, all patches are subject to our SRU policy and uploads will only be granted at the discretion of the release team. https://wiki.ubuntu.com/Kernel/Dev/StablePatchFormat Important upcoming dates: * Thurs Apr 12 - Final Freeze (~2 days) * Thurs Apr 19 - Release Candidate (~1 week) * Thurs Apr 26 - Final Release (~2 weeks) === Status: CVE's === Currently we have 72 CVEs on our radar, with no new CVEs added this week. See the CVE matrix for the current list: * http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html Overall the backlog has decresed very slightly this week: * http://people.canonical.com/~kernel/status/cve-metrics.txt * http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt === Status: Stable, Security, and Bugfix Kernel Updates - Oneiric/Natty/Maverick/Lucid/Hardy === Here is the status for the main kernels, until today (Apr. 10): Oneiric has been somewhat problematic. We ran into a couple of very bad regressions that were pretty quickly identified. Our policy is to "revert aggressively" however our number one rule is to "Use our best judgement and do the right thing". In this case we are also running into the end of the Precise development cycle when testing resources (human) are scarce. After discussing this with a number of people we have decided to fix these known regressions and also pull in the stable release that was sitting on master-next and crank that out. The cycle will be extended with regression testing happening the week of May 1st. * Hardy - 2.6.24-31.101 - Nothing this cycle * Lucid - 2.6.32-41.88 - Verification; 52 commits in total. * Maverick - 2.6.35-32.68 - Ready for -updates; NOTE: THIS IS THE LAST MAVERICK KERNEL! * Natty - 2.6.38-14.58 - Ready for -updates; 12 commits in total. Mostly eCryptfs and KVM. * Oneiric - 3.0.0-19.32 - Verification; Current opened tracking bugs details: * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html For SRUs, SRU report is a good source of information: * http://people.canonical.com/~kernel/reports/sru-report.html Future stable cadence cycles: * https://wiki.ubuntu.com/PrecisePangolin/ReleaseInterlock === Open Discussion or Questions? Raise your hand to be recognized === No Discussion. -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
