Release Process

This document is only meant for the project administrators, not users and developers.

  1. Create a release branch release/XX on GitHub.

  2. In the release branch:

    1. update the version numbers in version.py.
    2. update the conda recipe.
    3. update the documentation with any new features or details about changes.
    4. run make linkcheck on the documentation and fix any redirected/broken links.
    5. update the README and this release documentation, if necessary.
  3. Run the following command in the conda-recipe directory to build the conda package:

    conda build -c conda-forge --numpy=1.17 .
    
  4. Upload the package to anaconda.org using anaconda upload --user ets <package tarball>. You will need to have the appropriate permissions for the ets organization.

  5. Build the PyPI source distribution using python setup.py sdist build.

  6. Upload the source distribution to TestPyPI using twine upload --repository testpypi dist/*. You will need to have the twine package installed and set up your $HOME/.pypirc correctly. See details here.

  7. Test the conda package by creating a new environment on different platforms with this package installed and then running SKLL examples or tests from a SKLL working copy. If the package works, then move on to the next step. If it doesn’t, figure out why and rebuild and re-upload the package.

  8. Test the TestPyPI package by installing it as follows:

    pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple skll
    
  9. Then run some SKLL examples or tests from a SKLL working copy. If the TestPyPI package works, then move on to the next step. If it doesn’t, figure out why and rebuild and re-upload the package.

  10. Create pull requests on the skll-conda-tester and skll-pip-tester repositories to test the conda and TestPyPI packages on Linux and Windows.

  11. Draft a release on GitHub while the Linux and Windows package tester builds are running.

  12. Once both builds have passed, make a pull request with the release branch to be merged into master and request code review.

  13. Once the build for the PR passes and the reviewers approve, merge the release branch into master.

  14. Upload source and wheel packages to PyPI using python setup.py sdist upload and python setup.py bdist_wheel upload

  15. Make sure that the ReadTheDocs build for master passes.

  16. Tag the latest commit in master with the appropriate release tag and publish the release on GitHub.

  17. Send an email around at ETS announcing the release and the changes.

  18. Post release announcement on Twitter/LinkedIn.