Use setuptools_scm to simplify versioning during release

This commit is contained in:
Hugo 2019-12-27 23:13:58 +02:00
parent 364f72f827
commit ad2f9cbaa2
5 changed files with 30 additions and 47 deletions

View file

@ -1,40 +1,30 @@
# Release Checklist
* [ ] Get master to the appropriate code release state. [Travis CI](https://travis-ci.org/pylast/pylast) should be running cleanly for all merges to master.
* [ ] Remove `.dev0` suffix from the version and update version and date in the changelog:
* [ ] Get master to the appropriate code release state.
[Travis CI](https://travis-ci.org/pylast/pylast) should be running cleanly for
all merges to master.
* [ ] Tag with the version number:
```bash
git checkout master
edit CHANGELOG.md src/pylast/version.py
```
* [ ] Commit and tag with the version number:
```bash
git add CHANGELOG.md src/pylast/version.py
git commit -m "Release 3.0.0"
git tag -a 3.0.0 -m "Release 3.0.0"
git tag -a 3.2.0 -m "Release 3.2.0"
```
* [ ] Push commits and tags:
```bash
git push
* [ ] Push tag:
```bash
git push --tags
```
* [ ] Create new GitHub release: https://github.com/pylast/pylast/releases/new
* Tag: Pick existing tag "3.0.0"
* Title: "Release 3.0.0"
* [ ] Check the tagged [Travis CI build](https://travis-ci.org/pylast/pylast) has deployed to [PyPI](https://pypi.org/project/pylast/#history)
* Tag: Pick existing tag "3.2.0"
* [ ] Check installation: `pip3 uninstall -y pylast && pip3 install -U pylast`
* [ ] Check the tagged [Travis CI build](https://travis-ci.org/pylast/pylast) has
deployed to [PyPI](https://pypi.org/project/pylast/#history)
* [ ] Check installation:
* [ ] Increment version and append `.dev0`, and add Unreleased to the changelog:
```bash
git checkout master
edit CHANGELOG.md src/pylast/version.py
```
* [ ] Commit and push:
```bash
git add CHANGELOG.md src/pylast/version.py
git commit -m "Start new release cycle"
git push
pip3 uninstall -y pylast && pip3 install -U pylast
```