public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Willy Tarreau is taking over the 2.6.27-longterm kernel release
Date: Sun, 12 Dec 2010 23:11:23 +0100	[thread overview]
Message-ID: <20101212221123.GA26949@1wt.eu> (raw)
In-Reply-To: <20101212190300.GB17174@kroah.com>

On Sun, Dec 12, 2010 at 11:03:00AM -0800, Greg KH wrote:
> Hi all,
> 
> Just a short announcement to let everyone know that Willy Tarreau is
> taking over the 2.6.27-longterm kernel releases, now that I am finished
> with maintaining them.
> 
> Any questions/patches/concerns about this kernel tree should go to Willy
> from this point forward, not me.

Just to clarify the process, I'm going to maintain it at a much slower pace,
comparable to 2.4, which also means that anything other than important fixes
might get ignored. I'm using 2.6.27 in places where it's not acceptable to
reboot once a month to fix a bug, and my goal is to provide users who have
similar expectations with less common updates so that they have the time to
review and test them before upgrading.

Greg has done a amazing job on 2.6.27, which has gained an excellent level
of stability. I intend to use this to convince 2.4 users that a longterm
2.6 can match their expectations and that it's time to migrate. It will
then be easier to have them migrate between longterm releases once they
enter the process.

I've not decided how long I will maintain it, but at least it will last
longer than 2.4 so that users have the time to note the stability (or
to report bugs if any).

Thanks,
Willy


      reply	other threads:[~2010-12-12 22:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12 19:03 Willy Tarreau is taking over the 2.6.27-longterm kernel release Greg KH
2010-12-12 22:11 ` Willy Tarreau [this message]

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=20101212221123.GA26949@1wt.eu \
    --to=w@1wt.eu \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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