hirsute will be EOL in about 1.5 months, at which point the package servers may be shut down. Avoid this by hopping to the next LTS release 22.04 (Jammy Jellyfish).
While the release is currently in development, it seems unlikely that anything will break for us. I am doing the hirsute->jammy hop to avoid a hirsute->impish->jammy hop, but if anything does break, we can fall back to that “double hop”.
Concept ACK on moving from hirsute.
While the release is currently in development, it seems unlikely that anything will break for us. I am doing the hirsute->jammy hop to avoid a hirsute->impish->jammy hop, but if anything does break, we can fall back to that “double hop”.
One more hop does not look too difficult to be done. Maybe avoid any concerns about using a non-final release in our CI, and just do a “double hop”?
We’ll also might have to backport to 22.x, so a single commit seems preferable.
Agree.
If this is too risky to merge right now, I am happy to wait until it is considered less risky.
I’m not familiar with Ubuntu development process closely. I’m fine with using a public beta release (yes, I understand that it will happen after hirsute EOL).
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
If this is too risky to merge right now, I am happy to wait until it is considered less risky.
What is the risk here? That there are intermediate failures due to the distribution itself being in development?
crACK fafa66e424cd0c4a4ac3175e0d3b15a54626aa4b
Worst case, if anything breaks due to 22.04 still being in development, we can hop back to 21.10 before the final jammy release is available in April next year.