[Pkg-mozext-maintainers] Bug#952645: Please clarify the status of ublock-origin in NEW

Markus Koschany apo at debian.org
Wed Jul 15 16:19:26 BST 2020


Am 14.07.20 um 17:22 schrieb Sean Whitton:
>> Please clarify the status of ublock-origin and why it is still in the
>> NEW queue.
> Simply that we do not have enough active FTP team members.
> Just to note that being in binary-NEW makes no difference; it gets a
> full check as if it were a new source package.

Thanks for your reply. I'm glad that ublock-origin hasn't been simply
forgotten. However I'd like to suggest to implement a strict FIFO queue
because now it is more like FILO. This would automatically reduce
support requests like this one to a minimum because everyone would be
able to watch the progress. I also recommend to prioritize binary-new
packages because they should require less work than completely new ones
since the check for DFSG compliance has already happened once before.
The focus should really be more on conflicting package names or binaries
and I'm sure this could be automated.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-mozext-maintainers/attachments/20200715/6ec78d52/attachment.sig>

More information about the Pkg-mozext-maintainers mailing list