BetaProcess

To be carried out by the Ubuntu release team and flavor release team managers.

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:

opt-in beta

final beta

task

x

x

Notify developers by mailing ubuntu-devel-announce:
* Pointer to beta milestone page (in launchpad)
* Reminder of beta freeze
* Send UserInterfaceFreeze reminder to ubuntu-devel, ubuntu-translators and ubuntu-doc, pointing out to the freeze exception process
* Toolchain freeze begins
* Request to avoid and eliminate PackageInconsistencies
* Target any relevant bugs to the beta milestone
* Review component mismatches and file any necessary main inclusion reports
* Clear the NBS list

x

x

Update metapackages for all releasing derivatives

x

Notify Michael Vogt to perform a GnomeAppInstallDesktopDatabaseUpdate

x

Run ./update-from-web.sh in command-not-found and upload to Ubuntu

x

Begin UpgradeTestingProcess

x

Contact Ara Pulido to check if any critical certification bugs remain to be resolved

x

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

x

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

x

Contact Canonical Marketing (IRC: vanessa, sian) and Web Team (#web-team on canonical; email: webteam@canonical.com) 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

x

Notify the web team (#web-team on canonical; email: webteam@canonical.com) to update http://www.ubuntu.com/testing/download for the beta

x

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

x

Notify DavidPlanella (ubuntu-translation-coordinators) to coordinate a fresh set of language packs which will be exported, uploaded, and built in time for beta.

x

x

Notify JonathanRiddell to regenerate kubuntu-patched-l10n

Release minus 7 days:

opt-in beta

final beta

task

x

Notify Ubuntu, Kubuntu and other flavour contacts to create and update their Upgrade docs at https://help.ubuntu.com/community/{{{$release}}}Upgrades

x

x

Review problems and file targeted bugs for those which need resolution for the beta:
* PackageInconsistencies
* Live filesystem build failures
* Installation bugs
* Upgrade bugs
* High-severity bugs
* Hardware support regressions
* Pending main promotions
* Oversized ISOs

x

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

x

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

x

x

Review iso. and confirm signoffs are accurate.

Release minus 6 days

opt-in beta

final beta

task

x

x

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

x

Collect marketing input for beta release notes
* Ask the marketing team (ubuntu-marketing@lists.ubuntu.com) if they have input.
* Check with Marketing (Vanessa Sammut) for themes to highlight.

x

x

prepare the ISO tracker for the milestone and make it the default
* marked as "automatically publish" (so no need to change isotracker configuration on cdimage)
* lists the new milestone
* has all the images listed on the ReleaseManifest

x

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

x

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

Release minus 3 days:

opt-in beta

final beta

task

x

x

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.

x

x

Block migration from -proposed of packages on images (Iain Lane has a script to generate the block)

x

x

Selectively accept package uploads to resolve targeted bugs

x

x

All CD-related problems should be resolved, and the archive consistent
* PackageInconsistencies
* Live filesystem build failures
* Pending main promotions

x

x

Notify Colin Watson (or other buildd admin) to begin rebuild testing

x

x

Stop all live filesystem and cdimage cron jobs

x

x

Modify debian-cd/CONF.sh to set OFFICIAL

x

x

Produce full set of images

x

Notify Ubuntu QA team (jibel) to begin ReleaseValidationProcess

x

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

x

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

x

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

x

x

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

x

x

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

Release minus 2 day:

opt-in beta

final beta

task

x

x

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(s) to make sure that any caveats and warnings present in the image are documented.

x

x

Prepare the release announcement

x

x

Review beta-targeted bugs and take final decisions on what to fix and what to defer

Release minus 1 day:

opt-in beta

final beta

task

x

x

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

x

x

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

Release minus a couple of hours:

opt-in beta

final beta

task

x

x

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

x

x

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

x

x

Copy .manifest to .manifest.full, pruning all images from previous releases from the .manifest file to allow timely mirror probing.

x

x

Remove any not-yet-official warnings from the announcement and release notes

x

x

Verify that all mirrors listed in the announcement or release notes have images, and remove faulty mirrors

x

x

Check torrents for proper functionality

x

x

Ensure Server Cloud team publishes cloud images (IRC: utlemming)

Release:

opt-in beta

final beta

task

x

x

Update the topic on #ubuntu-devel

x

Notify the web team (#web-team on canonical; email: webteam@canonical.com) to put the announcement on the website
* News sidebar
* /testing

x

Send the release announcement to ubuntu-devel-announce

x

Send the release announcement to ubuntu-announce

x

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

x

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

x

x

Add a note, atop wiki pages for previous alphas/betas, to point to the just-released one

x

x

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

x

x

Turn live filesystem and cdimage cron jobs back on.

x

x

Mark the milestone inactive in Launchpad ?? this is no longer accurate, closest month? what should trigger the month milestones being marked inactive now??

Release plus 1 day:

opt-in beta

final beta

task

x

x

Revert changes to debian-cd/CONF.sh

x

Notify Zaid Al Hamami to contact Canonical ISV partners for new builds of commercial software packages

x

Call for translations
* Send to ubuntu-translators@lists.ubuntu.com
* Reminder of deadlines for both langpackable and non-langpackable translations
* Include current translation statistics

x

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

x

x

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.

x

Begin preliminary steps from NewReleaseCycleProcess.

x

Continue on BetaProcess

x

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

x

Change daily builds to comment out any architectures that have not been tested during this point (that we are not releasing).

x

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 2014-04-17 18:27:43 by brian-murray)