-
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.
Merge pull request #18 from medizininformatik-initiative/release-v0.1.0
Release v0.1.0
- Loading branch information
Showing
3 changed files
with
20 additions
and
1 deletion.
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,5 @@ | ||
# Changelog | ||
|
||
## v0.1.0 | ||
|
||
Initial Version |
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,14 @@ | ||
# Development | ||
|
||
## Release Checklist | ||
|
||
* create a release branch called `release-v<version>` like `release-v0.1.1` | ||
* rename every occurrence of the old version, say `0.1.0` into the new version, say `0.1.1` | ||
* rename every occurrence of old Docker images like `ghcr.io/medizininformatik-initiative/flare:0.1` into the new image, say `ghcr.io/medizininformatik-initiative/flare:0.2` | ||
* update the CHANGELOG based on the milestone | ||
* create a commit with the title `Release v<version>` | ||
* create a PR from the release branch into main | ||
* merge that PR | ||
* create and push a tag called `v<version>` like `v0.1.1` on main at the merge commit | ||
* merge the release branch back into develop | ||
* create release notes on GitHub |
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