Hi!
On Sat, 19 Sep 2015, Agostino Sarubbo wrote:
> The ALLARCHES keyword is out since some time. For who does not
> remeber, the announcement is here [1]
>
> So, if an arch developer tests the package(s) on one
> architecture, he is allowed to stabilize/keyword for all.
This can lead to an interesting effect:
arch_A maintainer sees ALLARCHES keyworded bug, and tests
everything on A. Upon keywording and running repoman, she finds
that two other arches need additional deps. What to do?
The only feasible thing is to keyword for A and remove the
ALLARCHES keyword from the bug (and add a comment to that
effect).
Anything that involves more work than that will result in
maintainer mikado: whoever first touches the bug is stuck with
it. As a result, these bugs will rot much longer than is useful.
If anything, I'd say that the _maintainer_ can go ahead and
stabilize on all[0] arches after the first arch-specific
stabilization. Thus owning the decision and possible fallout.
Regards,
Tobias
[0] I am pretty sure some arches will want to opt out of this
scheme, at least for some more critical packages.
--
Sent from aboard the Culture ship
OU I Said, I've Got A Big Stick
