-
Notifications
You must be signed in to change notification settings - Fork 3
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
Showing
3 changed files
with
84 additions
and
38 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
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
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,44 @@ | ||
The following steps should be performed before releasing a new carl-storm version. | ||
|
||
1. Update `CHANGELOG.md`: | ||
* To get all the commits from an author since the last tag execute: | ||
```console | ||
git log last_tag..HEAD --author "author_name" | ||
``` | ||
* Set release month | ||
|
||
2. Check that carl builds without errors and all tests are successful: | ||
* [Github Actions](https://github.com/moves-rwth/carl-storm/actions/) should run successfully. | ||
|
||
3. Set new carl version: | ||
* Set new version in `CMakeLists.txt` | ||
|
||
4. Set new tag in Git (assuming that the new version is X.Y.Z and that the remote "origin" is the github repo). | ||
Use the flag `-s` to sign the tag. | ||
```console | ||
git tag -a X.Y.Z -m "Storm version X.Y.Z" | ||
git push origin X.Y.Z | ||
``` | ||
The new tag should now be visible on [GitHub](https://github.com/moves-rwth/carl-storm/tags). | ||
|
||
5. Use the [CI](https://github.com/moves-rwth/carl-storm/actions/workflows/release_docker.yml) on the tag, provide the version `X.Y.Z` as tag and automatically create the [Docker containers](https://hub.docker.com/r/movesrwth/carl-storm) for the new version. | ||
|
||
6. [Add new release](https://github.com/moves-rwth/carl-storm/releases/new) in GitHub. | ||
|
||
7. Update `stable` branch: | ||
|
||
```console | ||
git checkout stable | ||
git rebase master | ||
git push origin stable | ||
``` | ||
Note: Rebasing might fail if `stable` is ahead of `master` (e.g. because of merge commits). In this case we can do: | ||
```console | ||
git checkout stable | ||
git reset --hard master | ||
git push --force origin stable | ||
``` | ||
|
||
8. Use the [CI](https://github.com/moves-rwth/carl-storm/actions/workflows/release_docker.yml) on the `stable` branch, provide the tag 'stable' and automatically create the [Docker containers](https://hub.docker.com/r/movesrwth/carl-storm). | ||
|
||
9. Update [Homebrew formula](https://github.com/moves-rwth/homebrew-misc). |