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.

37 lines
1.6 KiB

  1. The following steps should be performed before releasing a new storm version.
  2. Note that in most cases a simultaneous release of [carl](https://github.com/smtrat/carl), [storm](https://github.com/moves-rwth/storm), [pycarl](https://github.com/moves-rwth/pycarl/) and [stormpy](https://github.com/moves-rwth/stormpy/) is preferred.
  3. 1. Update `CHANGELOG.md`
  4. To get all the commits from an author since the last tag execute:
  5. ```console
  6. git log last_tag..HEAD --author "author_name"
  7. ```
  8. 2. Update used carl version:
  9. * Update `GIT_TAG` in `resources/3rdparty/carl/CMakeLists.txt`
  10. * Maybe update `CARL_MINVERSION` in `resources/3rdparty/CMakeLists.txt`
  11. 3. Check that storm builds without errors and all tests are successful
  12. * [Travis](https://travis-ci.org/moves-rwth/storm) should run successfully
  13. * Invoke the script test_build_configurations.py to build and check different cmake configurations
  14. 4. Set new storm version:
  15. * Set new storm version in `version.cmake`
  16. 5. Set new tag in git
  17. ```console
  18. git tag -a new_version
  19. git push origin new_version
  20. ```
  21. Next we push the tag to GitHub. This step requires the GitHub repo to to be configured as a remote.
  22. ```console
  23. git remote add github https://github.com/moves-rwth/storm.git
  24. git push github new_version
  25. ```
  26. The new tag should now be visible on [GitHub](https://github.com/moves-rwth/storm/tags)
  27. 6. [Add new release](https://github.com/moves-rwth/storm/releases/new) in GitHub
  28. 7. Update [Homebrew formula](https://github.com/moves-rwth/homebrew-storm)
  29. 8. Announce new storm version on [website](http://www.stormchecker.org/news.html)