Improve the monthly release template to reflect more the current state
Th goal is to:
- reflect better how releases (including early RCs) are done
- be more explicit/precise for each step
A few points to discuss:
- I've set that RC1 should be done 15 working days before the official release, we can discuss that of course!
- I've set that QA should be done no later than 7 working days before the official release (I think it's a waste of time to do it too early, but you could argue that it'd be better to do it a bit later...)
- I've set that master could be merged to stable RC1 until 4 working days before the official release, after that, changes will be cherry-picked (again, let's discuss that and anyways, it should be taken as a recommendation, every release is unique)
For these 3 things, I have chosen arbitrary dates, I'm looking forward to having your feedback on that.
Other improvements:
- I've added the actual commands to run to release the packages
- I've also added tasks template to create several subsequent RCs
- I've tried to include as many links to the relevant doc pages as possible
- Throughout the template, I've tried to be as precise and to give as much information as possible so that it's even more easy and straightforward to be a release manager as it is today!
Closes #12.