ReleaseManagement
This page is intended put some structure around the various aspects of release management, and use this as a page for gathering information, processes, etc. First gather, then make look pretty.
Active Release Status
Links that are Tracking Release Dates:
- Current Development Release Schedule
- Long Term Support Release Schedule
Links to help track current activity of a release:
Brainstorming on better metrics to track releases quality:
Release Processes
These are the check lists necessary to set up the infrastructure for a release, manage it through the life cycle, get it burned to ISOs, and track after release to look for ways to improve.
New Release Kickoff
Review and update key information about a release in:
Work through:
Make necessary additions to:
Update templates and propose initial schedule for release+2 (for advanced planning of activites/etc.)
Tracking and Management
Publishing
Post Release Feedback
- TO DO: add in WIKI page based on feedback received at Natty UDS.
Stable Release Updates
Security Updates
https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures (handled by the Ubuntu Security team)
End of Life
- look into special pre-announce 2 months before for LTS
example for LTS announce: https://lists.ubuntu.com/archives/ubuntu-announce/2009-July/000123.html
Communication
These are the mechanisms we use to communicate with each other and manage the release and its quality.
Documentation
Updates to the documentation to accompany the release should follow the following.
Only ubuntu-doc-committers can commit to the main code.
Contributors can/should only push to the personal branches and propose a merge, or simply create a bundle and submit to the list for committers to review and accept/merge to the main.
See: https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation