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.

54 lines
2.1 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. * Set release month
  9. 2. Update used carl version:
  10. * Update `GIT_TAG` in `resources/3rdparty/carl/CMakeLists.txt`
  11. * Maybe update `CARL_MINVERSION` in `resources/3rdparty/CMakeLists.txt`
  12. 3. Check that storm builds without errors and all tests are successful:
  13. * [Github Actions](https://github.com/moves-rwth/storm/actions/) should run successfully.
  14. * Invoke the script `doc/scripts/test_build_configurations.py` to build and check different CMake configurations.
  15. 4. Set new storm version:
  16. * Set new storm version in `version.cmake`
  17. 5. Set new tag in Git:
  18. ```console
  19. git tag -a new_version
  20. git push origin new_version
  21. ```
  22. Next we push the tag to GitHub. This step requires the GitHub repo to to be configured as a remote.
  23. ```console
  24. git remote add github https://github.com/moves-rwth/storm.git
  25. git push github new_version
  26. ```
  27. The new tag should now be visible on [GitHub](https://github.com/moves-rwth/storm/tags).
  28. 6. [Add new release](https://github.com/moves-rwth/storm/releases/new) in GitHub.
  29. 7. Update `stable` branch:
  30. ```console
  31. git checkout stable
  32. git rebase master
  33. git push origin stable
  34. ```
  35. Note: Rebasing might fail if `stable` is ahead of `master` (e.g. because of merge commits). In this case we can do:
  36. ```console
  37. git checkout stable
  38. git reset --hard master
  39. git push --force origin stable
  40. ```
  41. 8. Update [Homebrew formula](https://github.com/moves-rwth/homebrew-storm).
  42. 9. Announce new storm version on [website](http://www.stormchecker.org/news.html).
  43. 10. Create [Docker containers](https://hub.docker.com/r/movesrwth/storm) for new version.