linux-kernel - Re: [ANNOUNCE] Linux 3.11.y.z extended stable support

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: <CA+5PVA4X+OV3L5oKL1XoPQ4=9pi_wd6MwMaSuqjyy57pAapxxw@mail.gmail.com>
Date:	Mon, 2 Dec 2013 14:58:31 -0500
From:	Josh Boyer <jwboyer@...oraproject.org>
To:	Luis Henriques <luis.henriques@...onical.com>
Cc:	"stable@...r.kernel.org" <stable@...r.kernel.org>,
	Ubuntu kernel team <kernel-team@...ts.ubuntu.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: Re: [ANNOUNCE] Linux 3.11.y.z extended stable support

On Mon, Dec 2, 2013 at 10:43 AM, Luis Henriques
<luis.henriques@...onical.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.

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