MilestoneRhythm

Differences between revisions 9 and 10
⇤ ← Revision 9 as of 2006-06-21 06:59:40 →
Size: 5158
Editor: ALagny-109-1-10-42
Comment: sync blacklist published
← Revision 10 as of 2006-06-21 07:18:39 → ⇥
Size: 5157
Editor: ALagny-109-1-10-42
Comment: fix URL
Deletions are marked like this. Additions are marked like this.
Line 46: Line 46:
The [https://people.ubuntu.com/~cjwatson/sync-blacklist.txt sync blacklist] lists sources that cannot be synced from Debian for various reasons. In particular, this blacklist includes sources which have been modified in Ubuntu and whose binaries have been moved to other source packages, which is a situation that generally needs to be resolved by those responsible for those source packages in Ubuntu. This needs occasional gardening. The [http://people.ubuntu.com/~cjwatson/sync-blacklist.txt sync blacklist] lists sources that cannot be synced from Debian for various reasons. In particular, this blacklist includes sources which have been modified in Ubuntu and whose binaries have been moved to other source packages, which is a situation that generally needs to be resolved by those responsible for those source packages in Ubuntu. This needs occasional gardening.

Summary

Processes and plans for milestone release preparation.

Rationale

We tend to do a lot of things leading up to milestone releases, such as clear out pending anastacia promotions/demotions, check britney uninstallables and out-of-date output, clear out bits of queue/new, etc. This specification documents what needs to be done, how frequently, and when it should be done, in relation to the actual ISO-building and release process.

Use cases

  • New members of the archive administration and milestone release management teams need to come up to speed quickly.
  • Milestone release managers want a checklist of things to do during milestone preparation to ensure that quality is as high as possible.
  • Milestone release managers want as many tasks as possible to be automated or simple so that milestone releases can be prepared regularly and frequently.

Routine technical tasks

The following tasks need to be performed frequently by archive administrators, and should be reviewed at the start of milestone release preparation:

The following tasks need to be performed occasionally by the milestone release managers and anyone else interested in helping, and should be reviewed during milestone release preparation:

  • check britney uninstallables and out-of-date output daily (http://people.ubuntu.com/~cjwatson/testing/edgy_probs.html)

  • check that ISOs actually work as frequently as is convenient
    • check for .OVERSIZED files daily, and do something about them (may require coordination with derivative leads)

The following tests need to be performed occasionally and may be part of milestone release preparation, depending on the desired quality/cost trade-off for the milestone in question:

  • upgrade testing? (but should be automated)
  • buildability tests

Where possible and sensible, we will produce automatic reports of at least some of the above which are mailed to the ubuntu-archive and ubuntu-release teams as appropriate (and perhaps others) daily.

https://launchpad.net/products/soyuz/+spec/overrides-consistency-check requests writing a script to check for out-of-sync components, sections, and priorities between architectures, since it is slightly too easy to produce such overrides by accident during routine archive maintenance.

The [http://people.ubuntu.com/~cjwatson/sync-blacklist.txt sync blacklist] lists sources that cannot be synced from Debian for various reasons. In particular, this blacklist includes sources which have been modified in Ubuntu and whose binaries have been moved to other source packages, which is a situation that generally needs to be resolved by those responsible for those source packages in Ubuntu. This needs occasional gardening.

Milestone release processes

The following checklist should be followed by milestone release managers. (Those people should feel free to amend this if experience demonstrates that other tasks are necessary.)

  • A few days in advance of the planned milestone release date, ask the documentation team to prepare a web page about the changes since the last milestone.
  • Check that core developers have landed everything major they need to land (or talk them out of it).

  • Announce the milestone freeze on the #ubuntu-devel topic and possibly ubuntu-devel-announce. 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.

  • Set the distrorelease to FROZEN in Soyuz temporarily.
  • Stop all live filesystem and cdimage cron jobs.
  • Warn the QA team of the upcoming milestone release.
  • Test and iterate uploads as required.
  • Go over DISTRORELEASE-changes since the last milestone to make sure that all relevant major changes have been documented in the milestone's web page.
  • Prepare the release announcement (this should refer to the web page prepared by the doc team rather than going into details of changes itself).
  • Publish the milestone CD images.
  • Verify that all mirrors have images.

  • Send the release announcement (current opinion on the target for the announcement seems to be ubuntu-devel-announce for non-beta/RC/final releases, and Bcc to fridge-devel).

  • Set the distrorelease back to DEVELOPMENT.
  • Clear out any pending entries in the UNAPPROVED queue.
  • Turn live filesystems and cdimage cron jobs back on.

CategorySpec

MilestoneRhythm (last edited 2008-08-06 16:39:27 by localhost)