Document release process

Question

Document release process

Opened this issue 7 years ago · 3 comments

Having this documented only in my head is suboptimal. The process is basically just "run towncrier, tag, build artifacts, upload to pypi" but there's some subtleties here.

Answer 1 · 2020-02-24T03:18:14.000Z

I'm going to do a release soon to try to address the somewhat dire dependency issues that have arisen as a result of the recent automat release; it sure would be nice to know what the steps are

Answer 2 · 2020-02-24T03:18:33.000Z

(I will absolutely just upload a screwed-up release here with no further info :))

Answer 3 · 2020-02-24T08:50:58.000Z

The process now is:

Update the changelog by running towncrier --version <next version number> (eg. 0.9.4), and branch/commit/push/PR/merge this to master.
Create/push a tag (either git signed or annotated) from master with the same name as the version to be released (eg. 0.9.4); note that I think rc versions will not work atm.
Run python setup.py sdist bdist_wheel && twine upload dist/*

I will try port over the automated-release-via-GA from Axiom but I'm not yet sure how to integrate towncrier.