XPost: linux.debian.devel.release
From: ben@decadent.org.uk

Hello release and LTS teams,

Starting with Debian 6.0, we've used longterm stable branches of Linux
that were maintained upstream for 5-6 years. The kernel packages in
these Debian releases have thus benefitted from upstream security
support (and other bug fixes) for their entire support lifetime.

This may not hold for Linux 6.1 (bookworm) or 6.12 (trixie).

Longterm stable branches
========================

Since the Linux 5.10 branch, the "projected EOL" for each longterm
stable branch shown at <https://www.kernel.org/category/releases.html>
has been set at December 2026, progressively reducing their lifetime to
2 years.

However, as the FAQ on that page states, "The "projected EOL" dates are
not set in stone", and the EOL for 6.1 has already been pushed back to
December 2027 (close to the end of bookworm LTS). The kernel team is
hopeful that we can work with the upstream stable maintainers to extend
the lifetimes of 6.1 and 6.12 to cover the respective Debian releases.

But there is still the possibility that we may lose upstream security
support during the bookworm LTS period, and during trixie regular
support or LTS. We would then need to do one of:

1. Maintain our own kernel branch with backported security fixes. This
is a lot of work, but could possibly be shared with Civil Infrastructure Platform (CIP) or other distribution(s).
2. Switch to a newer longterm stable branch.

This mail is just to make you aware of this possibility. We'll let you
know if we think that we are actually going to lose upstream support and
need to take one of those actions.

Real-time stable branches
=========================

Until recently, the real-time (PREEMPT_RT) kernel configuration required
a large number of patches to the mainline kernel. There are separate
stable branches that include these patches, and separate maintainers for
those branches. They have decided not to follow any extensions of the
EOL of the corresponding longterm stable branches. (I don't see any announcement of this on the mailing list, but see <https://youtu.be/P0FZhs2ghOk?t=676>.)

This means that we may have to drop security support for these kernel configurations, or entirely remove them if the patch series conflicts
with later changes to the corresponding longterm stable branch. This is
more of a risk for bookworm than trixie, because the patches needed for
6.12 are much smaller.

On behalf of the kernel team,
Ben.

--
Ben Hutchings
Man invented language to satisfy his deep need to complain.
- Lily Tomlin

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAmg434AACgkQ57/I7JWG EQl+MRAAtj0s/GShZbUMigGBI/W6luXnwiwM4XM8t3whu7aLHbUtLalIiGR7Y3Dg DP/35Yo8oLa/bwd23lFykg3bNWni6BnmtQ9Z+oCNUPrNZfKVJgceHDFuct2RW7X6 AzZYpaW0Ir2UghDoSaVU8SCY7icwcd0AI8eqcM26qgULSLQxk8X0JAL1/kfXbqrs f7CTZdqeapdmdy8/n8EHnqeA9EpocrwPpa+QIihS7xK7Ol+uqOSrpMTKrUBJvwVy ki4qEQYpgrEQecysFB99kmZLxj64WyDvQ/2fbpz3x8nhETWHAG/ewixTQzaZWHnz x74sVUykNO9tf30OWY36If/IDow+9+Lfni3hHTO26RSib6MCAhMc2WLzkdyNriOV H80eIb1IEq7SjkhX3pL5NUPA6RZePLJwo+ZuIG98wyJzfyBtxF5VMzoOczdeMP1Q Z9heLcZ2l+PURdqEl1YR6DlBIYkUuOHblyQRK7sYCUc/zOpHituVDDzViIR7ksrB py/UAq8it/eHoFHheFh1YSJalEd5XZcuTh1Zf5FCflVGYIxzClKq/cSdX7Yl24V3 xDRruezlGB05D3vYKnIf+x7eo6klqiusz1nXMPYozh3ge1kLMbH7ywhV4hFLDjLn ENX6Br5Wm/RTSPmyr0UCjjzf64cAUyV/exvXNJxCmiqD8asR+K0=
=WyZ8
-----END PGP SIGNATURE-----

--- SoupGate-Win3