public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
	stable-review@kernel.org, linux-kernel@vger.kernel.org,
	stable-review@linux.kernel.org
Subject: Re: 2.6.27 maintenance plans after 2.6.32 is released
Date: Tue, 8 Sep 2009 16:04:16 -0700	[thread overview]
Message-ID: <20090908230416.GA8283@kroah.com> (raw)
In-Reply-To: <43e72e890909081244m4083a1bcq30cf1306ce566726@mail.gmail.com>

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@gmail.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

  reply	other threads:[~2009-09-08 23:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-08 19:30 2.6.27 maintenance plans after 2.6.32 is released Luis R. Rodriguez
2009-09-08 19:44 ` Luis R. Rodriguez
2009-09-08 23:04   ` Greg KH [this message]
2009-09-09  2:08     ` Luis R. Rodriguez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090908230416.GA8283@kroah.com \
    --to=greg@kroah.com \
    --cc=chrisw@sous-sol.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=stable-review@kernel.org \
    --cc=stable-review@linux.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox