Re: Bug#870056: nmu: robustirc-bridge_1.7-1
On 07/01/18 11:26, Julien Cristau wrote:
> On Sat, Jan 6, 2018 at 19:19:13 +0100, Michael Stapelberg wrote:
>> On Sat, Jan 6, 2018 at 6:30 PM, Julien Cristau <email@example.com> wrote:
>>> also implications on visibility of unreleased security updates, so the
>>> set of people with access needs to stay limited.
>> Just to confirm: is this a side-effect of getting the permission? Being
>> able to schedule binNMUs doesn’t sound related to security updates to me :)
> Yes. Side effect of getting more than guest/read-only access to
I wonder if we shouldn't automate this. I.e. automatically schedule the binNMUs
for ocaml/haskell/go, with a way to (temporarily) disable them, e.g. if there
are clashing planned transitions. That way we avoid adding more people to
wanna-build, and it's also less work for the people involved as they don't have
to routinely log in to schedule the necessary binNMUs.
This was brought recently by the haskell people, fwiw.