| 1 |
On Wed, 21 Aug 2013 13:50:22 +0400 |
| 2 |
Sergey Popov <pinkbyte@g.o> wrote: |
| 3 |
|
| 4 |
> Easing stabilization procedure makes stable more, well, unstable. |
| 5 |
|
| 6 |
It doesn't have to be easier; it just has to be done differently, in |
| 7 |
which way we can benefit from the users whom are actively testing it. |
| 8 |
Currently we use "no bugs were filed lately" as a measure; but not all |
| 9 |
bugs get filed downstream, so that's a problematic measurement. |
| 10 |
|
| 11 |
If we bring in another measure, that is, users that state if it is |
| 12 |
stable or broken; then we have another measure that help determine |
| 13 |
whether to stabilize, because then you wouldn't have cases where 1) a |
| 14 |
package ends up being stabilized although it doesn't work for 33% of |
| 15 |
the users because the GUI wasn't tested thoroughly and also not have |
| 16 |
cases where 2) a package works for almost anyone but not for the arch |
| 17 |
tester for some blocker that nobody else experiences at all. It |
| 18 |
clarifies that the arch tester's system is broken, which we then fix. |
| 19 |
|
| 20 |
> Bringing some workarounds like this brokes consistency of keywording. |
| 21 |
|
| 22 |
It does not, when replacing the current way things are done we do not |
| 23 |
aim for it to be easier but rather for it to be different in that more |
| 24 |
users can contribute to the effort; the effort doesn't get easier, and |
| 25 |
should not result in a less consistent way of keywording. This should |
| 26 |
not be "let's ask some users" but rather "let's set up a carefully |
| 27 |
designed framework to properly deal with this". |
| 28 |
|
| 29 |
> As i said earlier, we should recruit more people -> then problem will |
| 30 |
> go away. |
| 31 |
|
| 32 |
There is no guarantee of that; years from now, we might have this |
| 33 |
discussion again. Yeah, maybe we might not; let's see what comes... |
| 34 |
|
| 35 |
-- |
| 36 |
With kind regards, |
| 37 |
|
| 38 |
Tom Wijsman (TomWij) |
| 39 |
Gentoo Developer |
| 40 |
|
| 41 |
E-mail address : TomWij@g.o |
| 42 |
GPG Public Key : 6D34E57D |
| 43 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |
Archives