Hello Joe, * Joe Wreschnig <[EMAIL PROTECTED]> [2005-03-08 11:25]: > On Mon, 2005-03-07 at 22:32 +0100, Martin Zobel-Helas wrote: > > On Monday, 07 Mar 2005, Marc Haber <[EMAIL PROTECTED]> wrote: > > > On Sat, 5 Mar 2005 18:03:50 +0100, Nico Golde <[EMAIL PROTECTED]> wrote: > > > >* Frank Küster <[EMAIL PROTECTED]> [2005-03-05 17:52]: > > > >>http://lists.debian.org/debian-devel-changes/2005/03/msg00019.html > > > > > > > >But it is very slow at the moment. > > > > > > Yes. And the people responsible refuse - as usual - to communicate. So > > > nobody knows about the reason. > > Might it be that they try to get no new packages into the archive before > > a release? It is just a guess... > > One of the goals of testing was to avoid freezing large portions of > unstable prior to a release. NEW should not stop processing before a > release. > > Now it's possible (even likely) that the people involved have better > things to do before a release than process NEW, like talk to mirrors or > test infrastructure.
Yes but I think both things are important so maybe it would be a good idea to split these jobs at the release time. > I haven't seen any evidence to this effect, though, > and if it's the case I think most people would like to know. > > This delay is bothering our users -- I have several packages waiting in > NEW, and I've either had to upload them to people.debian.org (libifp, > which has even had a new upstream release while it's been rotting > there), or gotten 2-3 people per week emailing me privately about > (libmusepack, python-flac). > > If NEW is stopped because the FTP masters are busy, other developers > should know. Why should they? It is not documentated. Regards Nico -- Nico Golde - [EMAIL PROTECTED] | GPG: 1024D/73647CFF http://www.ngolde.de | mutt-ng.berlios.de | grml.org VIM has two modes - the one in which it beeps and the one in which it doesn't -- encrypted mail preferred
pgp5Ni3qz9MJ5.pgp
Description: PGP signature
