ReleaseProcess

Differences between revisions 1 and 56 (spanning 55 versions)
⇤ ← Revision 1 as of 2007-10-12 15:04:27 →
Size: 3551
Editor: 82-69-40-219
Comment: moved from wiki.c.c
← Revision 56 as of 2010-11-24 23:11:04 → ⇥
Size: 7661
Editor: 99-191-111-134
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
To be carried out by: Steve Langasek, with support from the [https://launchpad.net/~ubuntu-release Ubuntu release team] To be carried out by: The Ubuntu Release Manager, with support from the [[https://launchpad.net/~ubuntu-release|Ubuntu release team]]
Line 7: Line 7:
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.
 1. 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.
 1. 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)
  1. ubiquity-slideshow-ubuntu
  1. gfxboot-theme-ubuntu
  1. wubi
  1. yelp, gnome-user-docs and ubuntu-docs
  1. DDTP data (package description translations)
 1. 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.
 1. Notify IS (JamesTroup) to prepare a signed copy of wubi (the signing key is kept in a controlled environment).
 1. If any image names have changed since the previous cycle, notify Matthew Nuzum to check the website downloader code.
Line 10: Line 27:
 1. Notify Scott James Remnant to perform a ReadaheadListUpdate
Line 13: Line 29:
 1. Notify Gerry Carr and [mailto:matthew.nuzum@canonical.com Matthew Nuzum] to ensure they have time to prepare the website (this includes preparing http://www.ubuntu.com/getubuntu/download)  1. Contact Gerry Carr and [[mailto:matthew.nuzum@canonical.com|Matthew Nuzum]] to confirm that website preparations are on-track; this includes preparing http://www.ubuntu.com/getubuntu/download
 1. Review list of full iso image names and sizing with Matthew Nuzum and cross check for mirror space issues with Jonathan Davies
 1. Notify Martin Pitt to disable apport and kerneloops by default (`enabled=0` in `/etc/default/apport` and `/etc/default/kerneloops`).
 1. Get the signed copy of WUBI from IS, and make sure queued up for image builds.
Line 17: Line 36:
 1. Make sure that /etc/issue, /etc/issue.net, and /etc/lsb-release are correct
Line 20: Line 40:
 1. Notify Fabio Massimo Di Nitto and ask for re-certification on test hardware  1. Clear the [[http://people.ubuntu.com/~ubuntu-archive/NBS|NBS]] list.
 1. Notify Marc Tardif and ask for re-certification on test hardware
Line 24: Line 45:
  * add any caveats discovered in RC
Line 28: Line 48:
  * Notify Matt Zimmerman, {{{ubuntu-doc@lists.ubuntu.com}}} to proofread the announcements and suggest changes   * Notify Matt Zimmerman, {{{ubuntu-doc@lists.ubuntu.com}}} to proofread the announcements and suggest changes, CC product owners (Rick Spencer, Jos Boumans, David Mandala) and Marketing (Gerry Carr).
Line 30: Line 50:
 1. Ensure a signed Wubi is on the CDs.
Line 32: Line 54:
 1. Disable the automatic mirror list update on the website
 1. Pre-publish the CD images.		  1. Pre-publish the CD images: {{{./publish-image-set.py --prepublish}}} will print the necessary commands.
 1. copy .manifest to .manifest.full, and prune all images from previous releases from the .manifest file to allow timely mirror probing
 1. Run {{{sync-mirrors}}} on antimony to push out the pre-published file structure.
Line 39: Line 62:
 1. Publish the CD images. This usually requires mangling the {{{HEADER.html}}} in the directory where the images are stored, since publish-release isn't smart enough to do the right thing there
 1. Run the mirror prober continuously to verify which mirrors are up to date
 1. Enable the automatic mirror list update on the website		  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.
 1. Copy the final wubi.exe to the release directory, {{{cdimage/www/simple/maverick/wubi.exe}}} (downloaded from http://people.ubuntu.com/~evand/wubi/maverick/stable).
 1. Notify the web team (Birgit Oberlerchner and/or Matt Nuzum) that http://www.ubuntu.com/desktop/get-ubuntu/windows-installer needs to point to the correct wubi.exe file.
 1. 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.
 1. copy .manifest to .manifest.full again, pruning all images from previous releases from the .manifest file to allow timely mirror probing
 1. Run {{{sync-mirrors}}} on antimony to push out the published file structure.
 1. 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
 1. Run the mirror prober continuously to verify which mirrors are up to date; [[https://launchpad.net/ubuntu/+cdmirrors|output visible here]]
Line 43: Line 75:
 1. Confirm that website content is finalized, as further edits will be difficult under load (Matthew Nuzum)  1. 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 (Matthew Nuzum, Jonathan Riddell, Oliver Grawert, James Troup)
 1. Notify James Westby to stop the Bazaar importer for the release.
Line 46: Line 79:
 1. Update the topic on {{{#ubuntu-devel}}} and {{{#canonical}}}
 1. Update the meta-release index (MichaelVogt updates the bzr [http://bazaar.launchpad.net/~ubuntu-core-dev/meta-release/ubuntu branch] and copies the updated meta-release* files (as user changelogs) to rookery:/srv/changelogs.ubuntu.com/www)
 1. Send the release announcement to {{{ubuntu-announce}}}		  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}}}.
 1. Update the meta-release index (MichaelVogt updates the bzr [[http://bazaar.launchpad.net/~ubuntu-core-dev/meta-release/ubuntu|branch]] and copies the updated meta-release* files (as user changelogs) to rookery:/srv/changelogs.ubuntu.com/www)
Line 52: Line 84:
 1. Post announcement to [http://www.ubuntuforums.org/forumdisplay.php?f=13 News & Announcements section] (Matt Zimmerman and forum admins have posting rights)  1. Send the release announcement to {{{ubuntu-announce}}}
Line 54: Line 86:
 1. Post announcement to [[http://www.ubuntuforums.org/forumdisplay.php?f=13|News & Announcements section]] (Matt Zimmerman and forum admins have posting rights)
 1. Post announcement to [[https://launchpad.net/ubuntu/+announce|Launchpad]] ([[https://launchpad.net/~ubuntu-drivers/+members|ubuntu-drivers members]] have posting rights)
 1. Post an announcement on http://release-blog.ubuntu.com/
Line 59: Line 94:

Release plus ~ 2 weeks:
 1. Hold PostReleaseReview session at UDS, and feed input into updating processes, and next release cycle.
----
CategoryProcess

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 Matthew Nuzum to check the website downloader code.

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 Matthew Nuzum 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 Marc Tardif and ask for re-certification on test hardware

  7. Notify Henrik Nilsen Omma to begin ReleaseValidationProcess

  8. Prepare the release announcement
    • Notify Jonathan Riddell, Oliver Grawert to prepare separate Kubuntu and Edubuntu 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 Matt Zimmerman, ubuntu-doc@lists.ubuntu.com to proofread the announcements and suggest changes, CC product owners (Rick Spencer, Jos Boumans, 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 (Matthew Nuzum)

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/maverick/wubi.exe (downloaded from http://people.ubuntu.com/~evand/wubi/maverick/stable).

  3. Notify the web team (Birgit Oberlerchner and/or Matt Nuzum) 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. Run the mirror prober continuously to verify which mirrors are up to date; output visible here

  9. Check torrents for proper functionality
  10. 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 (Matthew Nuzum, Jonathan Riddell, Oliver Grawert, James Troup)
  11. 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 Matthew Nuzum 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.

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)