= Meeting Minutes =
[[http://irclogs.ubuntu.com/2011/05/24/%23ubuntu-meeting.txt|IRC Log of the
meeting.]]
<<BR>>
[[http://voices.canonical.com/kernelteam|Meeting minutes.]]
== Agenda ==
[[https://wiki.ubuntu.com/KernelTeam/Meeting#Tues, 24 May, 2011|20110524
Meeting Agenda]]
=== Release Metrics ===
Release Meeting Bugs (0 bugs, 18 Blueprints)
==== Release Milestoned Bugs (24 across all packages) ====
* 0 linux kernel bugs ()
* 0 linux-ti-omap4 bugs ()
* 0 linux-meta-ti-omap4 bug ()
==== Release Targeted Bugs (171 across all packages) ====
* 21 linux kernel bugs ()
* 6 linux-ti-omap4 bugs ()
* 0 linux-meta-ti-omap4 bug ()
==== Milestoned Features ====
* 1 blueprint (Including HWE Blueprints)
==== Natty Updates Bugs ====
* 28 Linux Bugs ()
==== Maverick Updates Bugs ====
* 5 Linux Bugs (no change)
==== Lucid Updates Bugs ====
* 17 Linux Bugs (up 1)
==== Bugs with Patches Attached:90 (up 3) ====
*
[[https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on
| Bugs with Patches]]
* [[http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/
| Breakdown by status]]
=== Blueprints: Oneiric Bug Handling ===
All alpha 1 items are in progress:
* [jeremyfoshee] work with SRU team and KRM to develop/define process for
addressing development kernel bugs.: INPROGRESS
* started this conversation with an e-mail.
* [jeremyfoshee] Generate specific hotlist for devel bugs focus: INPROGRESS
* will initially use the same requirements as the 'by team' hotlist, but
focused on Oneiric
* copied the hotlist script and currently working through changes
* [jeremyfoshee] drive new state bugs to 0 and maintain 0 new status bugs
daily: INPROGRESS
* 8 current oneiric bugs. All have been initially triaged and are now going
through deeper analysis so far this has helped me determine what skills I'd
like to further develop
* [jeremyfoshee] identify which scripts we no longer run which we should port
forward (with the aim of 0 New bugs): INPROGRESS
* Brad's confirmed script is doing a great job currently of identifying
what bugs are complete enough to be set confirmed
* Started the discussion on this in e-mail. Will follow up with some
thoughts as soon as I have had the time to evaluate the responses and chatted
with Pete (he's been quite busy lately :))
=== Blueprints: Oneiric Config Review ===
We just need to schedule a follow on config review session to look at jj's
config comparisons. I suggest we do this at the Rally. I'm continuing to work
through some of the config options noted from UDS, none of which are critical
for the Alpha-1 release.
=== Blueprints: Oneiric Delta Review ===
apw, bjf, jjohansen, kees, lag, manjo, mpoirier, ralveti, rtg: you have Alpha-1 work items to review your set of Ubuntu patches. Please take a moment to review or postpone till Alpha-2. See
https://wiki.ubuntu.com/KernelTeam/Specs/KernelOneiricUbuntuDeltaReview for your specific set of patches.
=== Blueprints: Oneiric Server Requirements ===
All good (nothing started)
=== Status: General Oneiric ===
We've uploaded the 2.6.39-3.9 kernel which is based on upstream v2.6.39 final.
I intend to keep us on v2.6.39 final for our Alpha-1 release on Thurs June 2.
=== Status: Stable Kernel Team ===
All kernel packages in -proposed have had verification complete and will be
published when Certification and
QA are complete (Not all series receive Certification). The Stable team will
prepare new kernel packages this
week to begin a new cycle.
<<BR>>
<<BR>>
As decided at UDS, the stable kernel cadence will change to a three week cycle,
in order to allow time to
properly prepare the kernel packages
<<BR>>
<<BR>>
Herton is part of the stable team this cycle and Brad is part-time while doing
work with QA.
=== Security & bugfix kernels - Maverick/Lucid/Hardy ===
||Package || Upd/Sec ||
Proposed || TiP || Verified ||
|| || ||
|| || ||
||lucid linux-ec2 || 2.6.32-314.27 ||
2.6.32-316.31 || 8 || 8 ||
||--- linux-ports-meta || 2.6.32.31.23 ||
2.6.32.32.24 || 0 || 0 ||
||--- linux-meta-lts-backport-maverick || 2.6.35.25.36 ||
2.6.35.28.37 || 0 || 0 ||
||--- linux-lts-backport-maverick || 2.6.35-25.44~lucid1 ||
2.6.35-28.50~lucid1 || 13 || 13 ||
||--- linux-backports-modules-2.6.32 || 2.6.32-31.31 ||
2.6.32-32.32 || 0 || 0 ||
||--- linux-firmware || 1.34.7 || 1.34.10
|| 0 || 0 ||
||--- linux || 2.6.32-31.61 ||
2.6.32-32.62 || 4 || 4 ||
||--- linux-meta || 2.6.32.31.37 ||
2.6.32.32.38 || 1 || 0 ||
||--- linux-meta-ec2 || 2.6.32.314.15 ||
2.6.32.316.17 || 0 || 0 ||
|| || ||
|| || ||
||maverick linux-ports-meta || 2.6.35.28.21 ||
2.6.35.29.22 || 0 || 0 ||
||--- linux-backports-modules-2.6.35 || 2.6.35-28.20 ||
2.6.35-29.21 || 0 || 0 ||
||--- linux-meta || 2.6.35.28.36 ||
2.6.35.29.37 || 0 || 0 ||
||--- linux-firmware || 1.38.6 || 1.38.8
|| 1 || 0 ||
||--- linux || 2.6.35-28.50 ||
2.6.35-29.51 || 11 || 9 ||
|| || ||
|| || ||
||natty linux-ti-omap4 || ||
2.6.38-1209.13 || 10 || 10 ||
||--- linux-backports-modules-2.6.38 || ||
2.6.38-9.3 || 0 || 0 ||
||--- linux-meta-ti-omap4 || ||
2.6.38.1209.7 || 0 || 0 ||
||--- linux-meta || ||
2.6.38.9.23 || 0 || 0 ||
||--- linux || ||
2.6.38-9.43 || 9 || 9 ||
|| || ||
|| || ||
* Note: Maverick proposed fails to boot on ec2. Currently investigating.
=== Incoming Bugs: Regressions ===
Incoming Bugs
9 Oneiric Bugs ()
1207 Natty Bugs (up 273)
1142 Maverick Bugs (up 13)
1029 Lucid Bugs (up 7)
Current regression stats (broken down by release):
==== regression-update ====
* 1 natty bug ()
* 42 maverick bugs (up 1)
* 74 lucid bugs (no change)
* 0 hardy bugs (no change)
==== regression-release ====
* 458 natty bugs (down 26)
* 244 maverick bugs (up 2)
* 222 lucid bugs (up 4)
* 2 hardy bugs (no change)
==== regression-proposed ====
* 1 natty bugs (up 1)
* 2 maverick bugs (no change)
* 0 lucid bugs (no change)
=== Open Discussion or Questions ===
Nothing this week.
--
Brad Figg brad.f...@canonical.com http://www.canonical.com
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
