Re: [gentoo-dev] Re: rfc: revisiting our stabilization policy

[Steev Klimaszewski]

On Fri, 2014-01-24 at 20:29 +0100, Tom Wijsman wrote:
> On Fri, 24 Jan 2014 12:10:30 -0600
> Steev Klimaszewski <steev@g.o> wrote:
>
> > The problem isn't finding someone that has everything - we have people
> > that test on ARMv5, some that test on ARMv6, we have some that test on
> > ARMv7 - until ALL of them are tested, it doesn't get stabled on ARM.
> > So again, it just shuffles around the work, and does nothing to
> > address the actual problem which is manpower with people that have
> > the slower machines to finish their testing.  Unless you would like
> > to suggest that we maybe just say fuck anyone using a slow machine?
>
> Consider how packages would rarely get stabilized if we had to wait for
> all arches to test them first before adding any stable keyword at all.
>

Theoretical, again, as always, and not even worth considering because it
doesn't reflect reality.

> Organize first, then get more manpower; otherwise we say the F-word to
> everyone with a faster machine. Joining arm with a slower configuration
> and have everyone waiting on you is a working condition to avoid; so,
> we could have the slower configuration stabilize at its own pace.
>
> Would we say F-word to 'em? No, we give them better working conditions.
>

We're all adults here, you can say fuck.  And the entire point of the
emails were that the slow arches were bringing us down, and we need to
zomg stable fastar fastar fastar.  


For the record, the ARM team does just fine in stabling things in a
reasonable amount of time, so no, we aren't going to change our working
methods.  The point of this email thread was we all need to stable
faster, and slower arches need to just become unstable only, and fuck
them.  And I'm saying everyone needs to step back because stabling
things faster and faster doesn't allow for proper testing.

As QA, you should be focusing on making stable, actually stable, not
more bleeding edge.