ReleaseProcess

Differences between revisions 70 and 71
Revision 70 as of 2011-10-04 03:02:47
Size: 9071
Editor: 99-191-111-134
Comment:
Revision 71 as of 2011-10-06 06:14:17
Size: 9069
Editor: 82-69-40-219
Comment: typos
Deletions are marked like this. Additions are marked like this.
Line 38: Line 38:
 1. Review list of full iso image names and plans with web team ( elen.arnold@canonical.com, IRC: ellen)  1. Review list of full iso image names and plans with web team (ellen.arnold@canonical.com, IRC: ellen)
Line 48: Line 48:
 1. Turn off daily builds ( unless explicit reason why they need to remain on ).  1. Turn off daily builds (unless explicit reason why they need to remain on).

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 day minus 1.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.
  4. 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 marketing (Gerry Carr) of the requirements, for inclusion in the CD sleeves

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.

Release minus 10 days:

  1. Notify IS (JamesTroup) to prepare a signed copy of wubi (the signing key is kept in a controlled environment) after confirming no more bug fixes expected with Installer team (EvanDandrea).

  2. 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. Ask the web team to review Release Manifest. 1 Start off release notes and announce framework. Call for ubuntu-docs and other team participation in content creation of overview and documentation of release bugs.

Release minus 7 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. Review list of full iso image names and plans with web team (ellen.arnold@canonical.com, IRC: ellen)

  5. Review full iso image sizing with cross check for mirror space issues with IS (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 6 days:

  1. Contact 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

  2. Post full set of pre-release images with last language pack updates to QA iso tracker to start QA testing.
  3. Turn off daily builds (unless explicit reason why they need to remain on).

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. Ensure a signed Wubi is on the CDs.
  4. Produce a full set of official images
  5. Clear out the testing grid
  6. Clear the NBS list.

  7. Notify Platform Services and ask for re-certification on test hardware
  8. Notify QA to begin ReleaseValidationProcess

  9. Prepare the release announcement
    • Notify Flavor Product Managers (Kubuntu, Xubuntu, Lubuntu, Edubuntu, Ubuntu-Studio, Mythbuntu) to prepare separate release announcements and review/update Release Notes.
    • this should refer to the web page prepared by the teams 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 web team and David Planella)
    • 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).

  10. Review targeted bugs and take final decisions on what to fix and what to defer

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." (web team)
  6. Review on the staging server the 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 Cloud 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 minus 1 hour:

  • 1 Coordinate with web team for publishing of staging.

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. Deactive release milestone in Launchpad.
  7. Post announcement to News & Announcements section (Matt Zimmerman and forum admins have posting rights)

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

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

  10. 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

Release plus ~ 2 weeks:

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


CategoryProcess

ReleaseProcess (last edited 2021-10-15 08:15:45 by sil2100)