Complete our release process doc wrt. non-final releases
There are various areas where there aren't very specific instructions when it comes to non-final releases. For example:
XXX: adapt / fork for release candidates. In the meantime, read all this, and skip what does not make sense for a RC.
This is kinda scary for someone who has never RM'ed a non-final release (alpha, beta, RC). We should fix that.
Ideally, someone who's already RM'ed a non-final release would test the resulting updated instructions while RM'ing a real non-final release, before a RM who never did that goes through it.
Release process: document post-release steps for RCs.
This is an initial attempt, which will tried for 4.5~rc1. I'm slightly
unsure if did the right thing with the two "thaw" instructions.
I opted to "fork" the steps for final releases, instead of adapting
them, to make things simpler. I'm sure we could make the same steps
work for both types of releases, but there would be a lot of "If you
just released a final release..." and so on, while an exhausted RM
likely would prefer more straightforward instructions.
- Feature Branch set to doc/17376-finish-rc-post-release-steps
The feature branch has instructions that I am reasonably confident in. @kibi, let's try them tomorrow! I'll make extra sure to be around when you perform them. Also, there's Thursday. :)
I'll keep the branch assigned to me until after we have followed them, and done any potential follow-ups.