-
Notifications
You must be signed in to change notification settings - Fork 61
Open
Description
Description
The release-process.md describes the manual steps for creating a GitHub release. This release process already contains special cases to handle, and those can lead to mistakes.
We might not have the possibility to automate all the steps, but we should strive to automate as many as we can.
Motivation
Having to follow steps at release can introduce the change of mistakes. We should remove the chances of this by automating the release process.
Exemplification
https://www.sipios.com/blog-tech/tips-for-creating-stunning-software-releases-automatically contains examples for automating the release process.
Benefits
- Fewer mistakes during the release process
- Enables a more complex release process e.g., performing post-release tasks
- Possibility to remove special cases that we have in the release process today
Possible Drawbacks
None that I can think of
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Todo