| 1 |
On Tue, 14 Jan 2014 19:50:30 -0500 |
| 2 |
Michael Orlitzky <mjo@g.o> wrote: |
| 3 |
|
| 4 |
> On 01/14/2014 07:13 PM, Tom Wijsman wrote: |
| 5 |
> >> |
| 6 |
> >> For users, both options are worse than the status quo. |
| 7 |
> > |
| 8 |
> > When you do nothing then things are bound to get worse, under the |
| 9 |
> > assumption that manpower doesn't change as well as the assumption |
| 10 |
> > that the queue fills faster than stabilization bugs get added to it. |
| 11 |
> > |
| 12 |
> > As a result of this, stable will eventually become broken. It is up |
| 13 |
> > to you as well as us whether to consider it to be broken right now. |
| 14 |
> > Will it be in a month from now? What about in a year? |
| 15 |
> > |
| 16 |
> > Will we wait for hell? Or try to prepare and/or fix it now? |
| 17 |
> > |
| 18 |
> > Maybe there are other options if these can be deemed as being worse. |
| 19 |
> > |
| 20 |
> |
| 21 |
> As I mentioned in a reply to William, right now I can decide when |
| 22 |
> stuff is broken and keyword the newer versions. |
| 23 |
|
| 24 |
As in the mail I send seconds ago, I could complete this sentence with |
| 25 |
"... because I know stabilaziton has lagged / worsened"; but how does |
| 26 |
the user know of that? |
| 27 |
|
| 28 |
If we keep things the same we might consider to bring out a news item |
| 29 |
to at least make them aware of this, that news item might even be useful |
| 30 |
to attract new arch testers at the same time. |
| 31 |
|
| 32 |
> The proposal is to force me onto the new versions, which is strictly |
| 33 |
> worse from my perspective. |
| 34 |
> |
| 35 |
> The whole issue of how much it sucks that stable is lagging is |
| 36 |
> orthogonal. |
| 37 |
|
| 38 |
That's one of the proposals, there are others; and staying where we are |
| 39 |
is one of them, but we need to account for that (eg. recruit more, |
| 40 |
perhaps a news item, ...) to keep that option a good choice. |
| 41 |
|
| 42 |
Having stabilization eventually die due to the extra lag that collected |
| 43 |
over time is just another way of forcing you onto the new versions, |
| 44 |
which makes it less worse than you think it is; it might take a bit |
| 45 |
longer and yield a slow and painful death. |
| 46 |
|
| 47 |
-- |
| 48 |
With kind regards, |
| 49 |
|
| 50 |
Tom Wijsman (TomWij) |
| 51 |
Gentoo Developer |
| 52 |
|
| 53 |
E-mail address : TomWij@g.o |
| 54 |
GPG Public Key : 6D34E57D |
| 55 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |
Archives