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

potato revision one


2.2r1 is underway (ie, the ftpmasters are cleaning up the archive and
moving things around). Most of the proposed updates have been accepted.

Some concerns:

	* cross-architecture synchronisation isn't too great. sparc in
	  particular doesn't have .deb's for most of the changed packages.

	* a fair number of (somewhat minor) security updates don't seem to
	  have gone through the security team, or at least don't seem to
	  have been recompiled as most of the security updates that did
	  go through the security team.

Most of the updated packages are security fixes or RC bug fixes. A few
are regular bug fixes of one sort or another. The two notable exceptions
to this are mozilla M18 and console-apt.

I'm treating updates to stable under two principles: they should make
users notably better off; and they shouldn't ever make it harder for
users to do anything they were doing before.

So I'm willing to be fairly lenient on completely new packages
(assuming they've been thoroughly tested and are quite worthwhile, a
la console-apt) since anyone who's troubled by it can just pretend the
package doesn't exist; and also willing to accept major bugfix updates
assuming everyone's confident the new version will do *everything*
better than the old version in *all* circumstances (which is mainly
applicable to packages which were fairly broken originally, a la mozilla).

It'd probably be helpful if someone (or somebodies) interested in keeping
potato functional until woody's released would like to help out for r2.
Making sure arches are up to date, keeping track of bugs and things to
backport, and making sure updates don't break other things need more
time and care than I'm able to put into stable, unfortunately.


Anthony Towns <aj@humbug.org.au> <http://azure.humbug.org.au/~aj/>
I don't speak for anyone save myself. GPG signed mail preferred.

  ``We reject: kings, presidents, and voting.
                 We believe in: rough consensus and working code.''
                                      -- Dave Clark

Attachment: pgpjIVMrv0Pdp.pgp
Description: PGP signature

Reply to: