1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 02/01/15 03:17 PM, Mike Pagano wrote: |
5 |
> On Friday, January 02, 2015 03:11:22 PM Ian Stakenvicius wrote: |
6 |
>> On 02/01/15 02:57 PM, Mike Pagano wrote: |
7 |
>>> I understand your point. Maybe waiting a few days to auto |
8 |
>>> stable makes sense, because less than 7 days later, a new |
9 |
>>> version with bug/security fixes is released. |
10 |
>>> |
11 |
>>> Isn't our current rate of stabilization "selling" a promise of |
12 |
>>> stability we can't stand behind? |
13 |
>>> |
14 |
>>> Mike |
15 |
>> |
16 |
>> Well to be perfectly honest, the current-stable 3.16 and 3.17 |
17 |
>> kernels for me at least have some rather unfortunate regressions |
18 |
>> over 3.15 and previous, so even with the stabilization we're |
19 |
>> achieving now I don't think we're living up to our "promise of |
20 |
>> stability" :) |
21 |
> |
22 |
> Exactly. It may give people a warm fuzzy feeling, but it's not |
23 |
> like other packages. |
24 |
> |
25 |
|
26 |
I agree; and also with Rich. |
27 |
|
28 |
It might be a good idea to avoid stabilization of versions other than |
29 |
the LTS ones, ie let users that want anything newer than a (at this |
30 |
time of writing) 3.14 kernel use keywords to get them, and |
31 |
direct-to-stable gentoo-sources packages for 3.14, 3.12, 3.10 |
32 |
(probably with a 'genkernel kernel' test run on at least one arch |
33 |
first to make sure this doesn't break for the really lazy user). Then |
34 |
major dev work related to gentoo-sources stabilization is just in |
35 |
preparation for the next longterm release. |
36 |
|
37 |
Would that workflow still be too much for the current gentoo-sources |
38 |
maintainers? |
39 |
|
40 |
|
41 |
-----BEGIN PGP SIGNATURE----- |
42 |
Version: GnuPG v2 |
43 |
|
44 |
iF4EAREIAAYFAlSm/gYACgkQ2ugaI38ACPC8KgEAp57inwfpkk7O3IewDlUOt3ga |
45 |
QL6vcX630xaismVyrCYBALUR2e+zTtvbxXMJLsJoXWxFGJCCeSvB6rV2yH85gJnW |
46 |
=pnlH |
47 |
-----END PGP SIGNATURE----- |