unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: linux-libre kernel 4.4 series will end next month (Feb 2022)
Date: Mon, 3 Jan 2022 01:02:41 -0500	[thread overview]
Message-ID: <YdKRgeGL+/anPcwZ@jasmine.lan> (raw)

The Linux / linux-libre kernel "longterm" support series version 4.4 is
scheduled to reach the end of its life next month, in February 2022:

https://www.kernel.org/category/releases.html

There is a project by the Civil Infrastructure Platform (CIP) called
"SLTS" kernels, which offer "super longterm support". They begin by
pledging support for the 4.4 series until 2027:

https://wiki.linuxfoundation.org/civilinfrastructureplatform/start

So, we could use that if somebody wanted to make the necessary
adjustments to our packaging and agree to help keep it working.

I think this is the first time we face end of support of a kernel with
longterm suport in Guix, at least since we started to keep all the
longterm kernels packaged [0].

What should we do?

I'm not sure that many people are using this kernel series, but anybody
who is should speak up and give their opinion.

[0] Interesting parts of our Git history:
The first linux-libre package (3.3.8):
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=beacfcabe735b6d8d07a682f1c0663e4670cea5b

The first linux-libre update (to 3.11):
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=e7b385008ca0f0817c3514357cf53151cea0f511

First additional linux-libre variant (adding 4.0.8):
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=97121c2a2189c0880cfb4c9a7eb8efd3b6e1c16e


             reply	other threads:[~2022-01-03  6:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03  6:02 Leo Famulari [this message]
2022-02-02 16:43 ` linux-libre kernel 4.4 series will end next month (Feb 2022) Maxim Cournoyer
2022-02-03 16:18   ` Leo Famulari

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YdKRgeGL+/anPcwZ@jasmine.lan \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).