On Thu, Jan 19, 2017 at 02:48:38PM +0100, Greg KH wrote:
From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
Might as well just mark it as such now, to head off the constant
questions. Yes, 4.9 is the next longterm supported kernel version.
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
diff --git a/content/releases.rst b/content/releases.rst
index 3c2eb973f66b..efe10dc05a8f 100644
--- a/content/releases.rst
+++ b/content/releases.rst
@@ -40,6 +40,7 @@ Longterm
======== ==================== ============ ==================
Version Maintainer Released Projected EOL
======== ==================== ============ ==================
+ 4.9 Greg Kroah-Hartman 2016-12-11 Jan, 2019
4.4 Greg Kroah-Hartman 2016-01-10 Feb, 2018
4.1 Sasha Levin 2015-06-21 Sep, 2017
3.18 Sasha Levin 2014-12-07 Jan, 2017
diff --git a/pelicanconf.py b/pelicanconf.py
index a38ba7826489..cfbde607e6cf 100644
--- a/pelicanconf.py
+++ b/pelicanconf.py
@@ -24,7 +24,7 @@ import sys
sys.path.append('./')
from plugins import releases
-LONGTERM_KERNELS = ('4.4', '4.1', '3.18', '3.16', '3.14', '3.12', '3.10', '3.4', '3.2')
+LONGTERM_KERNELS = ('4.9', '4.4', '4.1', '3.18', '3.16', '3.14', '3.12', '3.10', '3.4', '3.2')
EOL_KERNELS = ('3.14', '3.19', '4.0', '4.2', '4.3', '4.5', '4.6', '4.7', '4.8')
GIT_MAINLINE = '/mnt/git-repos/repos/pub/scm/linux/kernel/git/torvalds/linux.git'
Partially applied. The releases script doesn't currently handle the
situation where there isn't at least one tree with the "stable" moniker
-- which is a bug, but the fix is non-trivial and will require testing.
So, for now, until 4.10 is released, I'm not marking 4.9 as "longterm"
on the landing page in order not to break things. I will work on
adjusting the logic so that we don't have to do this in the future.
When 4.10 is out, I'll properly mark 4.9 as longterm on the landing page
-- for now it's only indicated as such on the releases page.
-K
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html