We are preparing the next revision of the current stable Debian
distribution (etch) and will frequently 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.

The overall plan is to release a new update of the stable Debian
distribution roughly two months after the last update or after the
initial release, whichever is suitable.

An ftpmaster still has to give the final approval for each package
since ftpmasters are responsible for the archive. However, we are
trying to make their work as easy as possible in hope to get the next
revision out properly and without any hassle.

The regulations for updates to the stable Debian release are quite
conservative.

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 to 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.

Packages which will most probably be rejected:

. Packages that fix non-critical bugs.

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

These packages need further investigation. One reason the package is
listed here could be that I'm not yet convinced this package should go
into stable, but don't want to reject it entirely at the moment.

Another reason could be that released and updated architectures are
not yet in sync.

debootstrap-udeb

stable

0.3.3.2

alpha amd64 arm hppa i386 ia64 mips mipsel powerpc s390 sparc

debootstrap-udeb

updates

0.3.3.2etch1

amd64 arm hppa ia64 s390

debootstrap

stable

0.3.3.2

all source

debootstrap

updates

0.3.3.2etch1

all source

debootstrap - Add support for lenny.

epiphany-browser-dev

stable

2.14.3-6

all

epiphany-browser-dev

updates

2.14.3-7

all

epiphany-browser

stable

2.14.3-6

alpha amd64 arm hppa i386 ia64 mips mipsel powerpc s390 sparc source

epiphany-browser

updates

2.14.3-5

m68k

epiphany-browser

updates

2.14.3-7

alpha amd64 arm hppa i386 ia64 mips mipsel powerpc s390 source

epiphany-browser - Add language to gconf defaults

fai-kernels

stable

1.17

source

fai-kernels

stable

1.17+b1

amd64 i386 powerpc

fai-kernels

updates

1.17+etch2

powerpc

fai-kernels

updates

1.17+etch3

amd64 i386 source

DSA 1286 linux-2.6 - Several vulnerabilities
DSA 1289 linux-2.6 - Several vulnerabilities
fai-kernels - Include arcmsr scsi-driver which is included in the etch kernels

These packages don't meet the requirements and will be rejected (if
dak supports that, otherwise we'll just carry them with us until the
end of time).

Disclaimer

This list intends to help the ftp-masters releasing 4.0r1. They have the
final power to accept a package or not. If you want to comment on
this list, please send a mail to the debian release mailing list
<debian-release@lists.debian.org>.
Last updated 2007/05/25 10:40 MET