Re: Sprint on Seturday 12th July: Reforming ftpmaster team

[Joerg Jaspert <joerg@debian.org>]

On 17657 March 1977, Nicolas Mora wrote:

> We could split the NEW queue into two (or more?) branches: one for the 
> new packages with an ITP that need to be fully reviewed, and need 
> enough 
> time to process, another one when a package is updated because of the 
> soname change or when the package has an update, like the t64 or a 
> change I recall in one of my package [1]. It could help the 
> ftp-masters 
> to organize their upcoming work.

Won't help and only makes things more complicated. The NEW processing
tool already sorts binary-addition-only to the front.

> On the other hand, sometimes, some packages get a huge change in the 
> source code when bumping to a new version, but there is no change in 
> the 
> compiled package, so no reason to send it to NEW.

And thats why they aren't send to NEW.

> On this last statement (if it's relevant), I don't have a solution, 
> the 
> maintainer is the first and most important part of the solution, but 
> we 
> could add a 'helpdesk' without having to push a package in NEW: 
> "Please 
> ftp-masters, can you review my package?"

So it all goes around "it takes too much time in NEW, too much work" and
the way here is to add MORE work to those doing NEW? Doesn't sound like
the best idea.

> >       o The main proposed solution is to move the new package 
> >       processing
> >         work to a separate host. This would allow more people to 
> >         safely
> >         participate in reviews without needing access to the critical
> >         main archive server.
> If we can afford it thanks to the legal changes or so, it would be 
> awesome! It would also be better not to worry breaking the main 
> servers.

NEW processing can't break the server.

--
bye, Joerg