Re: starting with 2.7

[Bill Davidsen]

Christoph Hellwig wrote:
> On Fri, Jan 07, 2005 at 12:07:33PM +0100, Nicolas Mailhot wrote:
>
> > Hi all, 
> >
> > Since 2.6 is turning into a continuous release, how about just taking
> > the last 2.6 release every six months and backport security fixes to it
> > for the next half year ?
>
>
> Half a year is far too long because hardware is changing to fast for that.
> Three month sounds like a much better idea.
>
> The real problem is that this is a really time-consuming issue, so
> there need to be people actually commited to doing this kind of thing.
>
> Andres Salomon from the Debian Kernel maintaince team has been thinking
> about such a bugfix tree, but he's worried about having the time to
> actually get the work done - and we know what we're talking about as
> we're trying to keep a properly fixed 2.6.8 tree for Debian sarge.

Several of us have suggested that only security fixes and fixes for bugs 
which resulting in crashes, hangs, filesystem damage and the like be 
backported to the 2.6.N until 2.6.N+1 is released. No new drivers, 
schedulers (unless the old one breaks), just fixes. While this would 
work better with more frequent stable releases, the number of things in 
any given kernel which are actually broken is usually quite small, the 
bulk seem to be new features and "works better" patch sets.

I suspect that you are doing far more than bug fixes in your tree, which 
is admirable, but adds a LOT of work!

--
   -bill davidsen (davidsen@xxxxxxx)
"The secret to procrastination is to put things off until the
 last possible moment - but no longer"  -me
-
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/