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

• 2011-01-31
  • ?

Features and Bugs Summary

• Release bugs - 2011-02-06* (last snapshot 2011-01-31)

• Bugs to consider for stable release updates

10.04.2 Long Term Support Status

Planned Release Date: February 17, 2011

• Milestoned Bug Summary

  • 2 Critical/High unresolved remain milestoned against 10.04.2

Release Team

• image status? any concerns? - pitti, cjwatson
• language pack status?
• final image ETA?

Hardware Certification

• status of full certification on 10.04.2 images? - ara

Quality Assurance

• any sniff testing of images? - marjo

Foundations

• Unresolved Critical/High Milestoned Bugs

  • 635273:Building debs with SWIG libraries do not work

• Resolved Critical/High Milestoned Bugs

  • 579858:mount segfault on shutdown when unmounting autofs mountpoint (has patch)

  • 591207:Casper's USB update-initramfs shim should look for initrd.img in /boot

  • 607657:Lucid point release installer must support LTS backported Kernels

  • 628630:CD/DVD installs not rebooting system or promting user to press enter to reboot when doing "Install Ubuntu"

Server

• Unresolved Critical/High Milestoned Bugs
  • None
• Resolved Critical/High Milestoned Bugs

  • 458637: Windows Live Sign-In assistant prevents samba from accessing Windows 7 shares

Desktop

• Unresolved Critical/High Milestoned Bugs

  • 522538 : gwibber-service crashed with error in connect()

Kernel

• Unresolved Critical/High Milestoned Bugs
  • None

Stable Release Updates

• sconklin - tracking bug numbers?
• Recent
  • Lucid images moved to -proposed on 1/? see: Bug: ?
  • Maverick moved to -proposed on 1/? see: Bug: ?
• Next
  • Updates to Hardy, Dapper will be worked on during 10.04.2 freeze cycle.
  • Security - ??

• 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

Quality Assurance

• Current SRU status

Hardware Certification

• SRU Testing for Lucid and Maverick

  • Latest Test Results

  • Test Results Archive

Kernel

• -updates milestoned

  • 635344:After my CD-Rom is ejected, the tray will instantly retract. [on list since 2010-11-26]

• critical/high release specific -updates milestone:
  • TBR

Foundations

• critical/high release specific -updates milestone:
  • TBR

Server

• Server tracked bugs

• critical/high release specific -updates milestone:
  • ?

ARM

Desktop

• critical/high lucid-updates milestone:

  • 439448: Visual corruption affecting several panel applets

  • 525807:[upstream] [3.2.1] OOo Slide Show and Fullscreen modes - not full screen under compiz - pending OOo maintainer

  • 459647:Cannot change mouse cursor theme when compiz is enabled - jeopardizes stability, so may declare permanently broken in lucid.

OEM

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

Support

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

IRC Meeting Log

• mootbot logs available at

  • http://www.novarata.net/mootbot/ubuntu-meeting.log.20110207_1000.html

  • http://www.novarata.net/mootbot/ubuntu-meeting.20110207_1000.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.