On Friday, January 02, 2015 03:22:31 PM Ian Stakenvicius wrote:
> On 02/01/15 03:17 PM, Mike Pagano wrote:
> > On Friday, January 02, 2015 03:11:22 PM Ian Stakenvicius wrote:
> >> On 02/01/15 02:57 PM, Mike Pagano wrote:
> >>> I understand your point. Maybe waiting a few days to auto
> >>> stable makes sense, because less than 7 days later, a new
> >>> version with bug/security fixes is released.
> >>> 
> >>> Isn't our current rate of stabilization "selling" a promise of
> >>> stability we can't stand behind?
> >>> 
> >>> Mike
> >> 
> >> Well to be perfectly honest, the current-stable 3.16 and 3.17
> >> kernels for me at least have some rather unfortunate regressions
> >> over 3.15 and previous, so even with the stabilization we're
> >> achieving now I don't think we're living up to our "promise of
> >> stability" :)
> > 
> > Exactly.  It may give people a warm fuzzy feeling, but it's not
> > like other packages.
> 
> I agree; and also with Rich.
> 
> It might be a good idea to avoid stabilization of versions other than
> the LTS ones, ie let users that want anything newer than a (at this
> time of writing) 3.14 kernel use keywords to get them, and
> direct-to-stable gentoo-sources packages for 3.14, 3.12, 3.10
> (probably with a 'genkernel kernel' test run on at least one arch
> first to make sure this doesn't break for the really lazy user).  Then
> major dev work related to gentoo-sources stabilization is just in
> preparation for the next longterm release.

> Would that workflow still be too much for the current gentoo-sources
> maintainers?
Hi, that's only me.  :)


FYI, I do a compile/boot test on amd64 for every kernel I put out there.

OK, I don't hate this idea.

To summarize.

In this instance, as this moment:

1. Only enter stable req bugs for 3.18 and 3.17.
2. Once they enter LTS, then auto stable going forward.
3. At this moment, auto stable 3.14, 3.12, 3.10 and 3.4.

If this is what you're saying, this would make things much better for me and 
better for our users.

Who needs to bless this? Council, Arch Teams, Rich0, God, my dog?  


Mike








-- 
Mike Pagano
Gentoo Developer - Kernel Project
Team Lead - Gentoo Sources
E-Mail     : mpag...@gentoo.org
GnuPG FP   : EEE2 601D 0763 B60F 848C  9E14 3C33 C650 B576 E4E3
Public Key : http://pgp.mit.edu:11371/pks/lookup?search=0xB576E4E3&op=index


Reply via email to