Manage Package Interdependencies in Release better
Improve infrastructure for minimizing the risk of interdependent packages hitting at the end of the cycle simultaneously.
Blueprint information
- Status:
- Started
- Approver:
- Ubuntu Release Team
- Priority:
- High
- Drafter:
- Kate Stewart
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Drafting
- Series goal:
- Accepted for oneiric
- Implementation:
-
Started
- Milestone target:
- None
- Started by
- Martin Pitt
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Work items for oneiric-alpha-1:
[kate.stewart] update release to remove plumbing freeze and move feature freeze to week 15: DONE
Work items for oneiric-alpha-2:
[michaelh1] mail out proposal for compiler branch at alpha-2 time frame, and only bug fixes in that branch until end of oneiric: DONE
[doko] document publicly compiler feature upload plan : TODO
[cjwatson] scripts for flagging long term uninstallables: TODO
[pitti] mail out component-mismatch deltas to release team, for timely sorting out recently introduced problems: DONE
[ubuntu-release] review compiler feature upload plan to determine if there are risks: BLOCKED
---------
note: this was originally https:/
pitti, 2011-06-09: it's actually not obvious how to detect the root cause of a new component mismatch, so dropping the "mailing the last uploader" part of the work item. For now we'll mail the release team, which can then forward it to the appropriate team/person.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
