BetaProcess

Differences between revisions 1 and 40 (spanning 39 versions)
⇤ ← Revision 1 as of 2007-09-14 11:16:07 →
Size: 5742
Editor: 82-69-40-219
Comment: moved from Canonical wiki
← Revision 40 as of 2010-03-13 06:48:45 → ⇥
Size: 7616
Editor: minbar
Comment: Rick -> Jos
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 22: Line 22:
  * 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|NBS]] list
 1. Contact Marjo Mercado to confirm that all certification bugs are resolved for the freeze
Line 26: Line 27:
 1. Notify Evan Dandrea to remove the disclaimer from Ubiquity's first page
Line 27: Line 29:
 1. Notify Scott James Remnant to perform a ReadaheadListUpdate
Line 31: Line 32:
 1. Contact Gerry Carr and [[mailto:matthew.nuzum@canonical.com|Matthew Nuzum]] 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)
Line 34: Line 37:
 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. 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.
Line 38: Line 41:
  * Live filesystem build failures   * [[http://people.ubuntu.com/~ubuntu-archive/livefs-build-logs/|Live filesystem build failures]]
Line 43: Line 46:
  * Pending anastacia promotions   * Pending [[http://people.ubuntu.com/~ubuntu-archive/component-mismatches.txt|main promotions]]
Line 46: Line 49:
 1. Ask the marketing team (ubuntu-marketing@lists.ubuntu.com) to prepare a web page about the changes since the last milestone  1. Ask the marketing team (ubuntu-marketing@lists.ubuntu.com) to prepare a web page about the changes since the last milestone. CC product owners (Rick Spencer, Jos Boumans, David Mandala) and Marketing (Gerry Carr) for validation.
 1. Notify Matthew Nuzum about setting up http://www.ubuntu.com/getubuntu/download for the Beta release
 1. Check with Canonical marketing to see whether there will be a press release to coordinate for Beta
Line 53: Line 58:
  * Pending anastacia promotions   * Pending [[http://people.ubuntu.com/~ubuntu-archive/component-mismatches.txt|main promotions]]
Line 55: Line 60:
 1. Notify Adam Conrad to begin rebuild testing  1. Notify Colin Watson (or other buildd admin) to begin rebuild testing
Line 59: Line 64:
 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 Marjo Mercado to begin ReleaseValidationProcess
 1. Notify Marjo Mercado to begin https://wiki.canonical.com/UbuntuPlatform/HardwareCertification/Process (private due to agreements with vendors)
Line 63: Line 68:

Release minus 2 days:
 1. Request input for the beta announcement from the leads of the community products
Line 70: Line 78:
  * Notify Matt Zimmerman, `ubuntu-doc@lists.ubuntu.com` to proofread the announcement and suggest changes   * Notify Matt Zimmerman, `ubuntu-doc@lists.ubuntu.com` to proofread the announcement and suggest changes, CC product owners (Rick Spencer, Rick Clark, David Mandala) and Marketing (Gerry Carr).
Line 76: Line 84:
 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. Publish the CD images. This requires mangling the `.htaccess` and the `HEADER.html` in the top-level directory as well as in the `kubuntu/` and `edubuntu/` subdirectories, and trimming all images not related to the current release from the .manifest file so that full mirror probes are possible in a timely manner.
Line 84: Line 92:
 1. Send the release announcement to `ubuntu-announce`
Line 88: Line 95:
 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. Ask Ryan Troy to post announcement to [[http://www.ubuntuforums.org/forumdisplay.php?f=13|News & Announcements section]]
 1. Post announcement to [[https://launchpad.net/ubuntu/+announce|Launchpad]] ([[https://launchpad.net/~ubuntu-drivers/+members|ubuntu-drivers members]] have posting rights)
Line 94: Line 104:
 1. Notify Adam Conrad to begin BuildTestProcess
 1. Notify Malcolm Yates to contact Canonical ISV partners for new builds of commercial software packages		  1. Notify Zaid Al Hamami to contact Canonical ISV partners for new builds of commercial software packages
Line 102: Line 111:
 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 113:
 1. Begin preliminary steps from NewReleaseCycleProcess.
 1. Continue on MilestoneProcess or ReleaseCandidateProcess, as appropriate.
Line 107: Line 119:


----
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 Marjo Mercado 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. 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 Gerry Carr and Matthew Nuzum 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)

Release minus 7 days:

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

  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. CC product owners (Rick Spencer, Jos Boumans, David Mandala) and Marketing (Gerry Carr) for validation.

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

  7. Check with Canonical marketing to see whether there will be a press release to coordinate for Beta

Release minus 3 days:

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

  2. Repeat UpgradeTestingProcess

  3. Notify Colin Watson (or other buildd admin) 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 Marjo Mercado to begin ReleaseValidationProcess

  8. Notify Marjo Mercado to begin https://wiki.canonical.com/UbuntuPlatform/HardwareCertification/Process (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 2 days:

  1. Request input for the beta announcement from the leads of the community products

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, CC product owners (Rick Spencer, Rick Clark, David Mandala) and Marketing (Gerry Carr).

  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 .htaccess and the HEADER.html in the top-level directory as well as in the kubuntu/ and edubuntu/ subdirectories, and trimming all images not related to the current release from the .manifest file so that full mirror probes are possible in a timely manner.

  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. Notify Matthew Nuzum 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. Ask Ryan Troy to post announcement to News & Announcements section

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

Release plus 1 day:

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

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

  4. Set the distrorelease back to DEVELOPMENT in Launchpad

  5. Clear out any pending entries in the UNAPPROVED queue

  6. Call for translations

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

  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.

  9. Begin preliminary steps from NewReleaseCycleProcess.

  10. Continue on MilestoneProcess or ReleaseCandidateProcess, as appropriate.

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)