Launchpad Entry: https://launchpad.net/distros/ubuntu/+spec/edgy-release-schedule
Created: 2006-06-19 by ColinWatson
This document provides the rationale for the release schedule dates set and documented at EdgyReleaseSchedule.
Upstream Version Freeze
We've failed to catch up with Debian recently, and there are a large number of necessary syncs and merges; unfortunately Debian's freeze for etch is not at a useful time for us. To ensure there is sufficient time to discover bugs and actually work on features, two weeks and a half weeks have been allocated for the sync and merge from Debian.
After this date we will monitor the list of bugs closed in Debian uploads to see whether there are new versions we would like to sync or merge in on an individual basis.
The proposed date for the distro sprint places it in the second half of the feature development, the current date is chosen to avoid clashes with Colin's wedding anniversary and Matt's trip to burning man.
Feature freeze is the time at which features are ejected from a release because it is not believed that they will be stable in time; two months seemed a reasonable amount of time for shaking out the major bugs.
For edgy, artwork and user interface design is considered a feature. Major theme changes to usplash, gdm, GTK+ theme, etc. should be completed by this time, while still allowing two months for tweaking and adjustments which are effectively bug fixes.
Documentation String Freeze
This date was chosen based on the dapper schedule, it allows for documentation strings to change at and after feature freeze while providing sufficient time for translations.
We decided not to match the beta release to the GNOME release to allow for enough time for feature development and bug fixes of those. While edgy is supposed to be exciting, it has to at least be useful. There may be a release on GNOME day that isn't the formal beta.
One week after the freeze, as usual.
Major bugs in the kernel usually show up pretty quickly after the mass-testing of the beta release, so the freeze is one week afterwards, giving a couple of weeks for it to be polished.
Strings are frozen to allow for corrections after beta, but give enough time for translations before release.
One week before the release, as usual.
Last week of October, to keep to the original six-monthly schedule and restore both user and developer confidence that we can do it.