Release process

Manual (old approach)

1. Make sure that all tests pass

2. Remove old dist files

    rm -Rf dist/*
   

3. Build source and wheel distribution

    python setup.py sdist bdist_wheel
   

4. Sign the packages

    for f in $(ls dist/*)
    do
    gpg2 --detach-sign -a $f
    done
   

5. Test if package can be uploaded to PyPi test repository

    python3 -m twine upload --sign --repository-url https://test.pypi.org/legacy/ dist/*
   

6. If upload succeeds upload to main repository

    python3 -m twine upload --sign dist/*
   

7. Create and sign release tage

    STUBS_RELEASE_VERSION=$(python setup.py --version); git tag -s $STUBS_RELEASE_VERSION -m "$STUBS_RELEASE_VERSION"
   

8. Push tags

    git push --tags
   

9. Increment package version

10. In case of minor (i.e. 2.3 to 2.4) or major (i.e. 2.4 to 3.0) change be sure to updated SPARK_BRANCH variable in .travis.yml.

With Travis (current approach)

See PyPI deployment

1. Execute steps 2, 3 and 5 from the manual process. This ensures that there are no issues and the package is uploadable.

2. Follow steps 7 to 10 from manual process.