Looks good to me. In the beginning, there are some indentation changes that will render a similar result, I guess, but it's good to maintain the clarity of the document.

Otherwise, the changes seem right. There was an introduction of a checksum file and the stag-release file, which was actually the splitter script of the latter.

Additional Notes

Just make sure to include the following in your changes (some are already there, but I wanted to ensure everything is covered):

• For this process, Sigul setup is required.
• The respective script should be run with the correct mount and on a machine that has Sigul configured.
• For the Bodhi commands:
• Ensure your Bodhi client configuration is properly set up.
• You need the right ACLs (I think sysadmin-bodhi will do the trick).

Verification

At the end, verification is done to check for the tag. For example:

name: f42-updates
success: True

Make sure to check if there are any pending updates to the section. This might be misleading since we also do a final push. It is generally run as part of cron later, but if someone wants to avoid weekend hiccups, they should do it manually on stage release day, which often falls on Friday.

Add one more section:

Release Day (Tuesday @ 14:00 UTC)

On release day (usually Tuesday, 14:00 UTC), make sure to:

• Check that torrents are published and seeding properly.
• Unhide the directories that were hidden as part of the stage-release script — these should now be made available to the public.
• This step ensures that the content officially becomes public and everything is accessible after the release GO decision.

Only the signing one needs sigul. The other one can be run on any compose machine with /pub rw (typically compose-x86-01, but I suppose it could also be bodhi-backend01)

This should be moved to Monday, the day before release. We want to have the torrents up in advance so people can download the content to seed it to other users.
We don't typically announce this widely, just to those folks who normally seed torrents.

This should be moved to monday night (late) before the release. This is to allow mirrors that are not tier1 (and don't have access to pre-release content) to start syncing up, so that more of them are in sync by the time of the actual release announcement.
We typically don't announce this widely either. Mirrors will just start syncing it, we don't need to tell users about it.

A few minor comments, but otherwise looks good! Thanks for updating this!

There's conflicts here now. Can you rebase it?