Skip to content

Latest commit

 

History

History
22 lines (18 loc) · 1.05 KB

HOW_TO_RELEASE.md

File metadata and controls

22 lines (18 loc) · 1.05 KB
Raw

How to release a new version

  • On devel branch:

    • git pull to make sure everything is in sync with remote origin.
    • Change the version in tim_reasoning/__init__.py to the new version, e.g., 2.0.0 (using the format MAJOR.MINOR.PATCH).
    • In CHANGELOG.md, change the first version, e.g. 2.0.0.dev0 (yyyy-mm-dd) to the to-be-released version and date.
    • Commit with message Bump version for release.
    • git push

  • On master branch:

    • git pull to make sure everything is in sync with remote origin.
    • Merge devel into master branch: git merge devel
    • git push
    • Create a tag for the new version, git tag <tag_name> and push it git push origin <tag_name>

  • On devel branch:

    • git merge master to make sure devel is always on top of master.
    • Change the version in tim_reasoning/__init__.py appending .dev0 to the future version, e.g. 2.1.0.dev0.
    • Add a new empty version on top of CHANGELOG.md, e.g. 2.1.0.dev0 (yyyy-mm-dd).
    • Commit with message Bump version for development.
    • git push