Differences between revisions 39 and 40
Revision 39 as of 2013-01-02 17:08:29
Size: 9626
Editor: GeoffSimmons
Comment: Spelling, add DefaultTemplate header, InterWiki.
Revision 40 as of 2016-01-10 00:44:18
Size: 9613
Editor: PaulWise
Comment: update links
Deletions are marked like this. Additions are marked like this.
Line 129: Line 129:
 * [[http://people.debian.org/~joeyh/d-i/translations.txt|Translation status]] to make final translation only uploads before releases  * [[https://d-i.debian.org/translations.txt|Translation status]] to make final translation only uploads before releases

Translation(s): none

This page describes the process of making a release of the DebianInstaller. Its primary goal is to be a memento for the release managers of the DebianInstaller and to ease the transfer of these responsibilities to new people.

Process outline

  1. The debian-installer team upload every installer components (udebs) to unstable.

  2. After a testing phase through daily netboot and weekly CDs/DVDs builds, manual coordination with the release team is done to migrate the udebs to testing.

  3. A new debian-installer package is uploaded to unstable, then built as usual by the buildd network.

  4. ftpmasters copy stuff from the sid directories (dak copy-installer).
  5. The release team “urgents” the debian-installer source package, so that the source of the d-i images gets into testing.
  6. Then, CDs and DVDs are built using debian-cd.
  7. Images are put in some semi-public space where developers can perform last-minute checks.
  8. The release is announced: mail to dda@/dd@, and website update.

Announcing the release

Gathering package changelogs: scripts/prepare-release-announce to the rescue. A full example is available in the code.

Web site checkout (replace “kibi” with the proper username):

sudo apt-get install cvs
cvs -d :pserver:anonymous@anonscm.debian.org:/cvs/webwml login
cvs -d :ext:kibi@cvs.debian.org:/cvs/webwml checkout webwml
cvs -d :ext:kibi@cvs.debian.org:/cvs/webwml checkout cron/scripts/validate

Add a .wml file in the right directory, adding a Makefile (copying over is enough). Then render with make foo.en.html, run validate on the generated html file.

Update errata.wml; cat the news and errata to send the announce. Finally update index.wml and images.data to point to the new release.

Releasing DebianInstaller components

Even if any member of the team can upload a DebianInstaller component (udebs are no different than normal packages in this regard), release managers are expected to regularly test and upload the version in the repository.

The list-unreleased script is helpful to get an overview of packages which need an upload.

The package upload process is described in doc/devel/package-upload.txt.

Planning a release

In order to coordinate with every actors needed to get a release done, a schedule (see the one done for Etch RC2 as an example) needs to be done.

From previous experience, the most important blocker has always been waiting for the targeted kernel to migrate to testing. To announce a timeline it is a good idea to know when that migration will happen. Quite a few times it has been necessary to negotiate with RMs about this, either to speed up a kernel migration or, just as important, to _delay_ one in order to make a release with the version in testing.

Here is the procedure that was followed by FJP:

  • decide it is time to start working on a new release
  • decide which kernel we want; does that need an upload of kernel udebs?
  • check for major blockers; are all arches in sync and building OK
  • check with RMs if they have major migrations planned that could screw up testing for some time
  • check and upload pending changes; note that most changes should already be in unstable and tested by this time; minor translation updates can wait a bit, but components that have a large amount of translation updates should be uploaded now as well
  • create new ${Release}Prep wiki page and start collecting changes for release announcement, ToDo, blockers, etc.

  • decide if a string freeze is needed or not (consult with ChristianPerrier); check status of translations (any that should be activated/dropped?)

  • check if GI_LANGS or needed-characters need updating
  • decide if an SVN freeze is needed (maybe only for some components or for the "installer" directory)
  • initial "heads-up" announcement to d-boot, d-release and d-cd with summary of above (BCC (!) d-ports; hopefully porters will wake up); separate mail to d-i18n to inform translators

  • run some installation tests (different methods and different arches!) to check for regressions
  • check for issues with installation of desktop task
  • start pushing versions of udebs that should be released to testing
  • follow progress of blockers and push for their resolution
  • follow what happens in unstable; maybe it will be needed to request that certain packages are temporarily blocked from migrating to testing; after all, the migration of one broken package can easily set back a carefully planned/prepared release by a week or more!

  • send periodic progress updates to relevant lists (do not just spam everybody by default); once a week is good, more often near the end
  • wash, rinse, repeat
  • when things are starting to look good (more testing!), announce timeline
  • update the translation-status file; make sure correct versions of udebs are used and to exclude components that are not actually used; if there's been no string freeze then it may be better to not update the file or to include an empty file (and thus disable warnings for incomplete translations)

  • make sure other relevant teams know a D-I release is coming up

Stable point releases

For releases before Lenny the debian-installer package needed to be uploaded with a build/sources.list.udeb.local with <codename>-proposed-updates added as an extra source.

For later releases this is automated by the USE_PROPOSED_UPDATES in the debian/rules file, which should only need to be changed for the first upload to stable for a given Debian release.

Relationships with the debian-cd team

The debian-cd team is responsible for building out the full CDs and DVDs which can be used to install Debian systems.

The build box

CDs and DVDs builds, both for the weekly builds and for releases, are currently done on pettersson.debian.org.

Release managers and debian-cd hackers can be added to the debian-cd group by opening a ticket on RT and by being co-opted.

Example of tasks

  • playing with boot methods (e.g. introducing multiarch boot system)
  • solving disk space issues
  • playing with package ordering (e.g. to get a CD1 with what is needed for a full desktop)

Status of debian-cd

The software currently running on pettersson is the SVN version of debian-cd. The package in unstable is updated periodically.

New releases

Steve ?McIntyre usually takes care of the full CDs and DVDs builds done for a release. From past experience, it mostly boils down to a sleepless night.

Even if he's normally available through a reasonably short notice, warning him 3 weeks ago sounds like a good timeframe.

Checking pending requests from the Release Team

During last stages of release preparation, asking the release team to wait a bit before unblocking udebs is quite common. Then unblock requests are tagged 'd-i' to find them easily later on, which can be done using:

bts select package:release.debian.org status:open tag:d-i

Data sources

Here is a list of data that needs to be tracked in order to make nice releases:

Many thanks to JoeyHess and Frans Pop for the material that has been assembled here.