Setup a clear and low-effort versioning and release management workflow
dee-me-tree-or-love opened this issue · comments
What
In line with #404, I would really like to set up a clear versioning strategy and process. But am not sure which approach to go for at this point. Suggestions are very welcome!
I think that this would help a lot to make the project a bit easier to manage :).
Questions:
- can we decide which features to push immediately and when to make new major / minor / patch releases?
- what versioning strategy would work well for this project and does it actually need to change?
- how to set up a simple version & release management workflow?
DOD:
- Scripted flow for basic things
- Describe a step-by-step release process
- Improve the existing RC GitHub Actions with a step-by-step description
- Refresh the manual release documentation & tooling
- (Stretch) Automate post-RC release steps