Ensure `qubes-release` package is pushed to stable before each new release

[andrewdavidwong]

The problem you're addressing (if any)

We often forget to update the version number when issuing a new release:

• https://forum.qubes-os.org/t/fixed-r4-2-3-fully-updated-system-still-shows-4-2-2/29024/
• https://forum.qubes-os.org/t/qubes-users-qubes-os-4-2-4-has-been-released/32354/2
• https://forum.qubes-os.org/t/qubes-os-4-2-4-has-been-released/32355/12
• https://www.reddit.com/r/Qubes/comments/1is85xz/qubes_os_424_has_been_released/mdf3lc8/

It happens often enough that some users have started to assume it's intentional and blame the announcements instead for not mentioning the "expected delay." I asked whether it's intentional, and @marmarek indicated that it was just due to a forgotten push.

The solution you'd like

Since it's easy to forget to update this, we should add some kind of automated test or CI check to catch this before issuing each new release.

Perhaps even just checking to make sure that the version number has changed at all (or isn't equal to the old one) might be enough of a test.

The value to a user and who that user might be

Users who do in-place upgrades will be able to verify that they're on the correct release.

Completion criteria checklist

No response

[marmarek]

The updated qubes-release package is in current-testing: QubesOS/updates-status#5443

[andrewdavidwong]

But shouldn't it be pushed to stable at the time of release (or earlier)?

https://forum.qubes-os.org/t/fixed-r4-2-3-fully-updated-system-still-shows-4-2-2/29024/7

[marmarek]

It is now.

[andrewdavidwong]

Thank you, but this issue was for creating some kind of test, not just for fixing it for this one release.

[andrewdavidwong]

Oh, wait, I see what you're saying. The version number was already updated; it's just that the package with the update was still in testing. So, maybe what we really want here is some way to make sure that the relevant package has been pushed to stable before releasing.

Would a low-tech solution be to give me the ability to push that type of package from testing to stable, then I can just add that step to my release checklist and do it before I publish each release announcement?

[marmarek]

The "problem" is that we have enforced "at least 5 days in testing" rule by the automatic workflow. I have a way to override it (which I just used), but I don't have a way to delegate this one...

[andrewdavidwong]

Ah, I see. Would it be possible for you to add that step to your own release checklist? (I could also try to remind you, if that would be helpful.)