What should be NEW?
For some reason, I was under the impression that uploading a new upstream release would place the package in the NEW queue. I was proved wrong because I was able to upload ELinks 0.12~20080527-1 to experimental yesterday and I am a DM who can't upload NEW packages.
To me, this did not make a whole lot of sense. NEW exists to keep the Debian archive legal and to prevent serious QA issues. Uploading a new upstream release of a package pushes a _new_ orig.tar.gz file to the archive and could contain potentially DFSG non-free material which is an issue if the package is being uploaded to main.
What is a bit ironic here is that a DM can't upload an updated package that is essentially the same except that it creates new debugging-symbols packages from the same source package. To a very large extent, these -dbg packages should neither be of questionable legality nor have serious QA issues. What I don't know is if it is necessary that these go to NEW because the FTP masters add overrides manually.
To me, this did not make a whole lot of sense. NEW exists to keep the Debian archive legal and to prevent serious QA issues. Uploading a new upstream release of a package pushes a _new_ orig.tar.gz file to the archive and could contain potentially DFSG non-free material which is an issue if the package is being uploaded to main.
What is a bit ironic here is that a DM can't upload an updated package that is essentially the same except that it creates new debugging-symbols packages from the same source package. To a very large extent, these -dbg packages should neither be of questionable legality nor have serious QA issues. What I don't know is if it is necessary that these go to NEW because the FTP masters add overrides manually.