What does it help to have it sitting there instead of rejected?
I gave it more thought, and I don't think it has to be sitting in the NEW queue at all. As far as I understand it, the main advantage to gain is additional context; a bug report provides documentation and a place to discuss solutions for packaging issues, especially if the NEW package is maintained by a team. None of this requires the packages to keep waiting in NEW, it just requires the BTS to learn about them, so the bug reports can be assigned properly.
There are probably edge cases to consider (such as invalid package names or hijacking uploads) where it is not possible to assign the bugs. I still like the idea to expand the BTS scope to include pre-archive packaging bugs, provided that the assumption that most rejected package uploads will be fixed and accepted eventually, holds. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭────────────────────────────────────────────────────╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄⠀⠀⠀⠀ ╰────────────────────────────────────────────────────╯
signature.asc
Description: PGP signature
