Improve the dist-upgrade process
The recent dapper->edgy upgrade process caused quite a few problems for many users (some because of failures in the ubuntu archive, some because of problems caused by 3rd party packages). This spec tries to identify what went wrong and how things can be improved to provide a more robust upgrade process.
Blueprint information
- Status:
- Started
- Approver:
- Scott James Remnant (Canonical)
- Priority:
- High
- Drafter:
- Michael Vogt
- Direction:
- Needs approval
- Assignee:
- Michael Vogt
- Definition:
- Approved
- Series goal:
- Accepted for feisty
- Implementation:
-
Started
- Milestone target:
- None
- Started by
- Michael Vogt
- Completed by
Whiteboard
review: looks OK -- smurf
2006-11-29 kamion: Use cases should be positive (what should happen after the spec is implemented, not bad things that happen now). Also, I found this spec pretty difficult to read, mostly because it seems to take some time to get to the point. Could you refactor this so that the actual design is up-front (right after the Scope), remove text that is essentially just thought processes leading you to the final design, and make sure to factor in any relevant comments from "BoF agenda and discussion" (or rename it to Comments if it's stuff you don't intend to include in the design but would like to keep around for reference)? Bug references should probably go in a section near the end. For the record, I'm satisfied with the general design here.
2006-11-29 mvo: addressed the above points
2006-11-29 kamion: Thanks, that's much better; approved.
