Date: Fri, 7 Jan 2005 11:15:08 +0000
From: Christoph Hellwig <hch@infradead.org>
To: Nicolas Mailhot <Nicolas.Mailhot@laPoste.net>
Cc: linux-kernel@vger.kernel.org, debian-kernel@vger.kernel.org
Subject: Re: starting with 2.7
Message-ID: <20050107111508.GA6667@infradead.org>
Mail-Followup-To: Christoph Hellwig <hch@infradead.org>,
	Nicolas Mailhot <Nicolas.Mailhot@laPoste.net>,
	linux-kernel@vger.kernel.org, debian-kernel@vger.kernel.org
References: <1105096053.5444.11.camel@ulysse.olympe.o2t>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1105096053.5444.11.camel@ulysse.olympe.o2t>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1033
Lines: 23

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.

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