Meeting Minutes

IRC Log of the meeting.

Meeting minutes.


20110405 Meeting Agenda

Release Metrics

Release Meeting Bugs (6 bugs, 8 Blueprints)

Beta 2 Milestoned Bugs (64 across all packages (up 5))

  • 2 linux kernel bugs (down 2)
  • 0 linux-ti-omap bugs (no change)
  • 0 linux-meta-ti-omap bug (no change)

Release Targeted Bugs (272 across all packages (down 2))

  • 27 linux kernel bugs (up 5)
  • 0 linux-ti-omap bugs (no change)
  • 0 linux-meta-ti-omap bug (no change)

Milestoned Features

  • 6 blueprints (Including HWE Blueprints)

Maverick Updates Bugs

changed to only reflect linux package bugs

  • 6 Linux Bugs

Lucid Updates Bugs

changed to only reflect linux package bugs

  • 15 Linux Bugs

Bugs with Patches Attached:87 (up 3)

Blueprints: Natty Bug Handling

  • My plan for these is to have this blueprint completed prior to the release of Beta 2. As such, it is a high priority for me and I will be focusing on those items that are still outstanding for this week.

Status: General Natty

Last week we uploaded the 2.6.38-8.40 kernel which is based on the latest upstream stable v2.6.38.2. As Kernel Freeze is April 14, I plan to do another upload today for the patches queued in master-next and then a final upload before kernel freeze on Mon April 11 so that our builds are complete by the 14th. After kernel freeze we will transition to our SRU policy when submitting and accepting patches. See:

Any uploads beyond kernel freeze will likely have to resolve a critical issue, otherwise, it’ll have to wait for the first round of SRU’s.

Status: Stable Kernel Team

Last week we completed the Verification phase of the current cycle and entered the Testing Phase.
When testing is completed, the packages can be published.

This has the next upload to proposed and the start of the next cycle to be on 4/29.

Since there are a lot of changes in the Maverick kernel from upstream stable patches, and because there
are people interested in verifying specific fixes, we will soon produce a kernel and upload it to -proposed
for Maverick. This is not on the schedule, and is not part of a normal kernel cycle. We will replce it
with a kernel containing additional fixes for th enext official cycle.

Security & bugfix kernels – Maverick/Lucid/Karmic/Hardy/Dapper

Package    Upd/Sec    Proposed    TiP    Verified   
dapper linux-source-2.6.15    2.6.15-57.94    2.6.15-57.95    0    0   
karmic linux-ec2    2.6.31-308.28    2.6.31-308.29    1    1   
— linux    2.6.31-23.74    2.6.31-23.75    1    1   
lucid linux-ec2    2.6.32-314.27    2.6.32-315.28    5    5   
— linux-ports-meta    0    0   
— linux-meta-lts-backport-maverick    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-30.29    2.6.32-31.31    0    0   
— linux-firmware    1.34.4    1.34.7    1    1   
— linux    2.6.32-30.59    2.6.32-31.60    5    5   
— linux-meta    0    0   
— linux-meta-ec2    0    0   
maverick linux-backports-modules-2.6.35   

Incoming Bugs: Regressions

Incoming Bugs
574 Natty Bugs (up 121)
1252 Maverick Bugs (up 14)
1061 Lucid Bugs (up 8)
Current regression stats (broken down by release):


  • 46 maverick bugs (up 4)
  • 77 lucid bugs (up 1)
  • 6 karmic bugs (down 1)
  • 0 hardy bugs (no change)


  • 287 natty bugs (up 70)
  • 246 maverick bugs (up 7)
  • 222 lucid bugs (no change)
  • 38 karmic bugs (no change)
  • 2 hardy bugs (no change)


  • 15 natty bugs (up 5)
  • 0 maverick bugs (no change)
  • 0 lucid bugs (no change)
  • 0 karmic bug (no change)

Incoming Bugs: Bug day report

My effort last week was a bit different as I did not advertise the bug day in the same way I normally do. In this last case,
I directly pinged those parties that have provided the majority of the bug triage during our normally advertised bug days.
I also pressed those who continually ask me to review bugs (other than through the normal channels) to asist us in triaging
those bugs that they are bringing to my attention. It doesn’t seem to have had the desired effect, so I’ll be going back to
the e-mail and blog/tweet for advertisement of our bug days. The next bug day will be next Tuesday. We will be focusing on
regression-release bugs in all status starting with the new state.

Triage Status

I didn’t do much in the way of triage for the past week, nor did I interact heavily with our triagers due to the need to plan
for UDS a bit and to get my schedule in order for all of the tasks yet to do in this cycle. This week will likely be the same
as I will be working ot implement the plan and close out my remaining tasks while drafting blueprint information for the O UDS.

Open Discussion or Questions

  • (kamal) thanks ogasawara for the ubuntu-oneiric.git repo … the Oneiric 2.6.39 kernel builds and works great on Natty!