Don't mark 4.9 as longterm ... yet
The releases plugin gets confused if there isn't at least one tree with
the "stable" moniker -- which is a bug, but the fix is non-trivial and
requires extensive testing. For now, until we fix the larger issue,
don't mark 4.9 as longterm in the configuration until 4.10 is out
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
diff --git a/pelicanconf.py b/pelicanconf.py
index cfbde60..a38ba78 100644
--- a/pelicanconf.py
+++ b/pelicanconf.py
@@ -24,7 +24,7 @@
sys.path.append('./')
from plugins import releases
-LONGTERM_KERNELS = ('4.9', '4.4', '4.1', '3.18', '3.16', '3.14', '3.12', '3.10', '3.4', '3.2')
+LONGTERM_KERNELS = ('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'
