-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
b35369c
commit 382b34e
Showing
1 changed file
with
29 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
# Release Procedure | ||
|
||
## Version Numbers | ||
|
||
This software follows the [Semantic Versioning (SemVer)](https://semver.org/).<br> | ||
It always has the format `MAJOR.MINOR.PATCH`, e.g. `1.5.0`. | ||
|
||
## GitHub Release | ||
|
||
### 1. 📝 Check correctness of test.openpv.de | ||
|
||
- Navigate to test.openpv.de | ||
- Check that this is the website you want to deploy | ||
- Check that it has no bugs | ||
|
||
### 2. 🐙 Create a `GitHub Release` | ||
|
||
- Named `v0.12.1` | ||
- Possibly add a Title to the Release Notes Headline | ||
- Summarize key changes in the description | ||
- Use the `generate release notes` button provided by GitHub | ||
- Make sure that new contributors are mentioned | ||
- Choose the correct git `tag` | ||
- Choose the `main` branch | ||
- Publish release | ||
|
||
### 3. Deployment | ||
|
||
- Start the manual deployment process based on the `build` branch |