1 |
On Friday, January 02, 2015 03:22:31 PM Ian Stakenvicius wrote: |
2 |
> On 02/01/15 03:17 PM, Mike Pagano wrote: |
3 |
> > On Friday, January 02, 2015 03:11:22 PM Ian Stakenvicius wrote: |
4 |
> >> On 02/01/15 02:57 PM, Mike Pagano wrote: |
5 |
> >>> I understand your point. Maybe waiting a few days to auto |
6 |
> >>> stable makes sense, because less than 7 days later, a new |
7 |
> >>> version with bug/security fixes is released. |
8 |
> >>> |
9 |
> >>> Isn't our current rate of stabilization "selling" a promise of |
10 |
> >>> stability we can't stand behind? |
11 |
> >>> |
12 |
> >>> Mike |
13 |
> >> |
14 |
> >> Well to be perfectly honest, the current-stable 3.16 and 3.17 |
15 |
> >> kernels for me at least have some rather unfortunate regressions |
16 |
> >> over 3.15 and previous, so even with the stabilization we're |
17 |
> >> achieving now I don't think we're living up to our "promise of |
18 |
> >> stability" :) |
19 |
> > |
20 |
> > Exactly. It may give people a warm fuzzy feeling, but it's not |
21 |
> > like other packages. |
22 |
> |
23 |
> I agree; and also with Rich. |
24 |
> |
25 |
> It might be a good idea to avoid stabilization of versions other than |
26 |
> the LTS ones, ie let users that want anything newer than a (at this |
27 |
> time of writing) 3.14 kernel use keywords to get them, and |
28 |
> direct-to-stable gentoo-sources packages for 3.14, 3.12, 3.10 |
29 |
> (probably with a 'genkernel kernel' test run on at least one arch |
30 |
> first to make sure this doesn't break for the really lazy user). Then |
31 |
> major dev work related to gentoo-sources stabilization is just in |
32 |
> preparation for the next longterm release. |
33 |
|
34 |
> Would that workflow still be too much for the current gentoo-sources |
35 |
> maintainers? |
36 |
Hi, that's only me. :) |
37 |
|
38 |
|
39 |
FYI, I do a compile/boot test on amd64 for every kernel I put out there. |
40 |
|
41 |
OK, I don't hate this idea. |
42 |
|
43 |
To summarize. |
44 |
|
45 |
In this instance, as this moment: |
46 |
|
47 |
1. Only enter stable req bugs for 3.18 and 3.17. |
48 |
2. Once they enter LTS, then auto stable going forward. |
49 |
3. At this moment, auto stable 3.14, 3.12, 3.10 and 3.4. |
50 |
|
51 |
If this is what you're saying, this would make things much better for me and |
52 |
better for our users. |
53 |
|
54 |
Who needs to bless this? Council, Arch Teams, Rich0, God, my dog? |
55 |
|
56 |
|
57 |
Mike |
58 |
|
59 |
|
60 |
|
61 |
|
62 |
|
63 |
|
64 |
|
65 |
|
66 |
-- |
67 |
Mike Pagano |
68 |
Gentoo Developer - Kernel Project |
69 |
Team Lead - Gentoo Sources |
70 |
E-Mail : mpagano@g.o |
71 |
GnuPG FP : EEE2 601D 0763 B60F 848C 9E14 3C33 C650 B576 E4E3 |
72 |
Public Key : http://pgp.mit.edu:11371/pks/lookup?search=0xB576E4E3&op=index |