BetaProcess

Differences between revisions 11 and 12
⇤ ← Revision 11 as of 2007-09-27 08:08:00 →
Size: 6191
Editor: p578b2f7b
Comment: HEADER.html mangling for derivatives
← Revision 12 as of 2007-09-27 12:53:11 → ⇥
Size: 6296
Editor: p578b2f7b
Comment: add www.u.c./getubuntu/download poking
Deletions are marked like this. Additions are marked like this.
Line 47: Line 47:
 1. Notify Matthew Nuzum about setting up http://www.ubuntu.com/getubuntu/download for the Beta release

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

Goals:

  • Produce a set of well-tested distribution media images suitable for broad testing by advanced users
  • Allow all packages in main to be test-built and bugs filed where relevant
  • Confirm that certified hardware is properly supported
  • Keep the developer community informed about the status of the release.

During the whole process:

  • Check if there are newsworthy items and either mail them to ubuntu-devel or post them to the release blog (when we [https://rt.admin.canonical.com/Ticket/Display.html?id=27372 get that set up]). Examples of newsworthy items are: New candidate ISOs, important bugfixes (and ask for verification of same).

Release minus 10 days:

  1. Notify developers by mailing [http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce ubuntu-devel-announce]:

  2. Contact Henrik Omma to confirm that all certification bugs are resolved for the freeze
  3. Merge seeds and update metapackages for all releasing derivatives

  4. Notify Michael Vogt to perform a GnomeAppInstallDesktopDatabaseUpdate

  5. Begin UpgradeTestingProcess

  6. Notify Scott James Remnant to perform a ReadaheadListUpdate

  7. Notify James Troup to remind mirrors to check free disk space
    • Include estimate of disk space requirements for pre-publishing the beta release

  8. Announce any pending EOL of an older release (see EndOfLifeProcess)

Release minus 7 days:

  1. Announce the beta freeze on the #ubuntu-devel topic and [http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce ubuntu-devel-announce]. There is generally no need to tell people to hold off on uploads, as they will be held automatically by Soyuz once the next task is performed.

  2. Set the distrorelease status to FROZEN in Launchpad

  3. Review problems and file targeted bugs for those which need resolution for the beta:
  4. Selectively accept package uploads to resolve targeted bugs

  5. Ask the marketing team (ubuntu-marketing@lists.ubuntu.com) to prepare a web page about the changes since the last milestone

  6. Notify Matthew Nuzum about setting up http://www.ubuntu.com/getubuntu/download for the Beta release

Release minus 3 days:

  1. All CD-related problems should be resolved, and the archive consistent

  2. Repeat UpgradeTestingProcess

  3. Notify Adam Conrad to begin rebuild testing
  4. Stop all live filesystem and cdimage cron jobs

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

  6. Produce full set of images

  7. Notify Henrik Omma to begin ReleaseValidationProcess

  8. Notify Henrik Omma to begin https://wiki.canonical.com/CertificationTestingProcess (private due to agreements with vendors)

  9. Iteratively test and accept select showstopper fixes
    • Make sure to clear the testing grid for each iteration

Release minus 1 day:

  1. Prepare the release announcement

    • Review -changes mailing list since the last milestone to make sure that all relevant major changes have been documented in the milestone's web page

    • 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 Matt Zimmerman, ubuntu-doc@lists.ubuntu.com to proofread the announcement and suggest changes

  2. Review beta-targeted bugs and take final decisions on what to fix and what to defer
  3. Pre-publish the CD images

Release minus 15 minutes:

  1. Publish the CD images. This requires mangling the HEADER.html in the top-level directory as well as in the kubuntu/ and edubuntu/ subdirectories. Also make sure to create symlinks from the version number to the codename in the same directory. Also remember to change top-level .htaccess.

  2. Remove any not-yet-official warnings from the announcement and release notes
  3. Verify that all mirrors listed in the announcement or release notes have images, and remove faulty mirrors
  4. Check torrents for proper functionality

Release:

  1. Update the topic on #ubuntu-devel

  2. Send the release announcement to ubuntu-announce

  3. Notify Matthew Nuzum to put the announcement on the website
    • News sidebar

    • /testing

  4. Post announcement to [http://www.ubuntuforums.org/forumdisplay.php?f=13 News & Announcements section] (FIXME: who has posting rights? How do we get this done?)

Release plus 1 day:

  1. Revert changes to debian-cd/CONF.sh

  2. Turn live filesystem and cdimage cron jobs back on.

  3. Notify Adam Conrad to begin BuildTestProcess

  4. Notify Malcolm Yates to contact Canonical ISV partners for new builds of commercial software packages

  5. Set the distrorelease back to DEVELOPMENT in Launchpad

  6. Clear out any pending entries in the UNAPPROVED queue

  7. Call for translations
  8. If any changes were made to this document in this run, check whether the changes also apply to the other release process documents as well.

Outstanding issues

  • Publishing DVD images? (Those should usually just be published to cdimage, but it's probably worth putting them in the list).

CategoryProcess

BetaProcess (last edited 2021-09-24 20:52:01 by brian-murray)