This is debian-mentors stuff, IMHO. Sorry, I don't have time myself to answer this now, this list probably will. --Jeroen ----- Forwarded message from James Damour <jdamour@nycap.rr.com> ----- Subject: Re: Please help sorting out which sid updates need to make sarge From: James Damour <jdamour@nycap.rr.com> Reply-To: "James Damour (Suvarov454)" <suvarov454@users.sourceforge.net> To: Jeroen van Wolffelaar <jeroen@wolffelaar.nl> Date: Sun, 15 Aug 2004 11:15:01 -0400 I apologize if you did not intend to have maintainers email you directly, but you didn't specify any other communication mechanism (except waiting for an email next week... I'm trying to be helpful and proactive). I recently adopted the orphaned package named "filler" and uploaded a new version to Sid that hasn't made it into Sarge because it FTBFS. Mind you, the old (orphaned) version **also** FTBFS, so I'm not really sure how it made it into Woody; perhaps it got grandfathered in when the Debian policy on Java was changed. Nevertheless, I wanted to let you know that there is only bugs that the Sid version closes are the "package orphaned" bug and a complaint about the documentation. I don't know if either bug is considered important for the Sarge release, and I don't know the policy on replacing one FTBFS version of a package for another. Perhaps the package should be dropped from Sarge? On Sat, 2004-08-14 at 19:29, Jeroen van Wolffelaar wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi all, > > Executive summary: If you maintain one or more packages that are > out-of-sync in sarge, please go to http://www.wolffelaar.nl/~sarge/, > read the guidelines, login, lookup your own packages, and fill in the > questions. > > Full story: > > We are currently quite close to the release of the next Debian version, > Sarge. Dozens of packages are uploaded to sid daily, and it looks like > by far not all of them are going to make it into sarge. > > Currently, there are about 1500 packages that have a different version > in sid than they have in sarge. Bugs are closed when they are fixed in > sid, bugs aren't reported very often if they are only present in sarge, > and not in sid, and sid simply still has more users than sarge. > > This situation has a high risk of letting important bugs slip into the > sarge release, and that is not good. Trying to track bugs that were > fixed in sid but not yet in sarge is very tedious, and also not all bugs > and issues are reported in the BTS. > > A better approach to this issue is to judge manually on all those > package that are out-of-sync whether the sid version contains essential > fixes that really ought to make it into Sarge. For this purpose, I > hereby call on all maintainers that have packages that are out-of-sync, > to let the release team know whether this is the case. 1500 packages is > too much for a few volonteers, since it requires intimite insight on all > the changes made in the package between the sarge and the sid version. > > Please visit http://www.wolffelaar.nl/~sarge/ , the site where this is > administred. Next week the maintainers of those packages of which it is > still unknown whether the sid version contains important fixes will be > asked by mail to provide their judgement. > > Thank you for your cooperation, > - --Jeroen > > - -- > Jeroen van Wolffelaar > jeroen@wolffelaar.nl > http://jeroen.A-Eskwadraat.nl > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.4 (GNU/Linux) > > iD8DBQFBHpsqKN6ufymYLloRAga9AJ0YVRRavXOwe2kLJB3zyZLy1P9AEQCffH2z > L+UoodIklLlEXAdEJBLh6Po= > =xetU > -----END PGP SIGNATURE----- -- James Damour (Suvarov454) <suvarov454@users.sourceforge.net> ----- End forwarded message ----- -- Jeroen van Wolffelaar Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl
Attachment:
pgpVHkcdOcLmB.pgp
Description: PGP signature