NEW handling ...
Hello,
After reading the mention of it in debian-weekly-news, i read with interest :
http://kitenet.net/~joey/blog/entry/random_idea_re_new_queue-2005-03-02-21-12.html
And i am not sure to get the hang of it.
You mention that not all packages will be able to do go to this new.debian.org
archive, but that not-really-new packages are good candidates. How would one
decide, is it the maintainer doing the upload who takes the decision ? will
there be an automated check during initial queue processing (for new binary
packages for a same source package for example, or wildcarded packages for
soname changes or kernels) ?
Also, i don't understand what you get more this way, apart from added
bureaucrazy, over simply accepting not-really-new packages out-of hand, since
debian has always considered the maintainer to be a responsible person and the
ultimate decision taker for his packages in general. Is the maintainers
reputation less valable than a random set of DDs having signed the NEW thingy ?
Maybe we could imagine a automated-but-delayed NEW processing for
not-really-new packages ? The initial queue handling notice that the package
is NEW, but also that it is not really NEW at all, and sends an email to the
maintainer and to the ftp-masters, and if no action is taken after a given
time (7 days ? more flexibility depending on the urgency of the upload ? same
rules as the testing script use ?), if there is no override from the
ftp-masters, the package gets automatically processed.
Friendly,
Sven Luther
Reply to: