2011-09-19; CharlieKravetz; a process/checklist to assist in getting all the items done for Xubuntu releases
|Deletions are marked like this.||Additions are marked like this.|
|Line 5:||Line 5:|
|||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||||== The Xubuntu release process ==|
|Line 7:||Line 7:|
|To be carried out by the Xubuntu Release Team with support from the Xubuntu Team and advice from the [[https://launchpad.net/~ubuntu-release|Ubuntu release team]] where needed.|
|Line 8:||Line 9:|
|To be carried out by: The Xubuntu Release Manager, with support from the Xubuntu Development Team and advice from the [[https://launchpad.net/~ubuntu-release|Ubuntu release team]]||The goal of this process is to ensure that all ISOs are suitable for release.|
|Line 10:||Line 11:|
|Goals:||''' 14 days before release '''
* Notifications of freezes
* Reminder to update the website FAQ (for the final release only)
|Line 12:||Line 15:|
| * Ensure that all ISOs are suitable for release.
* This process should apply to alphas, betas, [[ReleaseCandidate|ReleaseCandidates]], final releases, and milestones.
* Ship it!
|''' 7 days before release '''
* Gather people for milestone testing
* Start preparing release notes and release announcement
|Line 16:||Line 19:|
|== T minus 14 days ==||''' 5 days before release '''
* Smoketest images
|Line 18:||Line 22:|
| 1. Forward notifications of milestone freeze to email@example.com mailing list.
1. Insure freeze times are posted in #xubuntu-devel and firstname.lastname@example.org mailing list.
1. Freeze Day - notify developers of freeze and change topic in #xubuntu-devel.
|''' 3 days before release '''
* Start milestone testing
|Line 22:||Line 25:|
|== T minus 7 days ==||''' 1 day before release '''
* Review release notes
|Line 24:||Line 28:|
| 1. Request Xubuntu developers availability for milestone testing.
1. Review [[https://wiki.ubuntu.com/Xubuntu/Testing | testing pages]] to insure they are up to date.
1. Remind project lead to begin preparing release notes.
|''' Release day '''
* Publish release announcement
* Update the website
|Line 28:||Line 32:|
|== T minus 5 days ==
* Testing should smoketest the images to insure they install.
== T minus 3 days ==
1. Testing begins on the images available.
* For alpha images, use the [[https://wiki.ubuntu.com/Xubuntu/Testing/TestingInfo/Short | short tests]].
* For beta, rc, and final images, use the [[https://wiki.ubuntu.com/Xubuntu/Testing/TestingInfo/Long | long tests]].
* All tests are recorded/tracked using the Ubuntu QA [[http://iso.qa.ubuntu.com/qatracker/build/xubuntu/all | ISO tracker]].
1. Coordinate all testing with Ubuntu QA in #ubuntu-testing.
1. Start the news article for the release; this is to be published on [[http://xubuntu.org | the website]] at the time of the release.
== T minus 1 day ==
1. Add release notes to the wiki.
* Alpha notes are combined with Ubuntu release notes at https://wiki.ubuntu.com/ReleaseName/TechnicalOverview .
* Beta and rc notes can be combined as alpha or, if significant changes were made should be separate under https://wiki.ubuntu.com/Xubuntu/ReleaseName/Milestone (example: https://wiki.ubuntu.com/Xubuntu/LucidLynx/Final).
== Release Day ==
1. Review the Technical Overview/Release Notes to insure everything is accurate.
1. Monitor for release announcement and PASS IT ON when announced.
* Publish news on the Xubuntu website.
* For the final release, insure the website download page is updated for the new release.
1. Review bugs to insure all bugs found during testing are listed at https://wiki.ubuntu.com/Xubuntu/Bugs/ReleaseName .
1. Update the [[https://wiki.ubuntu.com/Xubuntu/TeamReports | Team Report]].
1. Add milestone review to [[https://wiki.ubuntu.com/Xubuntu/Meetings | meeting agenda]].
* Reviewing as soon as possible helps to learn what we could have done better.
* This is also a great time to congratulate the team for a job well done.
== T plus 7 days ==
* Review this page and update it as needed for the next milestone/release period.
* Reviewing as soon as possible helps keep this as up to date as possible.
|''' 7 days after release '''
* Review and update this page
The Xubuntu release process
To be carried out by the Xubuntu Release Team with support from the Xubuntu Team and advice from the Ubuntu release team where needed.
The goal of this process is to ensure that all ISOs are suitable for release.
14 days before release
- Notifications of freezes
- Reminder to update the website FAQ (for the final release only)
7 days before release
- Gather people for milestone testing
- Start preparing release notes and release announcement
5 days before release
- Smoketest images
3 days before release
- Start milestone testing
1 day before release
- Review release notes
- Publish release announcement
- Update the website
7 days after release
- Review and update this page