Meeting Minutes

IRC Log of the meeting.

Meeting minutes.


20100928 Meeting Agenda

ARM Status

lag chases snakes in his sleep.

Release Metrics:

please note that the statistics are for a 2 week time period:

Release Meeting Bugs (5 bugs, 9 Blueprints)

Release Milestoned Bugs (26 across all packages (down 45))

  • 1 linux kernel bugs (no change)
  • 0 linux-fsl-imx51 bugs (no change)
  • 0 linux-ec2 bugs (no change)
  • 0 linux-mvl-dove bugs (no change)
  • 0 linux-ti-omap bugs (no change)
  • 0 linux-meta-ti-omap bug (no change)

Release Targeted Bugs (144 across all packages (down 51))

  • 13 linux kernel bugs (up 6)
  • 0 linux-fsl-imx51 bugs (down 1)
  • 0 linux-ec2 bugs (down 1)
  • 2 linux-mvl-dove bugs (down 1)
  • 0 linux-ti-omap bugs (down 1)
  • 0 linux-meta-ti-omap bug (no change)

Milestoned Features

  • 13 blueprints (Including HWE Blueprints)

Bugs with Patches Attached:121 (down 2)

Blueprint: kernel-maverick-bug-handling

Remaining items postponed. To be discussed at UDS.

Status: Maverick

The Maverick Release Candidate comes out this Thurs Sept 30 and the Release Team has stopped processing upload requests for the Ubuntu 10.10 Release Candidate. See for more info.

We’ve been queuing patches for Maverick SRU which includes the latest and stable updates. We are also planning a 0-day kernel upload which has been documented at bug 647071 . I’d finally like to point out that we have closed out all Maverick blueprint work items \o/. We have been and will be below the trend line for the entire Maverick cycle for our overall burn down chart.

Security & bugfix kernels – Lucid/Karmic/Jaunty/Hardy/Others

   Upd./Sec.    Proposed    TiP    Verified   
Dapper: Kernel    2.6.15-55.88            
Hardy: Kernel    2.6.24-28.79            
= LRM            
Jaunty: Kernel    2.6.28-19.65            
Karmic: Kernel    2.6.31-22.65    2.6.31-22.66    5    1/ 4 (+ 1)   
= mvl-dove    2.6.31-214.30    2.6.31-214.32    5    1/ 4 (+ 1)   
= fsl-imx51    — retired —            
= ec2    2.6.31-307.17    2.6.32-307.18    5    1/ 4 (+ 1)   
Lucid: Kernel    2.6.32-25.44            
= LBM    2.6.32-25.23    2.6.32-25.24    1    0/ 1   
= mvl-dove    2.6.32-209.25    2.6.32-211.27    0      
= fsl-imx51    2.6.31-608.19    2.6.31-608.20    0      
= ti-omap    2.6.33-502.10    (in progress)         
= ec2    2.6.32-308.16    (in progress)         
  • The Lucid proposed kernel has been moved to updates. Topic branch updates
    which are rebased against this have or will be uploaded.
  • Karmic fsl-imx51 has been retired.

Incoming Bugs: Regressions

629 Maverick Bugs (up 96)

978 Lucid Bugs (down 58)

Current regression stats (broken down by release):


  • 320 maverick bugs (up 48)
  • 160 lucid bugs (down 10: to be converted to regression-release)


  • 55 lucid bugs (up 8)
  • 7 karmic bugs (no change)
  • 4 jaunty bugs (no change)
  • 0 hardy bugs (no change)


  • 170 lucid bugs (down 11)
  • 36 karmic bugs (down 1)
  • 17 jaunty bugs (down 1)
  • 2 hardy bugs (down 1)


  • 6 lucid bugs (down 1)
  • 1 karmic bug (no change)
    Jaunty bugs will be closed and removed from this list once Jaunty EOLs

Incoming Bugs: Bug day report

I’ve put off the bug day till next week due to the past week of traveling. The next Kernel Community Bug Day will be on bugs in the New status improperly.

There are curently about 1500 bugs in the New state. My guess is that many of these are the result of people simply marking Expired bugs to new without doing the requested tasks. The majority should move to Invalid or Triaged depending on the reporters interaction.

We will continue to have the Team Bug Day to address the Top 50 list as half days on Friday and Monday unless someone has an objection.

Reviewers, please take a look at your needs-review lists and help us keep the process moving. There are several lists that are not getting a look.
Please also take ownership of your bugs as you work them so we can get them fixed or otherwise off the list. There are a number in need of love.
There are several subsystems owned by all that need to be reviewed for inclusion in our top 50 list.

Triage Status

There was a surprising amount of attendance in the UHS Kernel Bugs talk and a number of the participants were actively listening, so I hope this means that we will have some good buy in on the process form these folks should any of them come on board with hardware/kernel bugs.
Since I was traveling, I have not had the chance to interact with the community over the past week.

Open Discussion or Questions: Raise your hand to be recognized

Nothing this week.