-
Notifications
You must be signed in to change notification settings - Fork 124
HowToRelease
-
Checkout
master
:git checkout master && git pull
-
Evaluate a new version by incrementing a major, minor or micro number. Typically increment micro only if there are bug fixes. New features need to increment at least minor version.
-
Create a branch:
git checkout -b v1.1.0
-
Edit these files:
-
rtree/__init__.py
with new version -
CHANGES.rst
with guidance from https://github.com/Toblerity/rtree/compare/1.1.0...master - Optional: CREDITS.txt or pyproject.toml
-
-
Commit with message "Release 1.1.0" and
git push <your-branch> v1.1.0
-
Create a pull request with an optional message
-
Ensure all tests pass. Check the rendered docs from readthedocs.org and make sure the release notes look OK. If all is goo, click "Squash and merge"
-
Draft a new release with title "1.1.0", creating a new tag "1.1.0", with content copied from rendered changes, click "Publish release"
-
Check that the publish step has succeeded. If not, then manually download and extract all artefacts and
twine upload *