Ubuntu Wiki

To be carried out by: The Ubuntu Release Manager, with support from the Ubuntu release team

Goals:

• Ship it!

After final Beta Release is published:

1. Work with universe/multiverse community to identify delegates to approve Feature Freeze Exceptions, in addition to ubuntu-release until the date of Final Freeze for universe.
2. Set the Final Freeze date (typically at release minus 5 days) for universe/multiverse for the packages that are NOT found on any installation media.
3. Universe/multiverse delegates and final freeze date is broadcast to ubuntu-devel-discuss and ubuntu-devel-announce.

Release minus 14 days:

1. NonLanguagePackTranslationDeadline, ensure uploads with updated translations downloaded from Rosetta are done for:

   1. ubiquity (debian-installer)
   2. ubiquity-slideshow-ubuntu
   3. gfxboot-theme-ubuntu
   4. wubi
   5. yelp, gnome-user-docs and ubuntu-docs
   6. DDTP data (package description translations)

2. Notify Language Translation Lead (DavidPlanella) to coordinate a fresh set of language packs which will be exported, uploaded, and built in time for the release.

3. Notify IS (JamesTroup) to prepare a signed copy of wubi (the signing key is kept in a controlled environment).

4. If any image names have changed since the previous cycle, notify the web team (ellen.arnold@canonical.com, IRC: ellen) to check the website downloader code.

5. Check the minimum memory, disk requirements for installation and:

   1. update https://help.ubuntu.com/community/Installation/SystemRequirements

   2. update bin/make-web-indices
   3. notify Gerry Carr of the requirements, for inclusion in the CD sleeves

Release minus 6 days:

1. Selectively accept package uploads to resolve targeted bugs

2. Go through ReleaseChecklist (again, yes)

3. Top up the CDs with language packs (but leave a megabyte or two just in case)

4. Contact Gerry Carr and the web team (ellen.arnold@canonical.com, IRC: ellen) to confirm that website preparations are on-track; this includes preparing http://www.ubuntu.com/getubuntu/download

5. Review list of full iso image names and sizing with Matthew Nuzum and cross check for mirror space issues with Jonathan Davies

6. Notify Martin Pitt to disable apport and kerneloops by default (enabled=0 in /etc/default/apport and /etc/default/kerneloops).

7. Get the signed copy of Wubi from IS, and make sure queued up for image builds.

Release minus 3 days:

1. Make sure that /etc/issue, /etc/issue.net, and /etc/lsb-release are correct

2. Modify debian-cd/CONF.sh to set OFFICIAL

3. Produce a full set of images
4. Clear out the testing grid

5. Clear the NBS list.

6. Notify Platform Services and ask for re-certification on test hardware

7. Notify QA to begin ReleaseValidationProcess

8. Prepare the release announcement
   • Notify Jonathan Riddell to prepare separate Kubuntu release announcements
   • this should refer to the web page prepared by the doc team rather than going into details of changes itself
   • update the page to include any caveats
   • notify loco teams to translate release notes (coordinate new translation URLs with Matthew Nuzum)

   • Notify Rick Spencer, ubuntu-doc@lists.ubuntu.com to proofread the announcements and suggest changes, CC product owners (Jason Warner, Robbie Williamson, David Mandala) and Marketing (Gerry Carr).

9. Review targeted bugs and take final decisions on what to fix and what to defer
10. Ensure a signed Wubi is on the CDs.

Release minus 1 day:

1. Pre-publish the CD images: ./publish-image-set.py --prepublish will print the necessary commands.

2. copy .manifest to .manifest.full, and prune all images from previous releases from the .manifest file to allow timely mirror probing

3. Run sync-mirrors on antimony to push out the pre-published file structure.

4. Begin running the mirror prober hourly on staging.ubuntu.com to monitor the propagation of the images to mirrors
5. Prepare a static front-page and a list of mirrors "just in case." (Matthew Nuzum)

6. Publish release announcement, release notes and feature walk through on the website (ellen.arnold@canonical.com, IRC: ellen)

Release minus 3 hours:

1. If there is a previous milestone for this series, move those images from /srv/cdimage.ubuntu.com/www/full to /srv/cdimage.ubuntu.com/old-images/, and notify the sysadmin team that these are available for off-line archival.

2. Copy the final wubi.exe to the release directory, cdimage/www/simple/natty/wubi.exe (downloaded from http://people.ubuntu.com/~evand/wubi/natty/stable).

3. Notify the web team (Ellen Arnold) that http://www.ubuntu.com/desktop/get-ubuntu/windows-installer needs to point to the correct wubi.exe file.

4. Publish the CD images: ./publish-image-set.py will print the necessary commands.

   • You need to edit cdimage/www/simple/HEADER.html, cdimage/www/simple/kubuntu/HEADER.html, cdimage/www/simple/.htaccess, and cdimage/www/simple/kubuntu/.htaccess by hand, to drop the mention of "Release Candidate", since neither publish-release nor publish-image-set.py is yet smart enough to do the right thing there.

5. copy .manifest to .manifest.full again, pruning all images from previous releases from the .manifest file to allow timely mirror probing

6. Run sync-mirrors on antimony to push out the published file structure.

7. Update the UEC images - see checklist on https://wiki.ubuntu.com/UEC/Images/Publishing

   • log into nectarine and start screen.
   • run ~vmbuilder/bin/vbcron promote-daily release --make-public -release... /srv/ec2-images/server/maverick/20101007.1 --verbose
   • log into amazon server and update the ami pages
8. Publish the Chinese edition (this involves copying files by hand).

9. Run the mirror prober continuously to verify which mirrors are up to date; output visible here

10. Check torrents for proper functionality
11. Confirm that website content is finalized, as further edits will be difficult under load and check with sysadmin that caches will be cleared on time (Ellen Arnold, Jonathan Riddell, Oliver Grawert, James Troup)
12. Notify James Westby to stop the Bazaar importer for the release.

Release:

1. Update the topic on #ubuntu-devel, #canonical, and #ubuntu-release-party and make announcement in #ubuntu-release-announce, and then in #ubuntu-release-party.

2. Update the meta-release index (MichaelVogt updates the bzr branch and copies the updated meta-release* files (as user changelogs) to rookery:/srv/changelogs.ubuntu.com/www)

3. Notify Ellen Arnold to announce on the website
   • News sidebar
   • Box at top of home page

4. Send the release announcement to ubuntu-announce

5. Notify a Launchpad admin to set the status of this distrorelease to CURRENT, and to change any previous CURRENT distrorelease(s) to SUPPORTED.

6. Post announcement to News & Announcements section (Matt Zimmerman and forum admins have posting rights)

7. Post announcement to Launchpad (ubuntu-drivers members have posting rights)

8. Post an announcement on http://release-blog.ubuntu.com/

9. Sleep!

Release plus 1 day:

1. If any changes were made to this document in this run, check whether the changes also apply to MilestoneProcess, BetaProcess or ReleaseCandidateProcess.

2. Continue on NewReleaseCycleProcess.

3. Update Relevant community documentation with references to this new release

   • https://help.ubuntu.com/community/ReportingBugs

Release plus ~ 2 weeks:

1. Hold PostReleaseReview session at UDS, and feed input into updating processes, and next release cycle.

CategoryProcess