We're still not done with the %Debian 12 bookworm upgrade or even the %Debian 11 bullseye upgrade, but when we do, we need to start working towards the Debian 13 "trixie" release. If we follow the current cadence, we'll get a release some time around July 2025, with a freeze some time in the end of 2024. We could, therefore, cautiously start upgrading during the freeze.

This milestone tracks all work related to that upgrade, including regressions and issues that were caused by the upgrade.

See TPA-RFC-80 for the plan and schedule.

Tickets to create/do as next steps here:

• make RFC for upgrade process (team#41990 (closed), previously: team#41245 (closed))
• add support for trixie in container images (previously: base-images#15 (closed) and base-images#17 (closed))
• switch installers to trixie by default (team#42107 (closed), previously: team#41244 (closed))
• automate major upgrades (team#41485 (closed))
• trixie updates, first batch: low risk (previously: team#41251 (closed), now team#42071 (closed))
• trixie updates, second batch: moderate risk (previously: team#41252 (closed), now team#42070 (closed))
• trixie updates, third batch: high risk (previously: team#41321 (closed), team#42069)
• ganeti clusters (previously: team#41254 (closed), team#41253 (closed)) merged in above third batch
• remove support for bookworm in container images on bookworm EOL date (team#42107 (closed), base-images#24 (closed), previously: base-images#19 (closed))
• cleanup Puppet code (team#40747 (closed) team#40723 (closed))

Timeline for this milestone is set to wrap up everything by 2025-Q4, but the actual RFC suggests we will still be doing "cleanup" in 2026, so that due date is slightly optimistic.

Next upgrade is, of course, %Debian 14 forky upgrades