Skip to content

Commit c82529a

Browse files
author
George K. Thiruvathukal
committed
add docs about releasing; will script this at some point
1 parent 769b0c8 commit c82529a

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

docs/RELEASING.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
# Notes to Selves
2+
3+
- Start by updating `zversion.py`
4+
5+
- We only use major, minor, and point releases (x.y.z)
6+
7+
- To bump the release, modify `zversion.py`. At some point, we may add a "version bumping" framework, e.g. bump2version, but I don't see an immediate need for this yet.
8+
9+
- Commit the changes
10+
11+
- Tag a release in GitHub. Note that releasing on PyPI and releasing on GitHub are two different things. You can avoid having to keep track by runnign `git tag $(python setup.py --version)`. This will give the version that is associated with the Python setup.py file and use it not only to make a release but to ensure this release triggers a release on PyPI.
12+
13+
- Make sure not only to `git push` but to `git push --tags`.

0 commit comments

Comments
 (0)