GitHub/PyLink
3
0
Fork 0
mirror of https://github.com/jlu5/PyLink.git synced 2024-11-01 01:09:22 +01:00
Code Issues Projects Releases Wiki Activity

docs: Refresh release-process.md

Browse Source 
[skip ci]
This commit is contained in:
James Lu 2017-10-05 18:20:59 -07:00
parent f0d1c1bb89
commit 82a6ceb99e
1 changed files with 5 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/technical/release-process.md
View File

@ -2,16 +2,12 @@
This document documents the steps that I (James) use to release updates to PyLink.
1) Draft the next release & changelog at https://github.com/GLolol/PyLink/releases
1) Draft the next release's changelog in `RELNOTES.md`
2) Copy/export the changelog draft to [RELNOTES.md](../../RELNOTES.md), using a new section.
2) Bump the version in the [`VERSION`](VERSION) file.
- [`export_github_relnotes.py`](https://github.com/GLolol/codescraps/blob/master/utils/export_github_relnotes.py) allows automating this process, using the GitHub API and an optional login to read unpublished drafts.
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".
3) Bump the version in the [`VERSION`](VERSION) file.
4) Publish the release via the GitHub release page, using the same changelog content as `RELNOTES.md`.
4) Commit the changes to `VERSION` and `RELNOTES.md`, and tag+sign this commit as the new release. Do not prefix version numbers with "v".
5) Publish the release via the GitHub release page.
6) For stable releases, also upload to PyPI: `python3 setup.py sdist upload`
5) For stable releases, ~~also upload to PyPI: `python3 setup.py sdist upload`~~ PyPi uploads are handled automatically via Travis-CI.