Ubuntu Kernel Team Meeting Minutes - 2011-03-15
Brad Figg
brad.figg at canonical.com
Tue Mar 15 17:49:14 UTC 2011
= Meeting Minutes =
[[http://irclogs.ubuntu.com/2011/03/15/%23ubuntu-meeting.txt|IRC Log of the meeting.]]
<<BR>>
[[http://voices.canonical.com/kernelteam|Meeting minutes.]]
== Agenda ==
[[https://wiki.ubuntu.com/KernelTeam/Meeting#Tues, 15 Mar, 2011|20110315 Meeting Agenda]]
=== ARM Status ===
* The Kernel team has a new ARM developer.
* The existing MVL Dove regression has been resolved and a new package will be uploaded.
=== Release Metrics ===
Release Meeting Bugs (9 bugs, 9 Blueprints)
==== Beta 1 Milestoned Bugs (104 across all packages (down 2)) ====
* 8 linux kernel bugs (up 2)
* 0 linux-ti-omap bugs (no change)
* 0 linux-meta-ti-omap bug (no change)
==== Release Targeted Bugs (293 across all packages (down 11)) ====
* 22 linux kernel bugs (up 2)
* 0 linux-ti-omap bugs (no change)
* 0 linux-meta-ti-omap bug (no change)
==== Milestoned Features ====
* 7 blueprints (Including HWE Blueprints)
==== Maverick Updates Bugs ====
* 71 Linux Bugs (up 2)
==== Lucid Updates Bugs ====
* 94 Linux Bugs (no change)
==== Bugs with Patches Attached:80 (up 1) ====
* [[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: Natty Bug Handling ===
* Andy and I will review the remaining items to see if any will be postponed.
<<BR>>
Additionally, I will be finishing up several that have been put off of completion due to other priorities taking precedence.
=== Status: General Natty ===
The natty kernel is now at v2.6.38-6.34 (v2.6.38-rc8 based). We have had some instability due to compiler changes from Linaro, but seem to be coming out the other side. v2.6.38 dropped today and kernels are in test prior to upload. We remain
concentrated on bug squashing for Natty. One area of concern is an interaction between vesafb and drmfb during boot, in some cases we are triggering gpu hangs; a prototype startup wherein we load vesafb later
is in test. We are closing in on Beta-1 freeze which is a week on thursday.
=== Status: Stable Kernel Team (sconklin / bjf) ===
* This week is the start of yet another stable kernel release cycle. I'm in the process of getting git repos in shape and packages put together.
* A request for feedback has gone out regarding the kernel SRU workflow. The proposal can be found at: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
=== Security & bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper (sconklin / bjf) ===
|| Package || Upd/Sec || Proposed || TiP || Verified ||
|| || || || || ||
|| dapper linux-source-2.6.15 || 2.6.15-55.93 || 2.6.15-57.94 || 0 || 0 ||
|| --- linux-meta || 2.6.15.56 || 2.6.15.57 || 0 || 0 ||
|| --- linux-backports-modules-2.6.15 || 2.6.15-55.13 || 2.6.15-57.15 || 0 || 0 ||
|| || || || || ||
|| hardy linux-meta || 2.6.24.28.30 || 2.6.24.29.31 || 0 || 0 ||
|| --- linux || 2.6.24-28.86 || 2.6.24-29.87 || 1 || 1 ||
|| || || || || ||
|| karmic linux-ec2 || 2.6.31-307.27 || 2.6.31-308.28 || 2 || 2 ||
|| --- linux-ports-meta || 2.6.31.22.18 || 2.6.31.23.19 || 0 || 0 ||
|| --- linux || 2.6.31-22.73 || 2.6.31-23.74 || 1 || 1 ||
|| --- linux-backports-modules-2.6.31 || 2.6.31-22.24 || 2.6.31-23.25 || 0 || 0 ||
|| --- linux-meta || 2.6.31.22.35 || 2.6.31.23.36 || 0 || 0 ||
|| --- linux-meta-ec2 || 2.6.31.307.6 || 2.6.31.308.7 || 0 || 0 ||
|| || || || || ||
|| lucid linux-ports-meta || 2.6.32.29.22 || 2.6.32.30.23 || 0 || 0 ||
|| --- linux-mvl-dove || 2.6.32-211.27 || 2.6.32-214.30 || 20 || 20 ||
|| --- linux-meta-mvl-dove || 2.6.32.209.12 || 2.6.32.214.15 || 0 || 0 ||
|| --- linux-backports-modules-2.6.32 || 2.6.32-29.28 || 2.6.32-30.29 || 0 || 0 ||
|| --- linux-firmware || 1.34.4 || 1.34.7 || 0 || 0 ||
|| --- linux || 2.6.32-29.58 || 2.6.32-30.59 || 3 || 3 ||
|| --- linux-fsl-imx51 || 2.6.31-608.22 || 2.6.31-608.25 || 0 || 0 ||
|| --- linux-meta || 2.6.32.29.35 || 2.6.32.30.36 || 0 || 0 ||
|| || || || || ||
|| maverick linux-ports-meta || 2.6.35.27.21 || 2.6.35.28.21 || 0 || 0 ||
|| --- linux-mvl-dove || || 2.6.32-414.30 || 9 || 9 ||
|| --- linux-meta-mvl-dove || || 2.6.32.414.4 || 0 || 0 ||
|| --- linux-firmware || 1.38.4 || 1.38.5 || 1 || 1 ||
|| --- linux || 2.6.35-27.48 || 2.6.35-28.49 || 4 || 4 ||
|| --- linux-backports-modules-2.6.35 || 2.6.35-27.18 || 2.6.35-28.19 || 0 || 0 ||
|| --- linux-meta || 2.6.35.27.35 || 2.6.35.28.36 || 0 || 0 ||
|| || || || || ||
=== Status: HW Cert. Team ===
This week we finised testing both the Maverick and the Lucid kernel. Results are publicly available:
All the 75 systems passed the SRU tests (the minor errors are problems with the script themselves).
So, from our side, they are good to go.
We updated the tracking bugs with this information as well.
=== Incoming Bugs: Regressions ===
Incoming Bugs
297 Natty Bugs (up 72)
1218 Maverick Bugs (up 18)
1034 Lucid Bugs (up 3)
Current regression stats (broken down by release):
==== regression-update ====
* 40 maverick bugs (no change)
* 74 lucid bugs (down 2)
* 7 karmic bugs (no change)
* 0 hardy bugs (no change)
==== regression-release ====
* 131 natty bugs (up 37)
* 240 maverick bugs (up 6)
* 221 lucid bugs (no change)
* 38 karmic bugs (no change)
* 2 hardy bugs (no change)
==== regression-proposed ====
* 5 natty bugs (up 4)
* 0 maverick bugs (no change)
* 1 lucid bugs (up 1)
* 0 karmic bug (no change)
=== Incoming Bugs: Bug day report ===
Last week's bug day was a success. We had several individuals helping to triage
new state bugs and we got a number of them triaged and into the proper status.
The next bug day will be next Tuesday. The focus will be on bugs in the confirmed state.
=== Triage Status ===
There is always tremendous interest in having me look at a particular bug here and there.
I am still working to get these interested parties to approach me in the pulblic channel
versus currently getting pinged in private windows.
We have had some further interest in working bugs from individuals geared toward beginning
device driver and module work. As much as it pains me, we had to explain that bugs were
likely not the best way to go to get into module development. :-)
=== Open Discussion or Questions: ===
Welcome back ogasawara !!!
--
Brad Figg brad.figg at canonical.com http://www.canonical.com
More information about the ubuntu-devel
mailing list