-
Notifications
You must be signed in to change notification settings - Fork 110
How to release
Uwe Krien edited this page Dec 14, 2018
·
16 revisions
This is a guide on how to publish and ship a new release of the windpowerlib.
- Check
setup.py- Version correct?
- Version of depending packages: Are lower and upper limits correct? Are new versions included?
- Update version number in
__init__file - Make sure desired changes (PRs) are merged to
dev - Check docs
- Build docs locally
sphinx-build -b html path/to/doc/ output/path/ - Remove errors and warnings as far as possible
- Build docs locally
- What's new
- Set release date in "What's new"
- Make sure list of changes, bug fixes and new features is complete. Consider to scan issues attached to the milestone that were closed.
- README
- Last check on README file because it will be the first page on PyPi
- Check the rendering of the README file.
a)
pip install readme_rendererb)python setup.py check -r -sc) If errors occur fix them now and check again (b). It is NOT possible to fix them after the release.
- Merge
devtomaster - Check the rendering of the README file on the master
python setup.py check -r -s - Create a release tag on
master. - Pull master to your local repository and check if the new tag is there.
- Release via PyPI (this link may be helpful).
- The upload requires a
~/.pypircfile with your PyPI credentials. - Make sure you are in
masterbranch and the latest commit. - Use
python setup.py register sdist uploadto register and upload package to PyPI.
- The upload requires a
- Set version for next release in setup.py and
__init__file ofdev - Create "What's new" file for next version
- Celebrate! 🎆 🍾 👏