Quantal
Weekly Status
Links to overall status, burn down charts, and work item tracking can be found at the following:
- Overall Status
- Burn Down Charts
- Work Item Tracking
What was done engineering wise?
This week we rebased the Quantal kernel to the latest v3.5-rc7 upstream Linux kernel and uploaded. We also uploaded this to the ppa:ubuntu-x-swat/q-lts-backport PPA to facilitate testing of the 12.10 kernel in 12.04. Please test and let us know your results.
What's about to land that might impact the other teams and release as a whole?
We are anticipating an upstream v3.5-rc8 release. If it lands in time for Quantal Alpha-3 we intend to rebase and upload. Otherwise we'll wait to after Alpha-3.
The Canonical kernel team has also been sprinting this week. Given the projected upstream release dates for v3.5 and v3.6, we are still discussing if we'll stick with a v3.5 based kernel for Quantal or move to v3.6. We'll be sure to keep everyone posted on a final decision.
Summary of bugs working on by team (reasonably reliable)
1005832 - Intel wifi frequent disconnects
1013305 - Corrupted graphics NVidia 320M
1011828 - Session failed to laod with 12.10 kernel on 12.04 test
1013372 - unable to suspend with 3.4.0-4.9~precise1-generic 3.4.0
993506 - nvidia kernel module fails to build on 3.4.x kernel [fatal error: asm/system.h: No such file or directory]
- Fixed in Quantal, but want it SRU'd for Precise as it will affect anyone running a 12.10 kernel in 12.04
994255 - bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu6.1: bcmwl kernel module failed to build [fatal error: asm/system.h: No such file or directory]
- Fixed in Quantal, but want it SRU'd for Precise as it will affect anyone running a 12.10 kernel in 12.04
1020285 - Addition of leap second causes spuriously high CPU usage and futex lockups
1022561 - Quantal : kexec kernel not triggered when kernel panics
1022578 - [omap3beagle - omap3beagle, recording] No sound at all
1023141 - wireless device hard-blocked on wakeup
959352 - Ephemeral containers have "/rootfs" prefix in /proc/self/maps entries
Dependencies on other teams to make deliverables, blocking items, release wide concerns?
None at this time.
Previous Meeting Summaries
2012-07-20 - https://lists.ubuntu.com/archives/ubuntu-release/2012-July/
2012-07-13 - https://lists.ubuntu.com/archives/ubuntu-release/2012-July/001532.html
2012-07-06 - https://lists.ubuntu.com/archives/ubuntu-release/2012-July/001503.html
2012-06-29 - https://lists.ubuntu.com/archives/ubuntu-release/2012-June/001468.html
2012-06-22 - https://lists.ubuntu.com/archives/ubuntu-release/2012-June/001401.html
2012-06-15 - https://lists.ubuntu.com/archives/ubuntu-release/2012-June/001362.html
2012-06-08 - https://lists.ubuntu.com/archives/ubuntu-release/2012-June/001326.html
2012-06-01 - https://lists.ubuntu.com/archives/ubuntu-release/2012-May/001284.html
2012-05-24 - https://lists.ubuntu.com/archives/ubuntu-release/2012-May/001259.html
Milestoned features
See Milestone ubuntu-12.10-alpha-1 for features and tasks for the current milestone. The overall burndown chart for the entire release is also available.
Kernel BurnDown
Status Color Key
Color |
Definition |
Red |
In danger of not making this release |
Yellow |
Has issues that need to be resolved in order to make the release |