No subject


Thu Jun 12 23:09:36 BST 2008


Final Freeze -> Release: Do final ISO testing, prepare SRUs for any
remaining RC bugs that didn't make it in before the freeze. For
Xubuntu, this will also be the time we prepare 4.4.3 and 4.6 for the
archive via syncing. Bug fixes continue, but are only for major bugs,
and only with a confirmed fix as there may not be a second chance to
correct, and each upload may require respinning test CDs depending on
what is affected.

Release -> Archive Open: Prepare SRUs for intrepid on any issues that
weren't fixed in time, or were too minor to risk disrupting the
freeze, but still meet SRU criteria.

Archive Open -> DIF : Spec out desired changes in Ubuntu, to be
brought up at UDS. Any bugs found in this phase should be forwarded to
Debian before resorting to a upload (since everything from sid will
automatically synced). SRU work in Intrepid continues as before and
for the previous new release continue for the remainder of the cycle
until that release leaves support. The focus is more on fixing and
providing patches in Debian vs Ubuntu. For any remaining merges,
patches should be sent to Debian as appropriate since smaller deltas
mean less maintenance later on. Features speced out during this time
are implemented in Ubuntu starting here straight onto feature freeze.

DIF: The automatic import of packages from Debian gets shut off; MOTUs
should finish any merges left over. At this point, Ubuntu is in
control of our archive rather then simply pulling in changes from
Debian, and any remaining pulls from Debian must be triggered by hand
(aka synced).

DIF -> Feature Freeze: . The focus begins to move towards usability
testing and improvement on the software imported from Debian. Features
such as the GNOME exit dialog are implemented as via the
specifications laid out both before, during, and after UDS.

Feature Freeze -> Beta Freeze: Translator teams and documentation
teams document and features added or removed before the Feature
freeze. Translation and docs are frozen after the beta freeze. Focus
moves to improving implemented features, resolving bugs, making the
distribution usable for non-developers, resolving critical bugs. It
also involves testing ISO images at each alpha and beta milestone, as
well as testing RC images making sure there are no show stopper bugs
that could affect users. Upgrade paths between the last release and
the current (i.e. Intrepid -> Jaunty) are fully tested, making sure
smooth upgrades are possible. The goal now is to polish the existing
software in the archive.

Beta Freeze -> Final Freeze: Continues as above, but the kernel and
documentation are frozen at this point, as are some translation
strings.



More information about the Motu-council mailing list