From: Willy Tarreau <w@1wt.eu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net
Subject: Re: Linux 2.6.32.58
Date: Mon, 5 Mar 2012 00:22:10 +0100 [thread overview]
Message-ID: <20120304232210.GR20538@1wt.eu> (raw)
In-Reply-To: <20120304180911.GA7336@kroah.com>
On Sun, Mar 04, 2012 at 10:09:11AM -0800, Greg KH wrote:
> I'm announcing the release of the 2.6.32.58 kernel.
>
> All users of the 2.6.32 kernel series must upgrade.
>
> ************************************************************************
> Note:
> This is the last 2.6.32 kernel I will be releasing. The 2.6.32
> kernel is now in "extended-longterm" maintenance, with no set
> release schedule from now on. I STRONGLY encourage any users of
> the 2.6.32 kernel series to move to the 3.0 series at this point
> in time.
> ************************************************************************
In order to second this statement, I'm (re-)announcing that I'm going
to take over 2.6.32 maintenance at a much slower pace, similar to the
2.6.27 branch (which also continues). In short, this means that while
critical fixes might cause a quick release, non-critical ones will wait
longer before being backported.
If you need quick fixes, you need 3.0. If you can't reboot your servers
often enough to be concerned by delayed fixes, you might support sticking
to 2.6.32 for a while.
Willy
next prev parent reply other threads:[~2012-03-04 23:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 18:09 Linux 2.6.32.58 Greg KH
2012-03-04 18:09 ` Greg KH
2012-03-04 23:22 ` Willy Tarreau [this message]
2012-03-05 11:32 ` Build broken on s390 and ia64 [was: Linux 2.6.32.58] Jiri Slaby
2012-03-05 12:02 ` Heiko Carstens
2012-03-05 12:48 ` Jiri Slaby
2012-03-05 12:54 ` Willy Tarreau
2012-03-05 12:56 ` Jiri Slaby
2012-03-05 13:13 ` Heiko Carstens
2012-03-05 13:18 ` Willy Tarreau
2012-03-05 22:33 ` Willy Tarreau
2012-03-08 11:06 ` Jiri Slaby
2012-03-08 11:47 ` Willy Tarreau
2012-03-09 5:29 ` Ben Hutchings
2012-03-09 6:57 ` Willy Tarreau
2012-03-09 8:23 ` Jiri Slaby
2012-03-09 8:41 ` Willy Tarreau
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=20120304232210.GR20538@1wt.eu \
--to=w@1wt.eu \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).