[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Preparation of the next stable Debian GNU/Linux update

Preparation of the next stable Debian GNU/Linux update

An up-to-date version is at <http://people.debian.org/~joey/3.0r3/>.

I am sorry for not being able to send out the entire document, but
the preparation efforts list has grown so much that the large mail
is rejected at the Debian listserver due to its sheer size.

I am preparing the third revision of the current stable Debian
distribution (woody) and will infrequently send reports so people can
actually comment on it and intervene whenever this is required.

If you disagree with one bit or another, please reply to this mail and
explain why these things should be handled differently.  There is
still time to reconsider.

The plan is to release this revision at some time in the future,
hopefully before the release of sarge.  It may be the last update if
no updates to 3.0 are possible after sarge has been released.

An ftpmaster still has to give the final approval for each package
since ftpmaster are responsible for the archive.  However, I will try
to make their work as easy as possible in the hope to get the next
revision out properly and without too much hassle.

The regulations for updates to the stable Debian release are quite

The requirements for packages to get updated in stable are:

 1. The package fixes a security problem.  An advisory by our own
    Security Team is required.  Updates need to be approved by the
    Security Team.

 2. The package fixes a critical bug which can lead into data loss,
    data corruption, or an overly broken system, or the package is
    broken or not usable (anymore).

 3. The stable version of the package is not installable at all due to
    broken or unmet dependencies or broken installation scripts.

 4. All released architectures have to be in sync.

 5. The package gets all released architectures back in sync.

It is (or (and (or 1 2 3) 4) 5)

Regular bugs and upgrade problems don't get fixed in new revisions for
the stable distribution.  They should instead be documented in the
Release Notes which are maintained by Rob Bradford
<mailto:robster@debian.org> and are found at

Packages, which will most probably be rejected:

  . Packages that fix non-critical bugs.

  . Misplaced uploads, i.e. packages that were uploaded to 'stable
    unstable' or `frozen unstable' or similar.

  . Packages for which its binary packages are out of sync with regard
    to all supported architectures in the stable distribution.

  . Binary packages for which the source got lost somehow.

  . Packages that fix an unusable minor part of a package.

If you would like to get a package updated in the stable release, you
are advised to talk to the stable release manager first (see

This is probably the last update to the current stable Debian release
since updates are impossible when a new suite is labelled stable.
It's also possible that the current stable Debian release won't be
updated at all.


2004/09/03 06:54 MET

 * Accepted qt-copy
 * Updated krb5 (accept)
 * Updated python2.2 (accept)


This list intends to help the ftp-masters releasing 3.0r3.  They have the
final power to accept a package or not.  If you want to comment on
this list, please send a mail to Martin Schulze <joey@debian.org>.

Last updated 2004/09/03 06:54 MET

WARNING: Do not execute!  This call violates patent DE10108564.

wget -O patinfo-`date +"%Y%m%d"`.html http://patinfo.ffii.org/

Attachment: signature.asc
Description: Digital signature

Reply to: