Progress towards topic-quantal-release-sru-and-12.04.1
This page shows the progress towards completing a Topic . You can see from the burndown if the Topic is likely to be completed at the current rate of work. Below that you can see the progress towards the blueprints that contribute to the Topic , and the progress of each person working on the Topic .
Launchpad pageWorkitem burndown
"foreign" counts refer to workitems that are assigned to someone not in the team
90% of 49
Contributing Blueprints
| Blueprint | Completion | Priority | Status/Description |
|---|---|---|---|
| other-q-12.04.1-team |
85% of 13
|
High | Session to discuss how the virtual team working on the 12.04.1 point release will organize their work |
| desktop-q-xorg-lts-updates |
86% of 21
|
High | Canonical has announced a new 5-year LTS support policy for the Ubuntu Desktop which will provide updates to X, drivers, and necessary plumbing layer components to provide support for newer hardware in the LTS. * What is the best way to distribute the updated X stack? * Will this be an opt-in change for upgraders? If so, how will the upgrader need to be changed to properly guide the user in making a choice? * For consistency, what version naming scheme should be used for these package updates? * Should we limit it to just the serverside portion of the X stack? (I.e. omit libX11, etc. to avoid breakage to client apps) * For certain graphics cards, there is a possibility that driver support could be dropped in future kernel and X combinations; the upgrader will need to be aware of this and not suggest the upgrade if it won't work, or perhaps make them aware of the risks or known-regressions they'll endure if they wish to proceed anyway. * Should a way be provided to enable the user to back out the changes? If so, how should that be implemented? * How tightly should the kernel / X package versions be kept? I.e. should we discourage or permit old-kernel/new-X and/or new-kernel/old-X setups. (If we permit these combinations it gives user flexibility but imposes a larger testing impact). |
| foundations-q-more-agile-sru-process |
100% of 7
|
Medium | Our current SRU process is perhaps slightly over-engineered as a reaction to the fact that out previous SRU process was almost certainly far too lightweight. While there's (I hope obvious to all) value in documentation, audit trails, regression testing, and "bake-in" periods, our current process makes it somewhat difficult to get urgent fixes out quickly, while also discouraging the casual observer with an "obviously-correct" 2-character patch from making contributions to stable releases. We don't want to throw the babies out with the bathwater here, but we need to discuss ways we can make the process more agile while still keeping it robust enough to avoid making serious mistakes along the way. |
| qa-q-isotracker-testcases |
100% of 8
|
High | Discussing expanding the isotracker to perform testcase management and reporting for all kinds of testing, not just iso. |
Status by assignee
| Assignee | Todo | Blocked | In Progress | Postponed | Done | Completion |
|---|---|---|---|---|---|---|
| all | 0 | 0 | 0 | 0 | 1 | 100% |
| Brian Murray | 0 | 0 | 0 | 0 | 3 | 100% |
| Bryce Harrington | 0 | 0 | 0 | 0 | 4 | 100% |
| Colin Watson | 0 | 0 | 0 | 0 | 1 | 100% |
| Daniel Holbach | 0 | 0 | 0 | 0 | 1 | 100% |
| Jamie Strandboge | 0 | 0 | 0 | 0 | 1 | 100% |
| Jean-Baptiste Lallement | 0 | 0 | 0 | 0 | 4 | 100% |
| Kate Stewart | 0 | 0 | 0 | 0 | 2 | 100% |
| Larry E Works | 1 | 0 | 0 | 0 | 0 | 0% |
| Leann Ogasawara | 0 | 0 | 0 | 0 | 1 | 100% |
| Maarten Lankhorst | 0 | 0 | 2 | 0 | 2 | 50% |
| Oliver Grawert | 1 | 0 | 0 | 0 | 0 | 0% |
| Chris Halse Rogers | 0 | 0 | 0 | 0 | 2 | 100% |
| Robert Hooker | 0 | 0 | 0 | 1 | 0 | 100% |
| Sebastien Bacher | 0 | 0 | 0 | 0 | 1 | 100% |
| Stéphane Graber | 0 | 0 | 0 | 1 | 9 | 100% |
| Luke Yelavich | 0 | 0 | 0 | 2 | 0 | 100% |
| Tim Gardner | 0 | 0 | 0 | 0 | 1 | 100% |
| Timo Aaltonen | 0 | 0 | 0 | 0 | 1 | 100% |
| ubuntu-x-swat | 1 | 0 | 0 | 0 | 0 | 0% |
| Chris Van Hoof | 0 | 0 | 0 | 0 | 1 | 100% |
| Steve Langasek | 0 | 0 | 0 | 0 | 5 | 100% |
Work item details
| Assignee | Status | Blueprint | Priority | Work item |
|---|---|---|---|---|
| all | done | foundations-q-more-agile-sru-process | Medium | follow up in the phased deployment session about whether we can gather information from whoopsie about -proposed packages that are *not* crashing |
| Brian Murray | done | other-q-12.04.1-team | High | create report of top duplicates coming in from 12.04 - to consider for release |
| foundations-q-more-agile-sru-process | Medium | patch sru-accept to link to .debs for -proposed in comment or the page of the binary package build in launchpad which has all the deb links from the librarian (as the security team does) | ||
| foundations-q-more-agile-sru-process | Medium | Advertise pending-sru.html in sru-accept comment? | ||
| Bryce Harrington | done | desktop-q-xorg-lts-updates | High | Look at existing kernel update package name scheme to follow that |
| desktop-q-xorg-lts-updates | High | Communicate with the release team that we don't put previous point releases where they can't be found | ||
| desktop-q-xorg-lts-updates | High | Need to write script to do renames, replaces, breaks | ||
| desktop-q-xorg-lts-updates | High | Sync with Gemma re: daily testing of 12.04-on-12.10 PPA | ||
| Colin Watson | done | other-q-12.04.1-team | High | enable precise daily builds, to be kept running through .4 if possible, and solve any disk space / load issues (might cause timing problems on arm builders where dailies for quantal build too) |
| Daniel Holbach | done | foundations-q-more-agile-sru-process | Medium | send pilot scheduling tools to dmitrij.ledkov |
| Jamie Strandboge | done | desktop-q-xorg-lts-updates | High | talk to release team about timing of EOL notice so it does not come too early |
| Jean-Baptiste Lallement | done | other-q-12.04.1-team | High | Setup installation automated smoketesting for Precise (jobs will start automatically when builds are available on cdimage.u.c) |
| other-q-12.04.1-team | High | need to figure what need to do about disk space when quantal start, so keeping auto regression. - RAID array will be rearranged to maximize device space, 3 slots are also available to add more disks to the array | ||
| other-q-12.04.1-team | High | upgrade testing from lucid to precise | ||
| other-q-12.04.1-team | High | upgrade testing from oneiric to precise | ||
| Kate Stewart | done | other-q-12.04.1-team | High | update schedule wiki pages with dates from above |
| other-q-12.04.1-team | High | update LTS point release process pages with flow decided above | ||
| Larry E Works | todo | other-q-12.04.1-team | High | rearrange raid array and add more disks on wazn and aldebaran (~100GB additional space required) |
| Leann Ogasawara | done | desktop-q-xorg-lts-updates | High | Drive decision pre UDS-R whether or not the 12.10 stack is the only supported stack on 12.04.2 media, and if both are supported, which is the default boot option for end users |
| Maarten Lankhorst | inprogress | desktop-q-xorg-lts-updates | High | Finalize list with all stakeholders of exactly which X packages will be renamed and list in lts-pkg-mapping.txt |
| desktop-q-xorg-lts-updates | High | Define desktop-enablement metapackage | ||
| done | desktop-q-xorg-lts-updates | High | Also review the rename script | |
| desktop-q-xorg-lts-updates | High | Need to test mechanically applying the update package names | ||
| Oliver Grawert | todo | other-q-12.04.1-team | High | patch update-manager in oneiric-updates to show a note about armel/armhf transition |
| Chris Halse Rogers | done | desktop-q-xorg-lts-updates | High | Check that just changing the package names doesn't severely break compatibility |
| desktop-q-xorg-lts-updates | High | Need to check libdrm and libpciaccess before P is release to make sure it'll update properly | ||
| Robert Hooker | postponed | desktop-q-xorg-lts-updates | High | script the package removal process so people can revert back easily |
| Sebastien Bacher | done | other-q-12.04.1-team | High | 2: review release-noted bugs for candidates |
| Stéphane Graber | done | other-q-12.04.1-team | High | 1: review release-noted bugs for candidates |
| other-q-12.04.1-team | High | Schedule regular (weekly/fortnightly) meeting for these involved with 12.04.1 (engineering + release manager + L3) | ||
| qa-q-isotracker-testcases | High | Update DB schema to have testcase entries be one-to-many to testsuite and have testsuite be many-to-many to milestone_series | ||
| qa-q-isotracker-testcases | High | Never allow modifications to qatracker_testcase | ||
| qa-q-isotracker-testcases | High | 2: Figure out how to manage users roles (per product roles) (use lp teams, grant isotracker roles based on team) | ||
| qa-q-isotracker-testcases | High | add link to report "bug" against problems found on a testcase (bug #684404) | ||
| qa-q-isotracker-testcases | High | 2: come up with development plan for cycle | ||
| qa-q-isotracker-testcases | High | add testcase id that stays unique and persists across revisions | ||
| qa-q-isotracker-testcases | High | Let the team know when (iso.qa.dev.stgraber.org) is ready for testing | ||
| postponed | qa-q-isotracker-testcases | High | implement reading LAVA format on the tracker (http://linaro-dashboard-bundle.readthedocs.org/en/latest/index.html) | |
| Luke Yelavich | postponed | desktop-q-xorg-lts-updates | High | Coordinate alsalib, et al. updates with the kernel backports (perhaps using same scripts as X) |
| desktop-q-xorg-lts-updates | High | Talk to diwic if pulseaudio is going to need backported when alsa is backported | ||
| Tim Gardner | done | desktop-q-xorg-lts-updates | High | Define kernel-enablement metapackage |
| Timo Aaltonen | done | desktop-q-xorg-lts-updates | High | Also also review the rename script |
| ubuntu-x-swat | todo | desktop-q-xorg-lts-updates | High | virtualbox from precise doesn't build with quantal kernel, find a solution for all dkms packages? |
| Chris Van Hoof | done | desktop-q-xorg-lts-updates | High | Talk with PES to ensure metapackage nameing won't frighten off the folks. |
| Steve Langasek | done | desktop-q-xorg-lts-updates | High | Review rename script |
| desktop-q-xorg-lts-updates | High | Investigate effect on bluetooth and other services for server updates | ||
| foundations-q-more-agile-sru-process | Medium | talk to balloons about reviving the SRU verification team | ||
| foundations-q-more-agile-sru-process | Medium | discuss with stgraber, balloons about QA tracker vs. his tools for gathering this information | ||
| foundations-q-more-agile-sru-process | Medium | fix SRU procedure to make the "regression potential" section emphasize areas that need additional testing; obsolete "development fix" in favor of bug tasks |
Last updated: Fri 26 October 2012, 08:49 UTC