To be carried out by: Ubuntu Release Team


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


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. If there is a release scheduled to End of Life, start off EndOfLifeProcess for it.

  3. Remind toolchain developers to begin preparing the new toolchain.
  4. 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 to file an RT ticket.

  3. Subscribe gmane to distroseries-changes mailing list, once it's available.

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 git+ssh:// The branch-seeds script in lp:ubuntu-archive-tools can do the hard work here.

  2. Notify Colin Watson to set up seed mirrors and germinate output for the new distroseries.
  3. Disable the Soyuz publisher cron jobs.
  4. Ensure that the Bazaar package importer on jubany is stopped (Obsolete, placeholder for future replacement).
  5. Notify a Launchpad admin to create new distroseries with status FROZEN.

  6. Create milestones in the new series:
    • ubuntu-$version-month-1 etc., set at monthly intervals after the previous release until feature freeze

    • ubuntu-$version-feature-freeze at feature freeze

    • ubuntu-$version-beta or ubuntu-$version-beta-1 etc. as required

    • ubuntu-$version at the next release date

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

  8. Visit<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.

  9. Notify a webops to run branch-distro to initialize branches for the new series (Obsolete, placeholder for future replacement).

  10. Re-enable the Soyuz publisher cron job for a single publisher run.
  11. Add the new series name to the official Launchpad bug tags, and add verification-needed-PREVIOUS and verification-done-PREVIOUS where PREVIOUS is the name of the previous series.

  12. Ask #webops to run "ANALYZE sourcepackagepublishinghistory; ANALYZE binarypackagepublishinghistory;" on launchpad_prod.
  13. Re-enable the Soyuz publisher cron job for a second publisher run.
  14. As ubuntu-archive@snakefruit, use compare-archives to compare dists trees under ~/mirror/ubuntu/ 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).

  15. Notify Iain Lane (Laney) to run through

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

  17. Grant ~ubuntu-sru queue admin access to the previous distroseries (for pocket in proposed updates; do edit-acl -p ubuntu-sru -S PREVIOUS --pocket $pocket -t admin add; done) and remove ~ubuntu-release's queue admin access (for pocket in release proposed; do edit-acl -p ubuntu-release -S PREVIOUS --pocket $pocket -t admin delete; done).

  18. Check that the process of initialising the new distroseries granted queue admin access to ~ubuntu-release to the new distroseries (edit-acl -p ubuntu-release -S NEW -t admin query).

  19. Move the bootstrap archive on snakefruit to use the new series, so the new chroots can reference it.
  20. Notify Adam Conrad 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.
  21. Add a request to Launchpad devs and admins to open Launchpad translations for the new distroseries.

  22. Modify various reports on snakefruit (at least britney) to point to the new distroseries.

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

  24. Update global.conf in lp:~ubuntu-transition-trackers/ubuntu-transition-tracker/configs

  25. Notify toolchain developers to upload new toolchain. Iterate uploads as necessary until this has successfully built on all architectures.
  26. Make sure that proposed-migration is configured properly for the new series.
    1. Check that<NEWSERIES>/results.cache exists, as required by bileto.

  27. Remove the "block-all source" hint from proposed-migration.
  28. Notify a Launchpad admin to set the status of the new distroseries to DEVELOPMENT.

  29. Check with a webops that branch-distro has completed (Obsolete, placeholder for future replacement).

  30. Notify #launchpad-ops (or someone with access to jubany) to add the new series name in the lp:udd code, pull that change onto the package importer, and restart package-import (Obsolete, placeholder for future replacement).
  31. Inform #ubuntu-devel and ubuntu-devel-announce that the new release is now open for uploads, pointing to merge-o-matic output.

  32. Check whether there are any uploads in the previous release's -updates pocket not in the new release, and copy them over if so.
  33. Copy everything from PREVIOUS-proposed to DEVEL-proposed, and delete the ones from PREVIOUS-proposed that aren't SRUs.
  34. Inform the SRU team that the bulk copy has been done, so that they know to sort out PREVIOUS-proposed vs. DEVEL-proposed for any new SRUs they accept.
  35. Drop the --dry-run flag from the auto-sync job in ubuntu-archive@snakefruit's crontab.

  36. Contact owners of each image with seeded snaps to have snap channels opened and closed for the new release.
  37. Create new live filesystem configurations for the new distroseries, using branch-livefses in lp:ubuntu-archive-tools. This currently needs to be done for OWNER where OWNER is:

    • ubuntu-cdimage
    • cloudware
    • cloud-images-release-managers
  38. 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 for the new release.

  39. Adjust cdimage code to be aware of the new release, and configure ~cdimage/.isotracker.conf

  40. Notify stgraber, vorlon, or bdmurray to follow README.series on db@limequat (the ISO tracker database).
  41. Notify Michael Vogt to update the default release in and update the component list
  42. Target issues from the previous release's release notes to be fixed in the new release.
  43. Notify Brian Murray or a real ~ubuntu-archive member to create an Apport retracer apt configuration (example for 17.04) for the new release and roll it out to porter-i386:/home/ubuntu-archive/config

  44. Check for the new release. (In principle that should happen by itself, but in practice it may crash/hang on not yet having indexes, or run into time outs on the gigantic first import after opening/copying the new release). This is running on numen.canonical.comsudo -u ddebs -i; This has a checkout of lp:ddeb-retriever and is cron driven.

  45. Notify Iain Lane or someone with access to the user update config.json to add the new release to the list in git lp:~ubuntu-desktop/+git/appstream-cloud (*make sure the json is valid*), and then as prod-ue-appstream-back@wendigo run juju set appstream-generator config="$(cat config.json)" after pulling. See 9163c1a2bc5fb3c2c2ba1c27df8f7573a54b4045.

  46. Open an RT to ask IS to create chroots on the porter boxes.
  47. Notify William Grant to update the ftbfs on
  48. Notify Gerfried Fuchs (Rhonda) to update
  49. Notify Iain Lane (Laney) to update people.c.c/~ubuntu-archive/transitions and
  50. Notify Josh Powers (or anybody in ~canonical-server) to update lp:ubuntu-manpage-repository
  51. Notify Brian Murray to update whoopsie-update-daily-users cronjob in the retracer charm owned by the daisy-pluckers team to include the new release of Ubuntu.
  52. Notify Brian Murray to update the Ubuntu Error Tracker for the new release of Ubuntu e.g. errors change and daisy change

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/, /etc/lsb-release, and /etc/os-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 lintian, vim, emacs-goodies-el and clang if necessary and update lists of Ubuntu release names to include the new release name.

  6. Do a no change rebuild of devscripts to pick up the new development release from distro-info.
  7. Do a no change rebuild of app-install-data-partner.
  8. Update /usr/share/python-apt/templates/ in python-apt to include the new release name.

  9. Update ubuntu-release-upgrader to handle the new release e.g. and DistUpgradeQuirks e.g.

  10. Update meta-release to handle the new release.

  11. Update syslinux-themes-ubuntu to handle the new release.

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

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

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

  15. Ensure that postgresql-common is updated for new release

  16. Update the version number in unity-greeter & unity-control-center logos to refer to the new release

  17. Ensure that the ISO tracker has a daily-build "milestone" for the new release
  18. Create ~ubuntu-archive/wubi/RELEASE/ and symlink ~ubuntu-archive/wubi/RELEASE-1/stable to ~ubuntu-archive/wubi/RELEASE/stable

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

  20. Notify canonical-platform-qa ( to set up Utah jobs for Ubuntu desktop and server.

  21. Add new series to production/current-triggers on nusakan.

  22. Turn live filesystem and cdimage cron jobs back on.
  23. Add the date of the previous release to calendar.ubuntu in bsdmainutils

  24. Defect Analysts (or team lead for those teams without Defect Analysts) 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

  25. Notify web team to reset to indicate no testing in progress, and reference new release.

  26. Check to make sure the future+1 and future+2 series is available on launchpad to assign bugs to, if not present, then ask webops on #launchpad-ops to add letter-series, with status Future.
  27. Update to new release, and all linked pages.

  28. Two weeks after new release starts, finish EndofLifeProcess for any old releases scheduled now that we've had some migration overlap.

  29. Update ubuntu-release-notes project to know about the new series.
  30. Ask firefox maintainer to update start page for the new release.

  31. Contact flavours to confirm their ongoing participation in the new release, and verify that the contact in the ISO tracker is still accurate.
  32. Continue on MilestoneProcess.


NewReleaseCycleProcess (last edited 2019-06-13 16:02:36 by cjwatson)