Skip to contentSkip to conversation

4.9 is a longterm kernel

PATCH In review Greg KH 2 participants 3 messages Jan 19, 2017 Stable branch

lore
Share & tools
lore

Greg KH

author maintainer
#0 lore raw

PATCH 1/1 4.9 is a longterm kernel

From: Greg Kroah-Hartman <[email protected]>

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.

content/releases.rst +1 -0
index 3c2eb973f66b..efe10dc05a8f 100644
@@ -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
pelicanconf.py +1 -1
index a38ba7826489..cfbde607e6cf 100644
@@ -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'
#1 lore raw
Quoted 31 lines · Greg KH

From: Greg Kroah-Hartman <[email protected]>

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.

content/releases.rst +1 -0
index 3c2eb973f66b..efe10dc05a8f 100644
@@ -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
pelicanconf.py +0 -0
index a38ba7826489..cfbde607e6cf 100644
@@ -24,7 +24,7 @@ import sys
 sys.path.append('./')

from plugins import releases

pelicanconf.py +1 -1
-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')

Quoted 1 line

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

author maintainer
#2 lore raw
Quoted 41 lines · Konstantin Ryabitsev
Quoted 31 lines · Greg KH

From: Greg Kroah-Hartman <[email protected]>

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.

content/releases.rst +1 -0
index 3c2eb973f66b..efe10dc05a8f 100644
@@ -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
pelicanconf.py +0 -0
index a38ba7826489..cfbde607e6cf 100644
@@ -24,7 +24,7 @@ import sys
 sys.path.append('./')

from plugins import releases

pelicanconf.py +1 -1
-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')

Quoted 1 line

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.

Quoted 2 lines

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.

Ah, ok, I kept telling people I couldn't mark anything as "LTS" until it actually had a chance to be dropped as a "normal" stable kernel. Turns out you coded the site based on that as well :)

I'll send you a follow-on patch once 4.10 is out if you happen to forget.

thanks,

greg k-h