linux-kernel - Re: Linux 2.6.32.58

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120304232210.GR20538@1wt.eu>
Date:	Mon, 5 Mar 2012 00:22:10 +0100
From:	Willy Tarreau <w@....eu>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	torvalds@...ux-foundation.org, stable@...r.kernel.org, lwn@....net
Subject: Re: Linux 2.6.32.58

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

--
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/