Re: Planning for 13.1 and 12.12 onwards

Hi,

(Adding debian-lts and backports-team to the loop)

Thanks for planning so early!

...
> | 16 May 2026 |  12.14, 13.5 |                 |
> | 11 Jul 2026 |  13.6        |                 |
> | 12 Sep 2026 |  12.15, 13.7 | bookworm to LTS |

Bookworm will move under the responsibility of the LTS team on June 11th
2026 (See: https://www.debian.org/releases/bookworm/).  To make things
more clear and easier to remember for everybody, there was an agreement
since bullseye (IIRC), to have full support during the first three years
of every release, independently of the next release.

Would it be possible then to have the final bookworm point release at
the same time than 13.6, so on 11 Jul 2026?


And taking advantage of this email…

Dear FTP team, would you be OK to open the bookworm-security queue on
June 11th 2026?

Backports team, https://backports.debian.org/Instructions/ reads "When a
new Debian release is made, the previous stable suite becomes oldstable.
While oldstable releases may have Long Term Support, oldstable-backports
are only made available for a period of one year after a new Debian
stable release has been made. "  I know that backports are independent
of the LTS release lifecycle, but to align with {old,}stable, and to
make things more clear to users, would you accept to change the policy
to maintain -backports three years after the initial release?
Yes, there was some discussion about this for bullseye, but I cannot
find any conclusion about the outcome.

Thank you all,

 -- Santiago

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

iHUEABYIAB0WIQR+lHTq7mkJOyB6t2Un3j1FEEiG7wUCaNPzdgAKCRAn3j1FEEiG
76P3AQCgzMf8q+HYjo0x786Dje6OdhdE9OSwRhA6JwIPpBvtSgEAyP3xrZJd4shL
Qh01lUE0Rln4mKQyHYUbqchZ9VJJmwU=
=slHk
-----END PGP SIGNATURE-----