
Releasing BEASTling
===================

Clone ``lmaurits/beastling`` and switch to the ``master`` branch. Then:

- Change version to the new version number in
  - ``beastling/__init__.py``

- Commit your change of the version number:
```shell
git commit -a -m "release <VERSION>"
```

- Make sure tests are passing (not only on Travis, which can't run BEAST, but locally).

- Create a release tag:
```shell
git tag -a v<VERSION> -m "<VERSION> release"
```

- Release to PyPI (see https://github.com/di/markdown-description-example/issues/1#issuecomment-374474296):
```shell
rm dist/*
python setup.py sdist
twine upload dist/*
rm dist/*
python setup.py bdist_wheel
twine upload dist/*
```

- Push to GitHub:
```shell
git push origin
git push --tags origin
```

- Increment the version number and append `.dev0` to start the new development cycle:
  - ``beastling/__init__.py``

- Commit/push the version change:
```shell
git commit -a -m "bump version for development"
git push origin
```

Add release instructions (shamelessly nicked from clldutils).
Add release instructions (shamelessly nicked from clldutils).
