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

Re: Is NEW processing on hold? (was: Question for candidate Towns)



On Mon, 2005-03-07 at 22:32 +0100, Martin Zobel-Helas wrote:
> Hi Marc,
> 
> On Monday, 07 Mar 2005, Marc Haber <mh+debian-devel@zugschlus.de> wrote:
> > On Sat, 5 Mar 2005 18:03:50 +0100, Nico Golde <nico@ngolde.de> wrote:
> > >* Frank Küster <frank@debian.org> [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. 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. If NEW is stopped because FTP masters or RMs think that
processing new packages prior to a release causes problems, other
developers should know. I'm not saying they're *wrong*; likely they know
better than most developers the relationship between RC bugs in testing
and new packages. But I would like to have something concrete to tell
upstream developers when they ask me why, despite my having a package
ready a month ago, their users still can't get it via APT. Right now I
just have to mumble something about sarge, busy people, and "Real Soon
Now." It frustates upstream, it frustrates our users, and it frustates
other Debian developers.
-- 
Joe Wreschnig <piman@debian.org>

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: