Release process: $TEST_IUK_SOURCE_VERSIONS wrong for Debian major version bumps
First of all, I'm a bit annoyed by the lack of concise and precise terminology for when we bump version N.x
→ (N+1).y
, which is what I mean with "major version bumps" in the title. But "major" isn't great as we already talk about "major versions" (e.g. $NEXT_PLANNED_MAJOR_VERSION
) and "major releases" (e.g. $MAJOR_RELEASE
). If any one has a suggestion how to improve this, please let me know!
Any way, while being RM for Tails 6.0 I had an issue with how rm-config
calculates $TEST_IUK_SOURCE_VERSIONS
: it became 5.22 6.0~rc1
, which is incorrect since we only provided IUKs from 6.0~rc1. As a consequence the "Wait until the IUKs are available" code snippet resulted in me waiting for 2 hours extra for the mirrors to sync before I noticed that it was looking for the non-existent 5.22_to_6.0
IUK. So in this case $TEST_IUK_SOURCE_VERSIONS
should have been only 6.0~rc1
.