How to Make a ReleaseΒΆ
A core developer should use the following steps to create a release X.Y.Z of scikit-build.
- Configure ~/.pypirc as described here.
- Make sure that all CI tests are passing.
- Update version numbers and download count:
- in setup.py and skbuild/__init__.py
- in CHANGES.rst by changing
Next Release
section header withScikit-build X.Y.Z
.- run this big table query and update the pypi download count in
README.rst
. To learn more about pypi-stats, see How to get PyPI download statistics.
- Commit the changes using title
scikit-build X.Y.Z
.
Create the source tarball and binary wheels:
git checkout master git fetch upstream git reset --hard upstream/master rm -rf dist/ python setup.py sdist bdist_wheel
Upload the packages to the testing PyPI instance:
twine upload --sign -r pypitest dist/*
Check the PyPI testing package page.
Tag the release. Requires a GPG key with signatures. For version X.Y.Z:
git tag -s -m "scikit-build X.Y.Z" X.Y.Z upstream/master
Upload the packages to the PyPI instance:
twine upload --sign dist/*
Check the PyPI package page.
Make sure the package can be installed:
mkvirtualenv skbuild-pip-install pip install scikit-build rmvirtualenv skbuild-pip-install
Add a
Next Release
section back in CHANGES.rst and merge the result.Push local changes