You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1.8 KiB
1.8 KiB
The following steps should be performed before releasing a new storm version. Note that in most cases a simultaneous release of carl, storm, pycarl and stormpy is preferred.
-
Update
CHANGELOG.md
:- To get all the commits from an author since the last tag execute:
git log last_tag..HEAD --author "author_name"
- Set release month
-
Update used carl version:
- Update
GIT_TAG
inresources/3rdparty/carl/CMakeLists.txt
- Maybe update
CARL_MINVERSION
inresources/3rdparty/CMakeLists.txt
- Update
-
Check that storm builds without errors and all tests are successful:
- Travis should run successfully.
- Invoke the script
doc/scripts/test_build_configurations.py
to build and check different CMake configurations.
-
Set new storm version:
- Set new storm version in
version.cmake
- Set new storm version in
-
Set new tag in Git:
git tag -a new_version git push origin new_version
Next we push the tag to GitHub. This step requires the GitHub repo to to be configured as a remote.
git remote add github https://github.com/moves-rwth/storm.git git push github new_version
The new tag should now be visible on GitHub.
-
Add new release in GitHub.
-
Update
stable
branch:git checkout stable git merge master git push origin stable
-
Update Homebrew formula.
-
Announce new storm version on website.