Improve Release Processes for Oneiric
This is a summary of the results of the Natty Release Review and feedback session, and suggestions from that for improving the Oneiric release management.
Blueprint information
- Status:
- Complete
- Approver:
- Ubuntu Release Team
- Priority:
- High
- Drafter:
- Kate Stewart
- Direction:
- Approved
- Assignee:
- Ubuntu Release Team
- Definition:
- Approved
- Series goal:
- Accepted for oneiric
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Kate Stewart
- Completed by
- Kate Stewart
Related branches
Related bugs
Sprints
Whiteboard
Work items for oneiric-alpha-1:
[kate.stewart] Discuss new day for the release meeting: DONE
[kate.stewart] Update Oneiric schedule with feedback from UDS: DONE
Work items for oneiric-alpha-2:
[kate.stewart] Create Oneiric Interlock page - include LTS events, QA, SRU, CERT, community events (KDE 3.0, etc): DONE
[kate.stewart] Get Gerry Carr to Review P/Q/R schedules for interaction with marketing plans: DONE
[allison] Summarize community case for rebalance of Q/R (Gnome, KDE, other problems?): DONE
[kate.stewart] Look implicationsinto rebalance of Q/R closer to 26 weeks each: DONE
Work items for oneiric-alpha-3:
[kate.stewart] Adjust Q/R schedules based on investigation and communicate: DONE
[kate.stewart] Determine focus points for each subsequent milestones, and arrange for contributors to pre-seed tech overview with "interesting things": DONE
Work items for oneiric-beta-2:
[kate.stewart] Get product managers sign off on images for oneiric manifest, after testing arranged for each image: DONE
-------
note: discussion on this was originally captured in: https:/
Work Items
Dependency tree
* Blueprints in grey have been implemented.
