public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luis Henriques <luis.henriques@canonical.com>
To: Josh Boyer <jwboyer@fedoraproject.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	Ubuntu kernel team <kernel-team@lists.ubuntu.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Linux 3.11.y.z extended stable support
Date: Tue, 3 Dec 2013 10:42:06 +0000	[thread overview]
Message-ID: <20131203104206.GA5058@hercules> (raw)
In-Reply-To: <CA+5PVA4X+OV3L5oKL1XoPQ4=9pi_wd6MwMaSuqjyy57pAapxxw@mail.gmail.com>

Hi Josh,

On Mon, Dec 02, 2013 at 02:58:31PM -0500, Josh Boyer wrote:
> On Mon, Dec 2, 2013 at 10:43 AM, Luis Henriques
> <luis.henriques@canonical.com> wrote:
> > Since Ubuntu 13.10 "Saucy Salamander" uses the 3.11 kernel, the Ubuntu
> > kernel team will pick up stable maintenance where Greg KH left off[1]
> > with 3.11.10 (thanks a lot, Greg!).
> >
> > The Ubuntu kernel team is pleased to announce that we will be
> > providing extended stable support for the Linux 3.11 kernel until
> > August 2014 as a third party effort maintained on our infrastructure.
> >
> > Our linux-3.11.y{-queue,-review} stable branches will fork from
> > 3.11.10 and will be published here:
> >
> >     git://kernel.ubuntu.com/ubuntu/linux.git
> >
> > We will use the same stable request/review workflow and follow the
> > standard upstream stable kernel rules.  More details are available at
> > http://wiki.ubuntu.com/Kernel/Dev/ExtendedStable
> >
> > We welcome any feedback and contribution to this effort.  We will be
> > posting the first review cycle patch set in a week or two.
> 
> I might have asked this already before, but if I did I've forgotten
> the answer.  Apologies if so.
> 
> Why not do this on the kernel.org infrastructure and treat it like all
> the other kernel.org stable releases?  I'm confused why it needs to be
> "forked" when it's following the same rules.  It seems like it could
> just pick up with 3.11.11 and carry on.

I would be more than happy to maintain the 3.11 kernel using Greg's
official stable git repository (e.g., by sending him a pull request).
However, I believe this has been proposed in the past without
success.

Anyway, we're still open to change this.  Greg, please let me know if
you would like to have the 3.11 kernel maintained for some more time,
or if you rather keep it dead.

Cheers,
--
Luis

      reply	other threads:[~2013-12-03 10:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-02 15:43 [ANNOUNCE] Linux 3.11.y.z extended stable support Luis Henriques
2013-12-02 19:58 ` Josh Boyer
2013-12-03 10:42   ` Luis Henriques [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=20131203104206.GA5058@hercules \
    --to=luis.henriques@canonical.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jwboyer@fedoraproject.org \
    --cc=kernel-team@lists.ubuntu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.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