BetaProcess

Differences between revisions 1 and 79 (spanning 78 versions)
⇤ ← Revision 1 as of 2007-09-14 11:16:07 →
Size: 5742
Editor: 82-69-40-219
Comment: moved from Canonical wiki
← Revision 79 as of 2012-10-02 11:58:34 → ⇥
Size: 11260
Editor: mpt
Comment: + point people forward to the latest release
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
To be carried out by: Martin Pitt, with support from the [https://launchpad.net/~ubuntu-release Ubuntu release team] To be carried out by: Ubuntu Release Manager, with support from the [[https://launchpad.net/~ubuntu-release|Ubuntu release team]]
Line 12: Line 12:
 * Check if there are newsworthy items and either mail the to `ubuntu-devel` or post them to the release blog (when we get that set up. Examples of newworthy items are: New candidate ISOs, important bugfixes (and ask for verification of same).  * Check if there are newsworthy items and either mail them to `ubuntu-devel` or post them to the [[http://release-blog.ubuntu.com|release blog]]. Examples of newsworthy items are: New candidate ISOs, important bugfixes (and ask for verification of same).
Line 16: Line 16:
 1. Notify developers by mailing [http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce ubuntu-devel-announce]:  1. Notify developers by mailing [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce|ubuntu-devel-announce]]:
Line 19: Line 19:
  * Send UserInterfaceFreeze reminder to `ubuntu-devel`, `ubuntu-translators` and `ubuntu-doc`, pointing out to the [[FreezeExceptionProcess#UserInterfaceFreeze%20Exceptions| freeze exception process]]
Line 22: Line 23:
  * Review anastacia output and file any necessary main inclusion reports
 1. Contact Fabio to confirm that all certification bugs are resolved for the freeze		   * Review [[http://people.ubuntu.com/~ubuntu-archive/component-mismatches.txt|component mismatches]] and file any necessary [[UbuntuMainInclusionQueue|main inclusion reports]]
  * Clear the [[http://people.ubuntu.com/~ubuntu-archive/nbs.html|NBS]] list
 1. Contact Ara Pulido to check if any critical certification bugs remain to be resolved
Line 26: Line 28:
 1. Notify Evan Dandrea to remove the disclaimer from Ubiquity's first page
Line 27: Line 30:
 1. Notify Scott James Remnant to perform a ReadaheadListUpdate
Line 31: Line 33:
 1. Contact Marketing (IRC: vanessa, sian) and Web Team (IRC: steveedwards) to confirm the date of the final release, to ensure they have time to prepare the website (this includes preparing http://www.ubuntu.com/getubuntu/download), and inquire whether there will be a press release to coordinate for Beta
 1. On initial Beta only, Work with Marketing Communications (IRC: cezzamanizzle) and development teams to specify out minimum installation configurations and any liner notes for CD/DVDs for products.
 1. Notify DavidPlanella to coordinate a fresh set of language packs which will be exported, uploaded, and built in time for beta.
Line 34: Line 40:
 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.
 1. Set the distrorelease status to `FROZEN` in Launchpad		  1. Notify Michael Vogt to have update-manager say that it's a beta release instead of an alpha
 1. Announce the beta freeze on the `#ubuntu-devel` topic, [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce|ubuntu-devel-announce]], and [[https://release-blog.ubuntu.com/wp-admin/edit.php|http://release-blog.ubuntu.com/]]. 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.
 1. Ask LOSA to set the distrorelease status to `PRE-RELEASE FREEZE` in Launchpad
 1. Notify Ubuntu, Kubuntu and other flavour contacts to create and update their Upgrade docs at https://help.ubuntu.com/community/PreciseUpgrades
Line 38: Line 46:
  * Live filesystem build failures   * [[http://people.ubuntu.com/~ubuntu-archive/livefs-build-logs/|Live filesystem build failures]]
Line 43: Line 51:
  * Pending anastacia promotions   * Pending [[http://people.ubuntu.com/~ubuntu-archive/component-mismatches.txt|main promotions]]
Line 46: Line 54:
 1. Ask the marketing team (ubuntu-marketing@lists.ubuntu.com) to prepare a web page about the changes since the last milestone  1. Ask ubuntu-doc for help in preparing https://help.ubuntu.com/community/{{{$release}}}Upgrades
 1. Ask developers (ubuntu-devel-announce) to mark their features as "Beta Available" or "Complete" in https://blueprints.launchpad.net/ubuntu/{{{$release}}}/+specs
 1. Review ReleaseManifest list and confirm signoffs are updated.

Release minus 6 days
 1. Set up framework for beta release notes
    * Review bugs from last milestone and remove those fixed.
    * Ask the marketing team (ubuntu-marketing@lists.ubuntu.com) if they have input.
    * ask product owners (see ReleaseManifest list) for input to release notes.
    * Check with Marketing (Vanessa Sammut) for themes to highlight.
 1. prepare the ISO tracker for the milestone and make it the default
    * lists the new milestone
    * has all the images listed on the ReleaseManifest
    * Edit `default_milestone` in `~cdimage/.isotracker.conf` to match the new milestone name in the ISO tracker
 1. Check with QA (#ubuntu-testing, IRC:jibel) on results of cdrom upgrades and manual installation smoke tests.
 1. Notify the web team (#web-team on canonical) about setting up http://www.ubuntu.com/testing for the Beta release, include anticipated list of ISO image file names.
 1. Discuss with ?? ( was: Matthew Nuzum and Jonathan Davies) anticipated sizes of ISO images and determine if any mirroring issues.
Line 49: Line 73:
 
Line 53: Line 77:
  * Pending anastacia promotions
 1. Repeat UpgradeTestingProcess
 1. Notify Adam Conrad to begin rebuild testing		   * Pending [[http://people.ubuntu.com/~ubuntu-archive/component-mismatches.txt|main promotions]]
 1. Notify Colin Watson (or other buildd admin) to begin rebuild testing
Line 59: Line 82:
 1. Notify Henrik Omma to begin ReleaseValidationProcess
 1. Notify Fabio Massimo Di Nitto to begin https://wiki.canonical.com/CertificationTestingProcess (private due to agreements with vendors)		  1. Notify Ubuntu QA team (jibel) to begin ReleaseValidationProcess
 1. Notify Hardware Certification team (ara) to begin https://wiki.canonical.com/UbuntuPlatform/HardwareCertification/Process (private due to agreements with vendors)
 1. Notify commercial engineering QA team (email: jeffrey.chang@canonical.com AND cc: steve.magoun@canonical.com) to begin testing.
 1. Notify commercial engineering (email: david.murphy@canonical.com AND cc: ce-infrastructure@lists.canonical.com; IRC: schwuk) that the archive is in a consistent state
Line 63: Line 88:
 1. Request input for the beta announcement from the leads of the community products

Release minus 2 day:
 1. Update the TechnicalOverview with the changes for this release (including community input)
  * Work with development leads to make sure that highlights of changes since last milestone, are overviewed.
  * Work with QA team to make sure that any caveats and warnings present in the image are documented.
 1. Prepare the release announcement
 1. Review beta-targeted bugs and take final decisions on what to fix and what to defer
Line 65: Line 98:
 1. Update TechnicalOverview with the bugs found from testing that are not going to be fixed.
 1. Pre-publish the CD images: `./publish-image-set.py --prepublish` (from [[https://code.launchpad.net/+branch/ubuntu-archive-tools|lp:ubuntu-archive-tools]]) will print the necessary commands.
Line 66: Line 101:
 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
 1. Review beta-targeted bugs and take final decisions on what to fix and what to defer
 1. Pre-publish the CD images		 Release minus a couple of hours:
Line 74: Line 103:
Release minus 15 minutes:

 1. Publish the CD images. This requires mangling the `HEADER.html` in the top-level directory. Also make sure to create symlinks from the version number to the codename in the same directory. Also remember to change top-level .htaccess		  1. Review the testing status of images and ensure all have been tested before being released.
 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 add an entry for the new beta release, 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, pruning all images from previous releases from the .manifest file to allow timely mirror probing.
Line 80: Line 110:
 1. Ensure Server Cloud team publishes cloud images (IRC: utlemming)
Line 84: Line 115:
 1. Send the release announcement to `ubuntu-announce`
 1. Notify Matthew Nuzum to put the announcement on the website		  1. Notify the web team (ellen.arnold@canonical.com, IRC: ellend) to put the announcement on the website
Line 88: Line 118:
 1. 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?)  1. Send the release announcement to `ubuntu-announce`
 1. Post an announcement on [[https://release-blog.ubuntu.com/wp-admin/edit.php|http://release-blog.ubuntu.com/]]
 1. Post announcement to [[https://launchpad.net/ubuntu/+announce|Launchpad]] ([[https://launchpad.net/~ubuntu-drivers/+members|ubuntu-drivers members]] have posting rights)
  * Use ubuntu-announce email subject as Headline
  * Use ubuntu-announce email body intro as the Summary
  * Use the mailing list archive URL for the ubuntu-announce email as the URL
 1. Add a note, atop wiki pages for previous alphas/betas, to point to the just-released one
Line 93: Line 129:
 1. Change `default_milestone` in `~cdimage/.isotracker.conf` back to "Precise Daily" (etc.)
Line 94: Line 131:
 1. Notify Adam Conrad to begin BuildTestProcess
 1. Notify Malcolm Yates to contact Canonical ISV partners for new builds of commercial software packages
 1. Set the distrorelease back to `DEVELOPMENT` in Launchpad		  1. Notify Zaid Al Hamami to contact Canonical ISV partners for new builds of commercial software packages
 1. Ask LOSA to set the distrorelease back to `DEVELOPMENT` in Launchpad
 1. Once the distrorelease is set back to `DEVELOPMENT`, flush all packages in the unapproved queue to the archive
 1. Mark the milestone inactive in Launchpad
Line 102: Line 140:
 1. If this will be an LTS release, notify `ubuntu-devel-announce` of any special post-release support plans, such as point releases
Line 103: Line 142:
 1. Begin preliminary steps from NewReleaseCycleProcess.
 1. Continue on MilestoneProcess or ReleaseCandidateProcess, as appropriate.
 1. If this is the last beta before ReleaseCandidateProcess,
  * 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.
  * Set the Final Freeze date (typically at release minus 1.5 days) for universe/multiverse for the packages that are NOT found on any installation media.
  * Broadcast universe/multiverse delegates and final freeze date to ubuntu-devel.
Line 104: Line 149:
== Outstanding issues ==  1. Change daily builds to comment out any architectures that have not been tested during this point (that we are not releasing).
 1. Security team: audit the set of kernel source packages in main to confirm that there are maintenance resources for each of these.
Line 106: Line 152:
 * Publishing DVD images? (Those should usually just be published to cdimage, but it's probably worth putting them in the list). ----
CategoryProcess

To be carried out by: Ubuntu Release Manager, with support from the 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. 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 ubuntu-devel-announce:

  2. Contact Ara Pulido to check if any critical certification bugs remain to be resolved
  3. Merge seeds and update metapackages for all releasing derivatives

  4. Notify Michael Vogt to perform a GnomeAppInstallDesktopDatabaseUpdate

  5. Notify Evan Dandrea to remove the disclaimer from Ubiquity's first page

  6. Begin UpgradeTestingProcess

  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)

  9. Contact Marketing (IRC: vanessa, sian) and Web Team (IRC: steveedwards) to confirm the date of the final release, to ensure they have time to prepare the website (this includes preparing http://www.ubuntu.com/getubuntu/download), and inquire whether there will be a press release to coordinate for Beta

  10. On initial Beta only, Work with Marketing Communications (IRC: cezzamanizzle) and development teams to specify out minimum installation configurations and any liner notes for CD/DVDs for products.

  11. Notify DavidPlanella to coordinate a fresh set of language packs which will be exported, uploaded, and built in time for beta.

Release minus 7 days:

  1. Notify Michael Vogt to have update-manager say that it's a beta release instead of an alpha

  2. Announce the beta freeze on the #ubuntu-devel topic, ubuntu-devel-announce, and http://release-blog.ubuntu.com/. 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.

  3. Ask LOSA to set the distrorelease status to PRE-RELEASE FREEZE in Launchpad

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

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

  7. Ask ubuntu-doc for help in preparing https://help.ubuntu.com/community/{{{$release}}}Upgrades

  8. Ask developers (ubuntu-devel-announce) to mark their features as "Beta Available" or "Complete" in https://blueprints.launchpad.net/ubuntu/{{{$release}}}/+specs

  9. Review ReleaseManifest list and confirm signoffs are updated.

Release minus 6 days

  1. Set up framework for beta release notes
    • Review bugs from last milestone and remove those fixed.

    • Ask the marketing team (ubuntu-marketing@lists.ubuntu.com) if they have input.

    • ask product owners (see ReleaseManifest list) for input to release notes.

    • Check with Marketing (Vanessa Sammut) for themes to highlight.
  2. prepare the ISO tracker for the milestone and make it the default
    • lists the new milestone

    • has all the images listed on the ReleaseManifest

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

  3. Check with QA (#ubuntu-testing, IRC:jibel) on results of cdrom upgrades and manual installation smoke tests.

  4. Notify the web team (#web-team on canonical) about setting up http://www.ubuntu.com/testing for the Beta release, include anticipated list of ISO image file names.

  5. Discuss with ?? ( was: Matthew Nuzum and Jonathan Davies) anticipated sizes of ISO images and determine if any mirroring issues.

Release minus 3 days:

  1. All CD-related problems should be resolved, and the archive consistent
  2. Notify Colin Watson (or other buildd admin) to begin rebuild testing
  3. Stop all live filesystem and cdimage cron jobs

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

  5. Produce full set of images

  6. Notify Ubuntu QA team (jibel) to begin ReleaseValidationProcess

  7. Notify Hardware Certification team (ara) to begin https://wiki.canonical.com/UbuntuPlatform/HardwareCertification/Process (private due to agreements with vendors)

  8. Notify commercial engineering QA team (email: jeffrey.chang@canonical.com AND cc: steve.magoun@canonical.com) to begin testing.

  9. Notify commercial engineering (email: david.murphy@canonical.com AND cc: ce-infrastructure@lists.canonical.com; IRC: schwuk) that the archive is in a consistent state

  10. Iteratively test and accept select showstopper fixes
    • Make sure to clear the testing grid for each iteration
  11. Request input for the beta announcement from the leads of the community products

Release minus 2 day:

  1. Update the TechnicalOverview with the changes for this release (including community input)

    • Work with development leads to make sure that highlights of changes since last milestone, are overviewed.
    • Work with QA team to make sure that any caveats and warnings present in the image are documented.
  2. Prepare the release announcement
  3. Review beta-targeted bugs and take final decisions on what to fix and what to defer

Release minus 1 day:

  1. Update TechnicalOverview with the bugs found from testing that are not going to be fixed.

  2. Pre-publish the CD images: ./publish-image-set.py --prepublish (from lp:ubuntu-archive-tools) will print the necessary commands.

Release minus a couple of hours:

  1. Review the testing status of images and ensure all have been tested before being released.

  2. 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 add an entry for the new beta release, since neither publish-release nor publish-image-set.py is yet smart enough to do the right thing there.

  3. Copy .manifest to .manifest.full, pruning all images from previous releases from the .manifest file to allow timely mirror probing.
  4. Remove any not-yet-official warnings from the announcement and release notes
  5. Verify that all mirrors listed in the announcement or release notes have images, and remove faulty mirrors
  6. Check torrents for proper functionality
  7. Ensure Server Cloud team publishes cloud images (IRC: utlemming)

Release:

  1. Update the topic on #ubuntu-devel

  2. Notify the web team (ellen.arnold@canonical.com, IRC: ellend) to put the announcement on the website

    • News sidebar

    • /testing

  3. Send the release announcement to ubuntu-announce

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

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

    • Use ubuntu-announce email subject as Headline
    • Use ubuntu-announce email body intro as the Summary
    • Use the mailing list archive URL for the ubuntu-announce email as the URL
  6. Add a note, atop wiki pages for previous alphas/betas, to point to the just-released one

Release plus 1 day:

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

  2. Change default_milestone in ~cdimage/.isotracker.conf back to "Precise Daily" (etc.)

  3. Turn live filesystem and cdimage cron jobs back on.
  4. Notify Zaid Al Hamami to contact Canonical ISV partners for new builds of commercial software packages

  5. Ask LOSA to set the distrorelease back to DEVELOPMENT in Launchpad

  6. Once the distrorelease is set back to DEVELOPMENT, flush all packages in the unapproved queue to the archive

  7. Mark the milestone inactive in Launchpad

  8. Clear out any pending entries in the UNAPPROVED queue

  9. Call for translations

  10. If this will be an LTS release, notify ubuntu-devel-announce of any special post-release support plans, such as point releases

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

  12. Begin preliminary steps from NewReleaseCycleProcess.

  13. Continue on MilestoneProcess or ReleaseCandidateProcess, as appropriate.

  14. If this is the last beta before ReleaseCandidateProcess,

    • 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.
    • Set the Final Freeze date (typically at release minus 1.5 days) for universe/multiverse for the packages that are NOT found on any installation media.
    • Broadcast universe/multiverse delegates and final freeze date to ubuntu-devel.
  15. Change daily builds to comment out any architectures that have not been tested during this point (that we are not releasing).
  16. Security team: audit the set of kernel source packages in main to confirm that there are maintenance resources for each of these.

CategoryProcess

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