All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Henriques <luis.henriques@canonical.com>
To: stable@vger.kernel.org
Cc: lwn@lwn.net, kernel-team@lists.ubuntu.com,
	linux-kernel@vger.kernel.org, debian-kernel@lists.debian.org
Subject: Re: [ANNOUNCE] Linux 3.16.y.z extended stable support
Date: Fri, 7 Nov 2014 10:43:28 +0000	[thread overview]
Message-ID: <20141107104328.GC8365@hercules> (raw)
In-Reply-To: <20141030181701.GD9032@hercules>

On Thu, Oct 30, 2014 at 06:17:01PM +0000, Luis Henriques wrote:
> The Ubuntu kernel team is pleased to announce that we will be
> providing extended stable support for the Linux 3.16 kernel until
> April 2016 as a third party effort maintained on our infrastructure.
> The team will pick up stable maintenance where Greg KH left off with
> v3.16.7 [1].  Thank you, Greg.
> 
> In addition to the Ubuntu 14.10 "Utopic Unicorn" release, the Debian 8
> "Jessie" release will also be based on this kernel [2].  Since the
> regular support for "Jessie" will go beyond April 2016, after this
> date Ben Hutchings (or myself) will continue the Linux 3.16 kernel
> maintenance.
> 
> Our linux-3.16.y{-queue,-review} stable branches will fork from
> v3.16.7
> 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
> here [3].
> 

In addition, I would like to announce a change in the kernel numbering
scheme that we will be using: we are adding the string '-ckt'
('Canonical Kernel Team') to the kernel version.  So, for example,
kernel '3.16.7.1' becomes '3.16.7-ckt1'.

Note that this change applies *only* to the 3.16 kernel, although in
the future we may consider doing it for other kernels we are currently
maintaining.

Cheers,
--
Luís

> We welcome any feedback and contribution to this effort.  We will be
> posting the first review cycle patch set in a week or two.
> 
> [1] https://lkml.org/lkml/2014/10/30/583
> [2] https://lists.debian.org/debian-kernel/2014/07/msg00413.html
> [3] http://wiki.ubuntu.com/Kernel/Dev/ExtendedStable
> 
> Cheers,
> -- 
> Luís Henriques
> Ubuntu Kernel Team, Canonical Ltd.
> 
> -- 
> kernel-team mailing list
> kernel-team@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/kernel-team

WARNING: multiple messages have this Message-ID (diff)
From: Luis Henriques <luis.henriques@canonical.com>
To: stable@vger.kernel.org
Cc: lwn@lwn.net, kernel-team@lists.ubuntu.com,
	linux-kernel@vger.kernel.org, debian-kernel@lists.debian.org
Subject: Re: [ANNOUNCE] Linux 3.16.y.z extended stable support
Date: Fri, 7 Nov 2014 10:43:28 +0000	[thread overview]
Message-ID: <20141107104328.GC8365@hercules> (raw)
In-Reply-To: <20141030181701.GD9032@hercules>

On Thu, Oct 30, 2014 at 06:17:01PM +0000, Luis Henriques wrote:
> The Ubuntu kernel team is pleased to announce that we will be
> providing extended stable support for the Linux 3.16 kernel until
> April 2016 as a third party effort maintained on our infrastructure.
> The team will pick up stable maintenance where Greg KH left off with
> v3.16.7 [1].  Thank you, Greg.
> 
> In addition to the Ubuntu 14.10 "Utopic Unicorn" release, the Debian 8
> "Jessie" release will also be based on this kernel [2].  Since the
> regular support for "Jessie" will go beyond April 2016, after this
> date Ben Hutchings (or myself) will continue the Linux 3.16 kernel
> maintenance.
> 
> Our linux-3.16.y{-queue,-review} stable branches will fork from
> v3.16.7
> 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
> here [3].
> 

In addition, I would like to announce a change in the kernel numbering
scheme that we will be using: we are adding the string '-ckt'
('Canonical Kernel Team') to the kernel version.  So, for example,
kernel '3.16.7.1' becomes '3.16.7-ckt1'.

Note that this change applies *only* to the 3.16 kernel, although in
the future we may consider doing it for other kernels we are currently
maintaining.

Cheers,
--
Lu�s

> We welcome any feedback and contribution to this effort.  We will be
> posting the first review cycle patch set in a week or two.
> 
> [1] https://lkml.org/lkml/2014/10/30/583
> [2] https://lists.debian.org/debian-kernel/2014/07/msg00413.html
> [3] http://wiki.ubuntu.com/Kernel/Dev/ExtendedStable
> 
> Cheers,
> -- 
> Lu�s Henriques
> Ubuntu Kernel Team, Canonical Ltd.
> 
> -- 
> kernel-team mailing list
> kernel-team@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/kernel-team

  parent reply	other threads:[~2014-11-07 10:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30 18:17 [ANNOUNCE] Linux 3.16.y.z extended stable support Luis Henriques
2014-10-30 18:17 ` Luis Henriques
2014-10-30 18:18 ` Greg KH
2014-11-07 10:43 ` Luis Henriques [this message]
2014-11-07 10:43   ` Luis Henriques
2014-11-07 16:16   ` Greg KH

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=20141107104328.GC8365@hercules \
    --to=luis.henriques@canonical.com \
    --cc=debian-kernel@lists.debian.org \
    --cc=kernel-team@lists.ubuntu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.