||<>|| = Stable Release Team Agenda = * '''PURPOSE:''' collaborate on stable release updates and long term support point releases * '''FREQUENCY:''' bi-weekly meeting * '''ACTIVE RELEASES:''' Maverick, Lucid, Karmic, Hardy, Dapper * '''RELEASE LIFECYCLE STATUS:''' https://wiki.ubuntu.com/Releases == Pending Actions == * 2010-02-14 * [skaet] add tracking of public bugs of interest from Support team to agenda to track. - IN PROGRESS, working with Martin * [skaet] implement some good suggestions received after meeting to improve meeting efficiency: (1) send out pointer to agenda day before meeting and encourage teams to post status in agenda itself, (2) create new business section, and encourage teams to post proposals there for consideration in meeting, (3) encourage teams to prepare status update in advance to cut/paste, rather than typing as go. - TO DO, need to resolved timing conflict with Release meeting follow up on Fridays. * 2010-03-14 * [bjf, sconklin] update status for this week on this https://wiki.ubuntu.com/ReleaseTeam/Meeting/2011-03-14-SR. * [martins] top 5 public bugs of concern? * [skaet] work with zul, Daviey, pitti to track Bug:651875 * [all] review 10.04.3 proposed date and flag any concerns at next meeting * [all] review flow of agenda, and get with skaet off line if have ideas for improvements ## == Features and Bugs Summary == ## ## copied/adjusted from https://wiki.ubuntu.com/BrianMurray/bugstats/ReleaseBugStats ## * Release bugs - 2011-02-06* (last snapshot 2011-01-31) ## || '''Release''' || '''Bugs Open''' || '''Critical''' || '''High''' || '''New''' || ## || Maverick || [[http://bugs.launchpad.net/ubuntu/maverick/+bugs|438 (+15)]] || [[http://bugs.launchpad.net/ubuntu/maverick#/+bugs?field.importance=Critical|4 (-1)]] || [[http://bugs.launchpad.net/ubuntu/maverick/+bugs?field.importance=High|66 (+1)]] || [[http://bugs.launchpad.net/ubuntu/maverick/+bugs?field.status=New|101 (-1)]] || ## || Lucid || [[http://bugs.launchpad.net/ubuntu/lucid/+bugs|656 (+12)]] || [[http://bugs.launchpad.net/ubuntu/lucid/+bugs?field.importance=Critical|3 (-1)]] || [[http://bugs.launchpad.net/ubuntu/lucid/+bugs?field.importance=High|112 (+1)]] || [[http://bugs.launchpad.net/ubuntu/lucid/+bugs?field.status=New|178 (+2)]] || ## || Karmic || [[http://bugs.launchpad.net/ubuntu/karmic/+bugs|317 (+10)]] || [[http://bugs.launchpad.net/ubuntu/karmic/+bugs?field.importance=Critical|2 (0)]] || [[http://bugs.launchpad.net/ubuntu/karmic/+bugs?field.importance=High|39 (+1)]] || [[http://bugs.launchpad.net/ubuntu/karmic/+bugs?field.status=New|117 (0)]] || ## || Hardy || [[http://bugs.launchpad.net/ubuntu/hardy/+bugs|487 (+8)]] || [[http://bugs.launchpad.net/ubuntu/hardy/+bugs?field.importance=Critical|0 (0)]] || [[http://bugs.launchpad.net/ubuntu/hardy/+bugs?field.importance=High|64 (0)]] || [[http://bugs.launchpad.net/ubuntu/hardy/+bugs?field.status=New|186 (0)]] || ## || Dapper || [[http://bugs.launchpad.net/ubuntu/dapper/+bugs|226 (+5)]] || [[http://bugs.launchpad.net/ubuntu/dapper/+bugs?field.importance=Critical|1 (0)]] || [[http://bugs.launchpad.net/ubuntu/dapper/+bugs?field.importance=High|14 (0)]] || [[http://bugs.launchpad.net/ubuntu/dapper/+bugs?field.status=New|73 (+1)]] || ## * Bugs to consider for stable release updates ## || '''Release''' || '''Patches''' || '''Fixed elsewhere''' || '''Regression potential ''' || '''-update target ''' || '''Nominated''' || ## || Maverick || [[https://bugs.launchpad.net/ubuntu/maverick/+patches|99]] || [[ https://bugs.launchpad.net/ubuntu/maverick/+bugs?field.status_upstream=resolved_upstream| 108]] || [[https://bugs.launchpad.net/ubuntu/maverick/+bugs?field.tag=regression-potential|2/6]] || [[https://bugs.launchpad.net/ubuntu/+bugs?&field.milestone:list=27564|8/30]] || [[https://bugs.launchpad.net/ubuntu/maverick/+nominations|437]] (459) || ## || Lucid || [[https://bugs.launchpad.net/ubuntu/lucid/+patches|157]] || [[ https://bugs.launchpad.net/ubuntu/lucid/+bugs?field.status_upstream=resolved_upstream| 149]](155) || [[ https://bugs.launchpad.net/ubuntu/lucid/+bugs?field.tag=regression-potential | 4/8 ]] ## || [[ https://bugs.launchpad.net/ubuntu/+bugs?&field.milestone:list=21448 | 15/43]] || [[ https://bugs.launchpad.net/ubuntu/lucid/+nominations | 1054]] (1087)|| ## || Karmic || [[https://bugs.launchpad.net/ubuntu/karmic/+patches|95]] || [[ https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.status_upstream=resolved_upstream| 64]](67) || [[ https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.tag=regression-potential | 0/0 ]] || [[ https://bugs.launchpad.net/ubuntu/+bugs?&field.milestone:list=12716 | 5/16 ]] || [[https://bugs.launchpad.net/ubuntu/karmic/+nominations | 915 ]] (929)|| ## || Hardy || [[https://bugs.launchpad.net/ubuntu/hardy/+patches|164]] || [[ https://bugs.launchpad.net/ubuntu/hardy/+bugs?field.status_upstream=resolved_upstream| 127]](129) || [[ https://bugs.launchpad.net/ubuntu/hardy/+bugs?field.tag=regression-potential | 0/0 ]] || [[https://bugs.launchpad.net/ubuntu/+bugs?&field.milestone:list=34695 | 0/0 ]] || [[ https://bugs.launchpad.net/ubuntu/hardy/+nominations | 328 ]] (333)|| ## || Dapper || [[https://bugs.launchpad.net/ubuntu/dapper/+patches|53]] || [[ https://bugs.launchpad.net/ubuntu/dapper/+bugs?field.status_upstream=resolved_upstream|70]](70) || [[ https://bugs.launchpad.net/ubuntu/dapper/+bugs?field.tag=regression-potential | 0/0 ]]|| [[ https://bugs.launchpad.net/ubuntu/+bugs?&field.milestone:list=135 | 1/1 ]] || [[ https://bugs.launchpad.net/ubuntu/dapper/+nominations | 74 ]] (76) || == Long Term Support Status == * 10.04.3 * ~+'''''Estimated'' 10.04.3 Release Date: July 14, 2011'''+~ * any known issues/conflicts? please raise. * Milestoned Bug Summary * [[https://bugs.launchpad.net/ubuntu/lucid/+bugs?field.milestone=30509| 1 Critical/ 4 High unresolved ]] milestoned against 10.04.3 * End of Life - Karmic, Hardy-Desktop * Just a reminder that April 2011 will see end of life of Karmic Koala (9.10), and Hardy Heron (8.04) Desktop. Dapper Drake (6.06) Server will end of life in June 2011. * https://wiki.ubuntu.com/Releases == Stable Release Updates - Kernel - bjf/sconklin == * Existing Process Documentation: https://wiki.ubuntu.com/StableReleaseUpdates * Existing Kernel SRU Process: https://wiki.ubuntu.com/KernelTeam/KernelUpdates * New Kernel SRU Process being piloted: https://wiki.ubuntu.com/Kernel/StableReleaseCadence * Overall SRU Status: http://people.ubuntu.com/~ubuntu-archive/pending-sru.html ## tracking bug links: https://kernel-tools.canonical.com/srus.html * A new kernel sru cadence cycle is starting this week. We are just a little behind schedule due to the previous cycle and the fact that the kernel stable team was part of a sprint last week. === Quality Assurance - marjo === * [[http://reports.qa.ubuntu.com/reports/sru/latest.html|Current SRU status]] === Hardware Certification - ara === * SRU Testing for Lucid and Maverick * [[http://people.canonical.com/~hwcert/sru-testing/current|Latest Test Results]] * [[http://people.canonical.com/~hwcert/sru-testing/|Test Results Archive]] === Stable Release Updates - pitti === * New Recruit - Clint Byrum - SpammapaS * Question: * Any SRU candidates about to expire? * Any specific concerns? == OEM - vanhoof == * Question: Any bugs that need to be worked on in next two weeks that should be SRU candidates? == Support - martins == * Question: Any escalation bugs that need to be worked on in next two weeks that should be SRU candidates? == New Business - ? == * zul: Highlighted bug: 651875 waiting on TB approval (update bind from 9.7.0 to 9.7.3) * skaet: reworking agenda for this meeting - input welcome. = IRC Meeting Log = * mootbot logs available at * http://www.novarata.net/mootbot/ubuntu-meeting.log.20110314_1002.html * http://www.novarata.net/mootbot/ubuntu-meeting.20110314_1002.html ## = ACTIONS = ## * [marjo] follow up with pitti on SRU process tweaks raised in meeting. ## * [skaet] add tracking of public bugs of interest from Support team to agenda to track. ## * [skaet] implement some good suggestions received after meeting to improve meeting efficiency: (1) send out pointer to agenda day before meeting and encourage teams to post status in agenda itself, (2) create new business section, and encourage teams to post proposals there for consideration in meeting, (3) encourage teams to prepare status update in advance to cut/paste, rather than typing as go.