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

Sean Whitton spwhitton at spwhitton.name
Wed Jul 15 17:24:28 BST 2020


On Wed 15 Jul 2020 at 05:19PM +02, Markus Koschany wrote:

> 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.

We're all volunteers, and generally I think this sort of thing would
make NEW processing feel like drudgery.

More specifically, not sure this could work well because the amount of
time packages take to process varies considerably, so if we only have
time for some small packages, we want to be able to get those through,
and not be stopped just because of a rule that we have to process the
oldest item in the queue.

> 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.

My experience shows that they often take *more* time, unfortunately.

Sean Whitton
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 869 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-mozext-maintainers/attachments/20200715/1872ff62/attachment.sig>

More information about the Pkg-mozext-maintainers mailing list