PyLink/docs/technical/release-process.md

# Release Process for PyLink

This document documents the steps that I (James) use to release updates to PyLink.

1) Draft the next release's changelog in `RELNOTES.md`

2) Bump the version in the [`VERSION`](VERSION) file.

3) Commit the changes to `VERSION` and `RELNOTES.md`, and tag+sign this commit as the new release. Do not prefix version numbers with "v".

4) Publish the release via the GitHub release page, using the same changelog content as `RELNOTES.md`.

5) For stable releases, ~~also upload to PyPI: `python3 setup.py sdist upload`~~ PyPI uploads are handled automatically via Travis-CI.
Document the PyLink release process 2016-09-16 22:01:10 -07:00			`# Release Process for PyLink`

			`This document documents the steps that I (James) use to release updates to PyLink.`

docs: Refresh release-process.md [skip ci] 2017-10-05 18:20:59 -07:00			1) Draft the next release's changelog in `RELNOTES.md`
Document the PyLink release process 2016-09-16 22:01:10 -07:00
docs: Refresh release-process.md [skip ci] 2017-10-05 18:20:59 -07:00			2) Bump the version in the [`VERSION`](VERSION) file.
Document the PyLink release process 2016-09-16 22:01:10 -07:00
docs: Refresh release-process.md [skip ci] 2017-10-05 18:20:59 -07:00			3) Commit the changes to `VERSION` and `RELNOTES.md`, and tag+sign this commit as the new release. Do not prefix version numbers with "v".
Document the PyLink release process 2016-09-16 22:01:10 -07:00
docs: Refresh release-process.md [skip ci] 2017-10-05 18:20:59 -07:00			4) Publish the release via the GitHub release page, using the same changelog content as `RELNOTES.md`.
Document the PyLink release process 2016-09-16 22:01:10 -07:00
Convert protocol-modules graphic to a .svg 2017-11-12 12:07:08 -08:00			5) For stable releases, ~~also upload to PyPI: `python3 setup.py sdist upload`~~ PyPI uploads are handled automatically via Travis-CI.