[arch-dev-public] Package signoffs page

[Tom Gundersen]

On Thu, Nov 3, 2011 at 6:17 PM, Thomas Bächler <thomas at archlinux.org> wrote:
> No idea if some of this has been implemented already, I'll just write it
> down.
>
>> Must haves:
>> * A way to cancel a signoff
>> * Signoff "blacklist" or modification- basically say "this package
>> doesn't need signoffs, just remove it from display"
>
> * A way to "disable" a signoff for a package ("this is not ready to go
> to core yet") and "enable" it when you actually want signoffs. For
> example, the "linux" package can often stay in testing for a week or two
> and doesn't need signoffs right away.
>
>> * A daily summary email saying "hey gang, here are today's pending signoffs"
>
> * "This package has been waiting for signoffs for N days" reminders
>
> also must-haves::
>
> * Display the actual number of signoffs for each built architecture
> * A way to block a package (what Eric said)
>
> maybe:
>
> * A possibility for integration into dbscripts (db-move could block
> based on signoff and blocker status)

This might be counterproductive, as sometimes unpopular packages are
moved without enough signoffs, or with some informal user signoffs
(the pcmcia stuff springs to mind). It should be possible to override
this, maybe with "db-move --force".

-t