2016-09-17 07:01:10 +02:00
|
|
|
# Release Process for PyLink
|
|
|
|
|
|
|
|
|
|
This document documents the steps that I (James) use to release updates to PyLink.
|
|
|
|
|
|
2017-10-06 03:20:59 +02:00
|
|
|
1) Draft the next release's changelog in `RELNOTES.md`
|
2016-09-17 07:01:10 +02:00
|
|
|
|
2017-10-06 03:20:59 +02:00
|
|
|
2) Bump the version in the [`VERSION`](VERSION) file.
|
2016-09-17 07:01:10 +02:00
|
|
|
|
2017-10-06 03:20:59 +02: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".
|
2016-09-17 07:01:10 +02:00
|
|
|
|
2017-10-06 03:20:59 +02:00
|
|
|
4) Publish the release via the GitHub release page, using the same changelog content as `RELNOTES.md`.
|
2016-09-17 07:01:10 +02:00
|
|
|
|
2017-10-06 03:20:59 +02:00
|
|
|
5) For stable releases, ~~also upload to PyPI: `python3 setup.py sdist upload`~~ PyPi uploads are handled automatically via Travis-CI.
|
