Ubuntu Kernel Team meeting minutes, 2010-05-18

Tue May 18 17:57:52 UTC 2010

[The minutes below are also available in the Ubuntu wiki at this URL:
 http://wiki.ubuntu.com/KernelTeam/Meeting/2010-05-18 ]

= Meeting Minutes =
[[http://irclogs.ubuntu.com/2010/05/18/%23ubuntu-meeting.txt|IRC Log of
the meeting.]]

== Agenda ==
[[https://wiki.ubuntu.com/KernelTeam/Meeting#Meeting: Tues, 18 May,
2010|20100518 Meeting Agenda]]

=== Outstanding actions from last meeting ===
None

=== New Bodies ===

A quick introduction to several new people joining the Team including:
Mathieu Poirier (mpoirier), Lee Jones (lag), and Chris Van Hoof
(vanhoof).

=== UDS/Blueprints ===

With UDS behind us its time to get all the discussion into the
blueprints, to get the outcomes distilled out, and the work items onto
the blueprint whiteboards.  Please ensure that your blueprint is
assigned to someone in the team, that it is targetted to a sensible
Maverick milestone, that it has a priority set, and that it has a Series
Goal of Maverick.

We will start to expect status reporting for the open blueprints from
next meeting.  If you are an assignee, you will be expected to report
progress or delegate someone to do so.  Please ensure your blueprint is
shown on the release status page (url below), and if not talk to
ogasawara or apw so we help sort it out.

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

=== Status: Maverick overall (ogasawara) ===

For those who haven't yet heard, we'll be targetting the 2.6.35 kernel
for Maverick.

We'll be rebasing to 2.6.34 final today and uploading.  Next will be to
get the changes from the UDS config review integrated as well as changes
noted from the UDS delta review.

For any brave souls wanting to try Maverick's current kernel, it's
available at https://edge.launchpad.net/ubuntu/+source/linux/2.6.34-2.9

=== Status: Security & Bugfix Kernels (smb/gnarl/sconklin) ===
   {{{
Dapper:      2.6.15-55.83  (updates)
Hardy:       2.6.24-27.69  (updates)
Intrepid:    --- End of Support ---
Jaunty:      2.6.28-18.60  (updates)
Karmic:      2.6.31-21.59  (updates)
 - mvl-dove  2.6.31-213.27 (updates)
 - fsl-imx51 2.6.31-111.27 (updates)
 - ec2       2.6.31-306.14 (updates)
Lucid:       2.6.32-22.33  (updates)
 - mvl-dove  2.6.32-204.16 (release)
 - fsl-imx51 2.6.31-607.13 (release)
 - ti-omap   2.6.33-500.6  (release)
 - qcm-msm   2.6.31-800.2  (release)
 - ec2       2.6.32-305.9  (release)
}}}

Currently working on security updates. Following that there are quite a
few stable updates for Lucid.  Given the number of topic branches I
expect pain.

Some discussion on whether there was a work item already for the
backport
of the Lucid fsl-imx51 tree to Karmic.  Action on smb to get one made.

=== Release Metrics (JFo) ===
   {{{
Release Meeting Bugs (none yet)
---
Release Targeted Bugs (none yet)
 * 0 linux kernel bugs
 * 0 linux-fsl-imx51 bugs
 * 0 linux-ec2 bug
 * 0 linux-mvl-dove bugs
---
Milestoned Features -
 * 15 blueprints
---
Bugs with Patches Attached:132
https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch-on
Breakdown by status:
http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/
}}}

I plan to do a review of patch attached bugs this week hopefully that
number will drop drastically

=== Incoming Bugs: Regressions ===
   {{{
Incoming Bugs
1134 Lucid Bugs
Current regression stats (broken down by release):
---- regression-potential ----
  * 317 lucid bugs
---- regression-update ----
  * 26 lucid bugs
  * 9 karmic bugs
  * 5 jaunty bugs
  * 2 intrepid bugs
  * 2 hardy bug (up 1)
---- regression-release ----
  * 141 lucid bugs
  * 52 karmic bugs
  * 21 jaunty bugs
  * 10 intrepid bugs
  * 3 hardy bugs
---- regression-proposed (no change) ----
  * 1 lucid bug
  * 1 karmic bug
}}}

please note the large amount of regression-release bugs for Lucid

It was noted and agreed that Intrepid is not longer required as it is
now off support.

apw noted that we need to remember to focus on lucid regression-release
bugs in the early cycle.  This is an LTS and we care as we have to have
this baby about forever.

smb noted that we need to get the current batch into -updates before we
start a new cycle of bug fixing.

manjo asked whether we could just move bugs over to Maverick, but as
this is an LTS we do need to focus on them and indeed have 3 months or
so of loose SRU policy designed to aiding getting those fixes in.

=== Incoming Bugs: Bug day report (JFo) ===

Bug Days will start back after next week. I plan to send out an
announcement for the next one early in the week with a reminder the
business day before.

=== Open Discussion or Questions: Anyone have anything? ===

kamal reported that some of his Dell Studio 155x patches have been
accepted to -stable.  We shall await those via stable shortly.

manjo asked if there were any SRU policy changes for Maveric.  Other
than the return to the normal non-LTS policy arrangement there is
nothing planned.

apw noted that it seems the SRU message is not getting out, we should
have had a session on it at UDS.

=== ACTIONS ===

 * ogasawara to email out reminder regarding blueprint disposition
 * smb to add work item for updating karmic fsl-imx51 in line with lucid