Ubuntu Wiki

To be carried out by: The Xubuntu Release Manager, with support from the Xubuntu Development Team and advice from the Ubuntu release team

Goals:

• Ensure that all ISOs are suitable for release.

• This process should apply to alphas, betas, ReleaseCandidates, final releases, and milestones.

• Ship it!

T minus 14 days

1. Forward notifications of milestone freeze to xubuntu-devel@lists.ubuntu.com mailing list.

2. Insure freeze times are posted in #xubuntu-devel and xubuntu-devel@lists.ubuntu.com mailing list.

3. Freeze Day - notify developers of freeze and change topic in #xubuntu-devel.
4. Remind contributors that Top 10 FAQ needs to be reviewed and updated for the new release.

T minus 7 days

1. Request Xubuntu developers availability for milestone testing.

2. Review testing pages to insure they are up to date.

3. Remind project lead to begin preparing release notes.

4. Remind the website team to begin preparations updating http://xubuntu.org.

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 short tests.

   • For beta, rc, and final images, use the long tests.

   • All tests are recorded/tracked using the Ubuntu QA ISO tracker.

2. Coordinate all testing with Ubuntu QA in #ubuntu-testing.

3. Start the news article for the release; this is to be published on 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/ReleaseNotes/ReleaseName/Milestone

Release Day

1. Review the Technical Overview/Release Notes to insure everything is accurate.
2. 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.

3. Update the Team Report.

4. Add milestone review to 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.