Ubuntu Wiki

To be carried out by: Ubuntu Release Manager

Goals:

• Inform users of a supported Ubuntu release of its imminent end-of-life and corresponding termination of maintenance and support

45 days prior to end of life:

• Send Release End of Life Warning to ubuntu-announce, ubuntu-security-announce

• Notify Amber Graner to add news item to UbuntuWeeklyNewsletter

• Notify the web team manager that ubuntu pages will need to be updated to remove EOL release.

At end of life (generally 2 weeks after a new release starts):

• Set release to OBSOLETE in Launchpad (work with LOSA)

• update http://changelogs.ubuntu.com/meta-release (mvo)

  • set the release to "Supported: 0"
  • update the ReleaseNotesURI so that it points to a EOL page, this informs the user that he is about to upgrade to a already EOL version of the distro

• update https://wiki.ubuntu.com/Releases for Canonical support.

• Deactivate any milestones for the release. Look at https://launchpad.net/ubuntu/$releasename/+milestones

• Archive the release on old-releases on antimony

  • Warning: It may not be possible to follow this procedure entirely mechanically! old-releases is by its nature not very regularly maintained, and the fact that many files are purged from the master system and only exist on mirrors can cause a good deal of confusion. Refer to the publicly-visible structure on http://old-releases.ubuntu.com/releases/. This procedure indicates with some degree of accuracy what steps need to be taken, but anyone following this procedure is strongly advised to use their initiative.

  • In the following instructions, RELEASE should be replaced throughout with the name of the EOLed release. PROJECT is used for flavours of Ubuntu other than Ubuntu itself (e.g. Kubuntu, Edubuntu, etc.).

  • Disable mirror syncing: chmod -x /srv/cdimage.ubuntu.com/bin/sync-mirrors.

  • In /srv/cdimage.ubuntu.com/www/simple/, find all directories named after the EOLed release. In each one:

    • Move all files containing the release number in the adjacent .pool directory to the corresponding .pool subdirectory of /srv/cdimage.ubuntu.com/www/old-releases/ (either .pool or PROJECT/.pool), creating it if necessary.

    • In the target .pool directory, run checksum-directory . /path/to/old/directory, or update checksums manually if necessary (in the latter case, remember to use sign-cdimage on each checksums file).

    • Move all files starting with a lower-case letter to the corresponding subdirectory of /srv/cdimage.ubuntu.com/www/old-releases/ (either RELEASE or PROJECT/RELEASE), creating it if necessary.

    • In the target directory, run checksum-directory . /path/to/old/directory ../.pool, or update checksums manually if necessary (in the latter case, remember to use sign-cdimage on each checksums file).

    • In the target directory, update web indices. The procedure for doing this varies depends on whether the images currently being archived supersede all previous images from the previous point release (if any), or if some images from a previous point release must be kept visible (as is the case when EOLing the server part of an LTS release).

      • In the former case, run DIST=RELEASE for-project PROJECT make-web-indices . PREFIX, where PREFIX is the common prefix of the images without any trailing - (e.g. ubuntu-9.10).

      • In the latter case, edit .htaccess and HEADER.html by hand and change the version numbers for only those images that are being superseded.

    • Make sure that appropriate version-number symlinks to the release name exist in /srv/cdimage.ubuntu.com/www/old-releases/ or /srv/cdimage.ubuntu.com/www/old-releases/PROJECT/.

    • Edit /srv/cdimage.ubuntu.com/www/old-releases/.htaccess and /srv/cdimage.ubuntu.com/www/old-releases/HEADER.html (or old-releases/PROJECT/...) by hand to refer to the EOLed releases.

    • In the source .pool directory (under /srv/cdimage.ubuntu.com/www/simple/), run checksum-directory . to get rid of references to the EOLed release.

    • Remove the remaining files and symlinks corresponding to the EOLed release from under /srv/cdimage.ubuntu.com/www/simple/. Clean up emptied directories if any.

    • Edit /srv/cdimage.ubuntu.com/www/simple/.htaccess and /srv/cdimage.ubuntu.com/www/simple/HEADER.html (or simple/PROJECT/...) by hand to remove references to the EOLed release.

    • Edit /srv/cdimage.ubuntu.com/www/simple/.htaccess (not PROJECT-specific) to add appropriate RedirectPermanent directives redirecting users to the new URLs.

  • Remove any relevant files from /srv/cdimage.ubuntu.com/www/simple/jigit/.

  • Re-enable mirror syncing: chmod +x /srv/cdimage.ubuntu.com/bin/sync-mirrors.

  • Push to mirrors: sync-old-releases; sync-mirrors.

• Move any images from cdimage.ubuntu.com to old-images on antimony and notify IS team for archival

  • Disable mirror syncing: chmod -x /srv/cdimage.ubuntu.com/bin/sync-mirrors.

  • If /srv/cdimage.ubuntu.com/www/full/netboot/RELEASE/ exists, remove it (it is only an HTML page with links, and does not need to be archived), remove any symlinks to it, and remove references to it from /srv/cdimage.ubuntu.com/www/full/netboot/index.html.

  • In /srv/cdimage.ubuntu.com/www/full/, find all directories named after the EOLed release which have /releases/ in their path. Each one will have a subdirectory identifying the milestone (e.g. release, release.1, etc.). For each one:

    • Move the directory to the corresponding subdirectory of /srv/cdimage.ubuntu.com/old-images/, creating it if necessary.

    • Remove any remaining files and symlinks corresponding to the EOLed release from under /srv/cdimage.ubuntu.com/www/full/. Clean up emptied directories if any.

  • Re-enable mirror syncing: chmod +x /srv/cdimage.ubuntu.com/bin/sync-mirrors.

  • Push to mirrors: sync-mirrors.

• Remove the release from the archive (work with LOSA - send RT ticket) (crosscheck with OEM)

• Clear all packages from the partner repository for this release (work with release team) on cocoplum (crosscheck with OEM)

• Send EndOfLifeAnnouncement to ubuntu-announce, ubuntu-security-announce

• Notify the web team manager to remove release from the website.
• Close all bugs targetted to RELEASE that haven't been fixed as WONT FIX.

CategoryProcess