[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4631FEEE.4070005@redhat.com>
Date: Fri, 27 Apr 2007 09:47:26 -0400
From: Chuck Ebbert <cebbert@...hat.com>
To: Jesper Juhl <jesper.juhl@...il.com>
CC: bryan.wu@...log.com, Greg KH <gregkh@...e.de>,
linux-kernel@...r.kernel.org, stable@...nel.org,
Justin Forbes <jmforbes@...uxtx.org>,
Zwane Mwaikambo <zwane@....linux.org.uk>,
"Theodore Ts'o" <tytso@....edu>,
Randy Dunlap <rdunlap@...otime.net>,
Dave Jones <davej@...hat.com>,
Chuck Wolber <chuckw@...ntumlinux.com>,
Chris Wedgwood <reviews@...cw.f00f.org>,
Michael Krufky <mkrufky@...uxtv.org>,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
alan@...rguk.ukuu.org.uk
Subject: Re: [patch 00/33] 2.6.20-stable review
Jesper Juhl wrote:
>
> The normal way -stable works is that it tracks the latest 2.6.x kernel
> that has been released.
> Now that 2.6.21 has been released, a final flush of the patch queue
> against 2.6.20 is done, that will be 2.6.20.10, and then -stable will
> switch to 2.6.21.y, when 2.6.22 comes out a final 2.6.21.y is made and
> then it's off to track 2.6.22
>
The older stable version is usually maintained for a while after the next
major release comes out. How long that is can vary. I would personally like
to see 2.6.20 continue for a while, at least until 2.6.21.x is judged stable
enough (that could be a long time.)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists