ReleaseProcess

Differences between revisions 5 and 6
⇤ ← Revision 5 as of 2007-10-18 08:33:06 →
Size: 3515
Editor: dsl093-039-086
Comment: htaccess also needs munging
← Revision 6 as of 2007-10-18 09:19:34 → ⇥
Size: 3515
Editor: dsl093-039-086
Comment: website before email announcement
Deletions are marked like this. Additions are marked like this.
Line 47: Line 47:
 1. Send the release announcement to {{{ubuntu-announce}}}
Line 51: Line 50:
 1. Send the release announcement to {{{ubuntu-announce}}}

To be carried out by: Steve Langasek, with support from the [https://launchpad.net/~ubuntu-release Ubuntu release team]

Goals:

  • Ship it!

Release minus 6 days:

  1. Selectively accept package uploads to resolve targeted bugs

  2. Notify Scott James Remnant to perform a ReadaheadListUpdate

  3. Go through ReleaseChecklist (again, yes)

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

  5. 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)

Release minus 3 days:

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

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

  4. Clear the [http://people.ubuntu.com/~ubuntu-archive/NBS NBS] list.

  5. Notify Marc Tardif and ask for re-certification on test hardware

  6. Notify Henrik Nilsen Omma to begin ReleaseValidationProcess

  7. Prepare the release announcement
    • 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
    • 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

  8. 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.
  2. Begin running the mirror prober hourly on staging.ubuntu.com to monitor the propagation of the images to mirrors
  3. Prepare a static front-page and a list of mirrors "just in case." (Matthew Nuzum)
  4. Publish release announcement, release notes and feature walk through on the website (Matthew Nuzum)

Release minus 3 hours:

  1. Publish the CD images. This usually requires mangling the .htaccess and the HEADER.html in the directory where the images are stored, since publish-release isn't smart enough to do the right thing there

  2. Run the mirror prober continuously to verify which mirrors are up to date
  3. Check torrents for proper functionality
  4. Confirm that website content is finalized, as further edits will be difficult under load (Matthew Nuzum)

Release:

  1. Update the topic on #ubuntu-devel and #canonical

  2. 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)

  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. Post announcement to [http://www.ubuntuforums.org/forumdisplay.php?f=13 News & Announcements section] (Matt Zimmerman and forum admins have posting rights)

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

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

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