Skip to content

Latest commit

 

History

History
55 lines (33 loc) · 1.09 KB

HOWTORELEASE.md

File metadata and controls

55 lines (33 loc) · 1.09 KB
Raw

How to release zugbruecke

  1. Merge all relevant changes into branch develop - this is where development and pre-release testing happens.

  2. In branch develop, run tests and examples and check that the documentation builds without errors.

make test

  1. In branch develop, add missing changes to CHANGES.md and commit.

  2. Push branch develop to GitHub.

  3. Wait for feedback from CI.

  4. Change to branch master.

  5. Merge branch develop into branch master (comment f"{version:s} release").

  6. Push branch master to GitHub.

  7. Tag branch master with f"v{version:s}".

git tag "v0.0.1"
  1. Push the tag to Github.
git push origin --tags
  1. Build and sign packages.
make release
  1. Upload package to pypi.
make upload

  1. Change to branch develop.

  2. In branch develop, bump the package version in src/zugbruecke/__init__.py by changing the __version__ string.

  3. In CHANGES.md, indicate that a new development cycle has started.

  4. Commit to branch develop.

  5. Push branch develop to GitHub.