Re: Linux 2.6.28-rc8

[Willy Tarreau]

On Wed, Dec 10, 2008 at 05:04:39PM -0800, Linus Torvalds wrote:
> 
> Nothing overly exciting here. Lots of small things, mostly in drivers 
> (with some defconfig updates for m68k and mips making the diffs bigger). 
> 
> There's some uncomfortably big changes to the intel DRI code, but most of 
> that is all about fixes to the new i916 "GEM" code that is only used by 
> development X servers, and is a new feature, so it shouldn't be able to 
> cause regressions.
> 
> Perhaps more interesting is simply the release scheduling issue. I'm 
> getting slowly ready to do a real 2.6.28, but I don't think anybody really 
> wants the merge window to be around the holidays. So the question is 
> really whether to 
> 
>  (a) just make the -rc's go on a few more weeks, and do 2.6.28 after xmas
> 
>      I like this, because alledgely people are debugging things, and we'd 
>      get a more stable 2.6.28.
> 
> or
> 
>  (b) release in a week or two, but just allow for possibly extending the 
>      merge window due to people being drunk on eggnog..
> 
>      I like this because let's face it, we get more and better bug 
>      information after releases, and everything _should_ be ready for 
>      merging *before* the merge window anyway.
> 
> or
> 
>  (c) some other crazy scheme that somebody comes up with in a drug-induced 
>      stupor.
> 
> So I haven't quite decided on that thing yet, but I'm open to suggestions. 

I'd suggest :
   (c) release before holidays, and not extend merge window. That way,
       users can test it during holidays, and we possibly merge less
       things this time, leading to less changes and more focus on fixes
       in 2.6.29, which I admit may imply more crap in 2.6.30. But that
       could give a high quality 2.6.29 by spring.

Just my 2 cents,
Willy

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/