NewReleaseCycleProcess

Revision 89 as of 2011-10-19 15:19:52

Clear message

Contents

  1. Goals
  2. Stages
    1. Previous release minus 1 month
    2. Previous release minus 2 weeks
    3. Previous release plus 1 day
    4. First weeks, after toolchain complete

To be carried out by: LaMont Jones and Ubuntu Release Manager

Goals

  • Unblock development process for new release as quickly as possible.
  • Prepare for first milestone CD release.

Stages

Bugs related to this process are tagged with new-release-cycle-process. If you discover new glitches or things that can be automated, please file a bug with that tag.

Previous release minus 1 month

  1. Contact Soyuz development/production teams to ensure there are no known outstanding issues that will prevent on-time opening of the new distroseries.
  2. Remind toolchain developers to begin preparing the new toolchain.
  3. Confirm final schedule for the new release and communicate key release dates
    • Create codenameReleaseSchedule page

    • Update ReleaseSchedule

    • Update Fridge calendar?
    • Canonical calendars

Previous release minus 2 weeks

  1. Double-check with Soyuz development/production teams.

  2. Ask for the maillist distroseries-changes to be set up by sending email to ubuntu-platform@rt.canonical.com to file an RT ticket.

Previous release plus 1 day

  1. Create new seed branches based on those for the previous release, and push them to the appropriate subdirectories of bzr+ssh://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/.

  2. Notify Colin Watson to set up seed mirrors and germinate output for the new distroseries.

  3. Reject any queued uploads to RELEASE pocket of previous distroseries.

  4. Disable the Soyuz publisher cron jobs.

  5. Notify a Launchpad admin to create new distroseries with status FROZEN.

  6. Create a milestone named ubuntu-$version in the release

  7. Check that the new distroseries exists with status FROZEN, and that the previous distroseries has status CURRENT.

  8. Create symbolic links /srv/launchpad.net/ubuntu-archive/ubuntu-misc/more-extra.override.DSN.restricted -> more-extra.override.DSN.main, /srv/launchpad.net/ubuntu-archive/ubuntu-misc/more-extra.override.DSN.universe -> more-extra.override.DSN.main, and /srv/launchpad.net/ubuntu-archive/ubuntu-misc/more-extra.override.DSN.multiverse -> more-extra.override.DSN.main on cocoplum, where DSN is the new distroseries name.

  9. Visit http://launchpad.net/ubuntu/<series> and click "Initialize Series" in the top right menu. Select which Debian parents you want for this series (it defaults to the existing ones), which architectures you want, ensure "Copy Source And Binaries" is selected and click the "Initialize Series" button.

  10. Notify a LOSA to run branch-distro to initialize branches for the new series.

  11. Re-enable the Soyuz publisher cron jobs and wait for the first run to complete.

  12. As lp_archive, use compare-archives to compare dists trees for previous and current distroseries and sign off on any differences; the only differences should be the distroseries name, that custom uploads (installer-*, dist-upgrader-all, and i18n) are missing from dists/DSN/main, that Release.gpg does not yet exist (this will be created when the full publisher cron job next runs), and that Contents-*.gz do not yet exist (these will be created when generate-contents next runs).

  13. Verify that the partner repository has been created on archive.canonical.com as a result of this process; if not, notify the Soyuz developers to fix it and check that this happens.

  14. Notify LaMont Jones to upload new buildd chroots (which can be copied from the previous distroseries), and to upload fresh tarballs for the just-released distroseries as well for efficiency.

  15. Add a request to Launchpad devs and admins to open Launchpad translations for the new distroseries.

  16. Notify Colin Watson to modify various reports (britney, architecture-mismatches, component-mismatches, priority-mismatches) to point to the new distroseries.

  17. Notify Colin Watson to set up merge-o-matic to point to the new distroseries.

  18. Notify toolchain developers to upload new toolchain. Iterate uploads as necessary until this has successfully built on all architectures.

  19. Notify a Launchpad admin to set the status of the new distroseries to DEVELOPMENT.

  20. Notify a Launchpad admin to enable PPAs for the new distroseries by enabling virtualization support on https://launchpad.net/ubuntu/DSN/{i386,amd64,armel}/+admin

  21. Check with a LOSA that branch-distro has completed.

  22. Notify canonical-bazaar or a LOSA to restart package-import with support for the new distroseries.

  23. Inform #ubuntu-devel and ubuntu-devel-announce that the new release is now open for uploads, pointing to merge-o-matic output.

  24. Check whether there are any uploads in the previous release's -updates pocket not in the new release, and copy them over if so.

  25. Create data/RELEASE, tools/RELEASE, and tools/boot/RELEASE directories in debian-cd based on corresponding directories for the previous release. Set OFFICIAL to "Alpha" in CONF.sh for the new release. Adjust cdimage code to be aware of the new release.

  26. Ask LaMont Jones to bootstrap the build-RELEASE-live chroot on the buildds for the livefs builds

  27. Update UbuntuDevelopment, ArchiveAdministration to reflect the code name of the current release

  28. Notify Michael Vogt to update the default release in popcon.ubuntu.com and update the component list

  29. Notify a member of the InstallerTeam to add the introductory message back to Ubiquity.

  30. Notify James Westby to enable kerneloops.
  31. Target issues from the previous release's release notes to be fixed in the new release.
  32. Update vmbuilder so that it can build VMs for the new release

First weeks, after toolchain complete

  1. Notify 'ubuntu-devel' and 'ubuntu-devel-announce' that the release is now open and where to subscribe to the release'-changes' maillist.

  2. Review the people listed in '!regression-alert' (StableReleaseUpdates#Regressions) as needed. '!regression-alert' is handled by ubotto and flagged in #ubuntu-devel. Changes can be made and tested in #ubuntu-ops. The people listed should be the tech leads for foundations, desktop, server, security, and QA, along with the release manager and key community members.

  3. Merge base-files if necessary and change /etc/issue, /etc/issue.net, and /etc/lsb-release to refer to the new release.

  4. Merge debootstrap if necessary and create a bootstrap script for the new release as a copy of the previous one (currently, we can just make the new one a symlink to gutsy, as it hasn't changed since then).

  5. Merge devscripts, lintian, vim, emacs-goodies-el, system-tools-backends, and clang if necessary and update lists of Ubuntu release names to include the new release name.

  6. Update /usr/share/python-apt/templates/Ubuntu.info in python-apt to include the new release name.

  7. Merge cdrom-detect, choose-mirror, and iso-scan if necessary and update cdrom/suite and /mirror/suite debconf templates to include a choice for the new release and update any previous default.

  8. Merge the rest of the installer in dependency order, ending with debian-installer once all other installer components have built successfully on all architectures.

  9. Notify ubiquity maintainer(s) to run debian/rules update, adjust as necessary to account for changes, and upload.

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

  11. Add the date of the previous release to calendar.ubuntu in bsdmainutils

  12. QA team will triage the +nominations bugs list, declining non-SRU candidate nominations and re-target bugs. The release team will evaluate the remaining list, accepting good SRU candidates

  13. Notify web team to reset http://www.ubuntu.com/testing to indicate no testing in progress, and reference new release.

  14. Continue on MilestoneProcess.

CategoryProcess