Debianizzati.Org

Come apparso nella Mailing-List, è in preparazione la r5 di Woody che, come sempre, corregge bug ed errori dei pacchetti della Stable corrente.

Nel resto della News la comunicazione ufficiale

[quote]Preparation of the next stable Debian GNU/Linux update
======================================================

An up-to-date version is at .

I am preparing the next 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. It is
scheduled for any time now.

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 roughly two months after the last
update. However, it may be required that this happens before the
release of sarge or it won’t happen at all. 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 ftpmasters are responsible for the archive. However, I’m trying
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
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 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
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
).[/quote]

In allegato i cambiamenti che verranno effettuati!