| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20090908230416.GA8283@kroah.com> Date: Tue, 8 Sep 2009 16:04:16 -0700 From: Greg KH <greg@...ah.com> To: "Luis R. Rodriguez" <mcgrof@...il.com> Cc: Chris Wright <chrisw@...s-sol.org>, stable-review@...nel.org, linux-kernel@...r.kernel.org, stable-review@...ux.kernel.org Subject: Re: 2.6.27 maintenance plans after 2.6.32 is released On Tue, Sep 08, 2009 at 12:44:23PM -0700, Luis R. Rodriguez wrote: > On Tue, Sep 8, 2009 at 12:30 PM, Luis R. Rodriguez<mcgrof@...il.com> wrote: > > I was curious if 2.6.27 is planned to be supported after 2.6.32 is > > released, or will that be dropped in favor for 2.6.28 as the last > > supported kernel. How does dropping an old kernel for stable > > maintenance consideration typically work? .27 is a "long term" support kernel that I've decided to keep going for a variety of reasons. .28 and .29 are currently no longer maintained. So .27 is "special" right now, and seems to be working well. I keep revaluating if it's worth keeping going, and so far, it seems like it is, if for nothing else, personal reasons as I have a few servers based on it :) For .30, we will probably do a few more releases once .31 is out, and then drop it as well. I'm confused as to what .32 has to do with any of this, that's months away... thanks, greg k-h -- 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