2010-12-06-SR

Differences between revisions 118 and 120 (spanning 2 versions)
Revision 118 as of 2010-11-23 01:55:20
Size: 10275
Editor: 99-191-111-134
Comment:
Revision 120 as of 2010-12-06 04:08:42
Size: 9420
Editor: 99-191-111-134
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was copied from ReleaseTeam/Meeting/2010-11-22-SR
Line 12: Line 13:
 * none (first meeting after all ;) )  * 2010-11-22
  * [cjwatson, apw, Keybuk, azul] - to come up with proposal to handle upstart interaction/bug 642555
  * [victorp] look at adding hardware cert reports with architectures as one of the pieces of info tracked for SRU meeting
  * [pedro, marjo] - look at adding regression test report as one of the pieces of info tracked for SRU meeting.
  * [victorp, pedro, bjf, sconklin, skaet] to set date for next target SRU release. We'll be skipping Dec. 2.
  * [skaet, victorp, bjf, pitti] - meet to discuss SRU release of maverick post hardware cert testing results
  * [skaet] publish meeting conventions and discuss pre-work expectations with individual leads, so we can get this a little more efficient.
Line 87: Line 95:
  * ''[ScottK via IRC on ubuntu-devel 11/22] - Tech board has approved putting KDE point releases into -updates. Kubuntu will update to KDE 4.4.5 (and 4.4.7 for kdepim) for 10.04.2''   * Kubuntu will update to KDE 4.4.5 (and 4.4.7 for kdepim) for 10.04.2 - update?
Line 91: Line 99:

  * Recent
    * Lucid shipped on 11/30
    * Maverick shipped on 12/02 (?)
    * Security Update shipped on 12/xx (?)

  * Next
    * Lucid - 12/??
    * Maverick - 12/??
    * Security - 12/??
Line 98: Line 116:
  Notes:
  * ''[cjwatson] sponsored 671097 and milestoned this for server team''
  * ''[cjwatwon] bug 554172, don't know a good fix. Need discussion on solutions, see action items''
  * ''[victorp] certification testing for lucid done on ubuntu for netbooks, desktop edition (laptops and pc) sevrers, i386 and amd64) testing link: http://people.canonical.com/~cr3/hw-testing/lucid-proposed.html''
  * ''[skaet] decision to ship lucid SRU update without regression testing formalized, some concern on it not baking for a week - reverts not reseting -proposed is the concern''
  * ''[skaet] shipping maverick SRU will be decided after we get result of SRU testing - action taken to call meeting to discuss tomorrow''
Line 109: Line 120:
  * what is the status of the regression automation infrastructure?

  * Current SRU status:
    * http://reports.qa.ubuntu.com/reports/sru/latest.html

  * Questions:
  * [[http://reports.qa.ubuntu.com/reports/sru/latest.html|Current SRU status]]

  * Questions:
    * what is the status of the regression automation infrastructure?
Line 116: Line 125:
    * is there a report that details the regression run report for the current SRU kernel update? ''[pedro] will take an action to provide next time ''     * is there a report that details the regression run report for the current SRU kernel update? ''[pedro] took an action to provide this time ''
Line 123: Line 132:
  * what is the status of the hardware certification infrastructure automation?   * certification testing for lucid done on ubuntu for netbooks, desktop edition (laptops and pc) sevrers, i386 and amd64) testing link: http://people.canonical.com/~cr3/hw-testing/lucid-proposed.html''
Line 126: Line 135:
    * is there a report that illustrates the results of the last cerification run? ( is http://people.canonical.com/~fader/hw-testing/current.html still in use ) - ''[victorp] see http://people.canonical.com/~cr3/hw-testing/lucid-proposed.html, was request to add architectures, and extend to releases ''

  * Questions:
    * how much time should be allocated for automated certification run, in planning? (assuming no significant regression)
    * overview of schedule and window? Ara's calendar

  * Questions:
    * any adjustment to 2-day time allocated for automated certification run, in planning? (assuming no significant regression)
Line 156: Line 165:
   * Questions:
    * Should this link be updated? : https://wiki.ubuntu.com/ServerTeam/StableReleaseTracker -- ''[[zul] - this is obsolete''
    * Is this the official one? : http://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html -- ''[zul] - this is the one to use''
 * [[http://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html|Server tracked bugs]]

 * Questions:
Line 201: Line 209:
= IRC Meeting Log =
 * mootbot logs available at
   * http://www.novarata.net/mootbot/ubuntu-meeting.log.20101122_1002.html
   * http://www.novarata.net/mootbot/ubuntu-meeting.20101122_1002.html

= ACTIONS =
 * [cjwatson, apw, Keybuk, azul] - to come up with proposal to handle upstart interaction/bug 642555
 * [victorp] look at adding hardware cert reports with architectures as one of the pieces of info tracked for SRU meeting
 * [pedro, marjo] - look at adding regression test report as one of the pieces of info tracked for SRU meeting.
 * [victorp, pedro, bjf, skaet] to set date for next target SRU release. We'll be skipping Dec. 2.
 * [skaet, victorp, bjf, pitti] - meet to discuss SRU release of maverick post hardware cert testing results
 * [skaet] publish meeting conventions and discuss pre-work expectations with individual leads, so we can get this a little more efficient.
##= IRC Meeting Log =
## * mootbot logs available at
## * http://www.novarata.net/mootbot/ubuntu-meeting.log.20101122_1002.html
## * http://www.novarata.net/mootbot/ubuntu-meeting.20101122_1002.html
##
##= ACTIONS =

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

Actions from Last Meeting

  • 2010-11-22
    • [cjwatson, apw, Keybuk, azul] - to come up with proposal to handle upstart interaction/bug 642555
    • [victorp] look at adding hardware cert reports with architectures as one of the pieces of info tracked for SRU meeting
    • [pedro, marjo] - look at adding regression test report as one of the pieces of info tracked for SRU meeting.
    • [victorp, pedro, bjf, sconklin, skaet] to set date for next target SRU release. We'll be skipping Dec. 2.
    • [skaet, victorp, bjf, pitti] - meet to discuss SRU release of maverick post hardware cert testing results
    • [skaet] publish meeting conventions and discuss pre-work expectations with individual leads, so we can get this a little more efficient.

Features and Bugs Summary

  • Release-targeted bugs (snapshot 2010/11/17)

Release

Bugs Open

Critical

High

New

Maverick

333

2

55

66

Lucid

623

5

113

161

Karmic

283

3

39

115

Hardy

458

0

65

180

Dapper

211

1

14

67

10.04.2 Long Term Support Status

Planned Release Date: February 17, 2011

Kernel

  • Unresolved Important Bugs
    • 635344:After my CD-Rom is ejected, the tray will instantly retract. [sconklin] - need to determine if can come up with fix for RC and where fix needs to happen

Foundations

  • Unresolved Important Bugs
    • 563916:[details.so] No prompt for [S]kip or [M]anual recovery on server boot - [cjwatson] - release candiate, on list

    • 591207:Casper's USB update-initramfs shim should look for initrd.img in /boot - [cjwatson] - .1 attempt failed, will see if possible, ev to look at

    • 607657:Lucid point release installer must support LTS backported Kernels - [cjwatson] - release candiate, on list

    • 635273:Building debs with SWIG libraries do not work - [cjwatson] - under investigation.

Server

  • Unresolved Important Bugs
    • 671103:backport grub-legacy-ec2 from maverick to lucid - [cjwatson] - accepted for validation already - will go out as SRU

Desktop

  • Unresolved Important Bugs
    • 525807:[upstream] [3.2.1] OOo Slide Show and Fullscreen modes - not full screen under compiz - [pitti] - pending finding an OOo maintainer

    • 625280:SRU: xserver-xorg-video-geode 2.11.9-1 to Lucid and older supported releases - [pitti] - will investigate

    • 459647:Cannot change mouse cursor theme when compiz is enabled - [pitti] compiz has been going off/on - jeopardizes stability, so may declare permanently broken in lucid.

Kubuntu

  • Kubuntu will update to KDE 4.4.5 (and 4.4.7 for kdepim) for 10.04.2 - update?

Stable Release Updates

Quality Assurance

  • Current SRU status

  • Questions:
    • what is the status of the regression automation infrastructure?
    • This report still looks like its being run, can it be updated to reflect the current releases? see: http://people.ubuntu.com/~sbeattie/sru_todo.html

    • is there a report that details the regression run report for the current SRU kernel update? [pedro] took an action to provide this time

    • what has changed in terms of the bug validation over the last week for the current SRU proposed packages?
    • how many packages moved from proposed to updates/security in last week?

Hardware Certification

  • certification testing for lucid done on ubuntu for netbooks, desktop edition (laptops and pc) sevrers, i386 and amd64) testing link: http://people.canonical.com/~cr3/hw-testing/lucid-proposed.html

  • Current SRU status:
    • overview of schedule and window? Ara's calendar
  • Questions:
    • any adjustment to 2-day time allocated for automated certification run, in planning? (assuming no significant regression)

Kernel

  • Questions:
    • Which bugs that are being targetted for next SRU testing cycle?
    • Which kernels will need SRU testing?
    • What date will the kernel(s) be available for build? test?
    • Any security issues that may impact next cycle?
    • What is the priority list of SRU candidate bugs that will be worked on in next two weeks?

Security

  • Questions:
    • Any show stoppers likely which will cause kernel SRU release cycle to be skipped?
    • Any packages which need to have SRU bugs validated?
    • Any SRU candidate bugs against packages to be worked on in next two weeks?

Foundations

  • Questions:
    • Any packages which need to have SRU bugs validated?
    • Any SRU candidate bugs against packages to be worked on in next two weeks?

Server

  • Server tracked bugs

  • Questions:
    • Any packages which need to have SRU bugs validated?
    • Any SRU candidate bugs against packages to be worked on in next two weeks?

ARM

  • Questions:
    • Any packages which need to have SRU bugs validated?
    • Any SRU candidate bugs against packages to be worked on in next two weeks?

Desktop

  • Questions:
    • Any packages which need to have SRU bugs validated?
    • Any SRU candidate bugs against packages to be worked on in next two weeks?

Ubuntu One

  • Questions:
    • Any packages which need to have SRU bugs validated?
    • Any SRU candidate bugs against packages to be worked on in next two weeks?

Kubuntu

  • Questions:
    • Any packages which need to have SRU bugs validated?
    • Any SRU candidate bugs against packages to be worked on in next two weeks?

Derivatives

Linaro

  • Questions:
    • Any fixes that need to be released in maverick SRU?
    • Any SRU candidate bugs against packages to be worked on in next two weeks?

OEM

  • Question:
    • Any escalation bugs that need to be worked on in next two weeks that should be SRU?

ReleaseTeam/Meeting/2010-12-06-SR (last edited 2010-12-14 22:09:44 by eth3)