ReleaseProcess

Differences between revisions 1 and 100 (spanning 99 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 100 as of 2013-04-09 22:42:14 → ⇥
Size: 9913
Editor: vorlon
Comment: fix contact info for the web team to use role info
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 [[https://launchpad.net/~ubuntu-release|Ubuntu release team]]
Line 7: Line 7:
Release minus 6 days: 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 day minus 1.5 days) for universe/multiverse for the packages that are [[UnseededUniverseFinalFreeze|NOT found on any installation media]].
 1. Universe/multiverse delegates and final freeze date is broadcast to ubuntu-devel-discuss and ubuntu-devel-announce.
 1. Check the minimum memory, disk requirements for installation and:
   1. update https://help.ubuntu.com/community/Installation/SystemRequirements
   1. update bin/make-web-indices
   1. notify marketing 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)
  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.

 
Release minus 10 days:

 1. Ask vanguard on #IS 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).
 1. If any image names have changed since the previous cycle, notify the web team (#web-team on canonical; email: webteam@canonical.com) 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 (release candidate week):
Line 10: Line 36:
 1. Notify Scott James Remnant to perform a ReadaheadListUpdate
Line 13: Line 38:
 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. Review list of full iso image names and plans with web team (#web-team on canonical; email: webteam@canonical.com)
 1. Review full iso image sizing with cross check for mirror space issues with IS (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.
 1. Get list of translated languages on CD from David Plannela.
 1. Notify Ubuntu, Kubuntu and other flavour contacts to create and update their Upgrade docs at https://help.ubuntu.com/community/RaringUpgrades
 1. Notify OEM team (irc: KyleN ) to build found license list for main.


Release minus 6 days:

 1. Contact the web team to confirm that:
    * website preparations are on-track; this includes preparing http://www.ubuntu.com/getubuntu/download
    * update http://www.ubuntu.com/project/about-ubuntu/derivatives (review flavors and translated languages)
 1. Post full set of pre-release images with last language pack updates to QA iso tracker to start QA testing.
 1. Turn off daily builds (unless explicit reason why they need to remain on).
 
Line 17: Line 58:
 1. Make sure that /etc/issue, /etc/issue.net, and /etc/lsb-release are correct
Line 18: Line 60:
 1. Produce a full set of images  1. Ensure that the ISO tracker lists the new milestone
 1. Edit `default_milestone` in `~cdimage/.isotracker.conf` to match the new milestone name in the ISO tracker
 1. Ensure a signed Wubi is on the CDs.
 1. Produce a full set of official images
Line 20: Line 65:
 1. Notify Fabio Massimo Di Nitto and ask for re-certification on test hardware
 1. Notify Henrik Nilsen Omma to begin ReleaseValidationProcess		  1. Clear the [[http://people.canonical.com/~ubuntu-archive/nbs.html|NBS]] list.
 1. Notify Hardware Certification team ( email: hardware-certification@canonical.com, IRC: ara ) to begin [[https://wiki.canonical.com/CertificationTestingProcess|CertificationTestingProcess]] (private due to agreements with vendors)
 1. Notify QA to begin ReleaseValidationProcess
Line 23: Line 69:
  * Notify Jonathan Riddell, Oliver Grawert to prepare separate Kubuntu and Edubuntu release announcements
  * add any caveats discovered in RC
  * this should refer to the web page prepared by the doc team rather than going into details of changes itself		   * 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
Line 27: Line 72:
  * 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		   * notify loco teams to translate release notes (coordinate new translation URLs with web team and David Planella)
Line 30: Line 75:

Line 32: Line 79:
 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 --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 nusakan to push out the pre-published file structure.
Line 35: Line 83:
 1. Prepare a static front-page and a list of mirrors "just in case." (Matthew Nuzum)
 1. Publish release announcement, release notes and feature walk through on the website (Matthew Nuzum)
Release minus 3 hours:		  1. Prepare a static front-page and a list of mirrors "just in case." (web team)
  * Notify management, marketing, and {{{ubuntu-doc@lists.ubuntu.com}}} to proofread the announcements and suggest changes.
 1. Review on the staging server the release announcement, release notes and feature walk through on the website (web-team)
 1. Build the sources images (cron.source) to be published, by the publisher script.
Line 39: Line 88:
 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. Check torrents for proper functionality
 1. Confirm that website content is finalized, as further edits will be difficult under load (Matthew Nuzum)		 Release minus 6 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.
 1. Copy the final wubi.exe to the release directory, {{{cdimage/www/simple/quantal/wubi.exe}}} (downloaded from http://people.canonical.com/~evand/wubi/quantal/stable).
 1. Notify the web team 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}}} will print the necessary commands.
  * You need to edit {{{cdimage/www/simple/HEADER.html}}} and {{{cdimage/www/simple/.htaccess}}} by hand to drop the mention of "Release Candidate", since neither publish-release nor publish-image-set 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 nusakan to push out the published file structure.
 1. Update the Cloud images (IRC: utlemming) - see checklist on https://wiki.ubuntu.com/UbuntuCloud/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. Publish the Chinese edition (this involves copying files by hand).
 1. Run the mirror prober continuously to verify which mirrors are up to date; [[https://launchpad.net/ubuntu/+cdmirrors|output visible here]]
 1. Check torrents for proper functionality.
 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 (web-team, IS, release-team).
 1. Notify #launchpad-ops (or someone with access to jubany) to stop the Bazaar importer for the release.

Release minus 1 hour:
 1. Coordinate with web team for publishing of staging.
 1. Coordinate with PR team (Sian Aherne) to inform media who are waiting for launch to post their articles.
 1. Post the md5 hashes to [[https://help.ubuntu.com/community/UbuntuHashes]].
Line 46: Line 114:
 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. Notify Matthew Nuzum to announce on the website		  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)
 1. Notify web team to announce on the website
Line 52: Line 119:
 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 121:
 1. Deactivate release milestone in Launchpad.
 1. Post announcement to [[http://www.ubuntuforums.org/forumdisplay.php?f=13|News & Announcements section]] (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 57: Line 128:
 1. If any changes were made to this document in this run, check whether the changes also apply to MilestoneProcess, BetaProcess or ReleaseCandidateProcess.  1. If any changes were made to this document in this run, check whether the changes also apply to AlphaProcess, BetaProcess or ReleaseCandidateProcess.
Line 59: Line 130:
 1. Update Relevant community documentation with references to this new release
    * https://help.ubuntu.com/community/ReportingBugs
 1 Review through the process pages, and update to the release name (oneiric->precise)

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 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 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. Ask vanguard on #IS 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 (#web-team on canonical; email: webteam@canonical.com) to check the website downloader code. Ask the web team to review Release Manifest.

  3. 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 (release candidate week):

  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 (#web-team on canonical; email: webteam@canonical.com)

  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.
  8. Get list of translated languages on CD from David Plannela.

  9. Notify Ubuntu, Kubuntu and other flavour contacts to create and update their Upgrade docs at https://help.ubuntu.com/community/RaringUpgrades

  10. Notify OEM team (irc: KyleN ) to build found license list for main.

Release minus 6 days:

  1. Contact the web team to confirm that:
  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 that the ISO tracker lists the new milestone

  4. Edit default_milestone in ~cdimage/.isotracker.conf to match the new milestone name in the ISO tracker

  5. Ensure a signed Wubi is on the CDs.
  6. Produce a full set of official images
  7. Clear out the testing grid

  8. Clear the NBS list.

  9. Notify Hardware Certification team ( email: hardware-certification@canonical.com, IRC: ara ) to begin CertificationTestingProcess (private due to agreements with vendors)

  10. Notify QA to begin ReleaseValidationProcess

  11. 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)
  12. 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 --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 nusakan 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)

    • Notify management, marketing, and ubuntu-doc@lists.ubuntu.com to proofread the announcements and suggest changes.

  6. Review on the staging server the release announcement, release notes and feature walk through on the website (web-team)
  7. Build the sources images (cron.source) to be published, by the publisher script.

Release minus 6 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/quantal/wubi.exe (downloaded from http://people.canonical.com/~evand/wubi/quantal/stable).

  3. Notify the web team 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 will print the necessary commands.

    • You need to edit cdimage/www/simple/HEADER.html and cdimage/www/simple/.htaccess by hand to drop the mention of "Release Candidate", since neither publish-release nor publish-image-set 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 nusakan to push out the published file structure.

  7. Update the Cloud images (IRC: utlemming) - see checklist on https://wiki.ubuntu.com/UbuntuCloud/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 (web-team, IS, release-team).
  12. Notify #launchpad-ops (or someone with access to jubany) to stop the Bazaar importer for the release.

Release minus 1 hour:

  1. Coordinate with web team for publishing of staging.
  2. Coordinate with PR team (Sian Aherne) to inform media who are waiting for launch to post their articles.

  3. Post the md5 hashes to https://help.ubuntu.com/community/UbuntuHashes.

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 web team 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. Deactivate release milestone in Launchpad.

  7. Post announcement to News & Announcements section (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 AlphaProcess, BetaProcess or ReleaseCandidateProcess.

  2. Continue on NewReleaseCycleProcess.

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

    1 Review through the process pages, and update to the release name (oneiric->precise)

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)