Ok, thanks. So currently the testing image will continue to follow testing.
Actually, it might be preferable the other way around: To let the testing images and systems use only the codename (currently bullseye), so that what they get are only stabilizing upgrades until the official release, never early breaking transitions.
With the release they would need to get the security and backports repository added and all the sources lines be changed to “stable” instead of the specific code-name.
But maybe this could be implemented rather simply with the plinth backports package builds. (They would only come in after the release.)
It might just require one of these:
- That having a specific, not-yet-existing backports repository already activated in “testing” (e.g. for bullseye) does not break regular testing (bullseye) upgrades.
- A pre-update? hook that would test for the availability of the backports repository and enable it once it becomes available.
Then, as soon as the backports become available the first plinth package from the backports could change everything from “codename” to “stable”.