Release Checklist

PyMC3 Release workflow

• make sure that __init__.py specifies the new version number
• track all relevant issues and PRs via a version-specific milestone
• make sure that there are no major known bugs that should not be released
• check that the CI pipelines on master are all green
• create a Release with the Tag as ´v1.2.3´ and a human-readable title like the ones on previous releases

After the last step, the GitHub Action "release-pipeline" triggers and automatically builds and publishes the new version to PyPI.

Troubleshooting

• If for some reason, the release must be "unpublished", this is possible by manually deleting it on PyPI and GitHub. HOWEVER, PyPI will not accept another release with the same version number!
• The release-pipeline has a test-install-job, which could fail if the PyPI index did not update fast enough.

Post-release steps

• Monitor the update the conda-forge/pymc3-feedstock repository for new PRs. The bots should automatically pick up the new version and open a PR to update it. Manual intervention may be required though (see the repos PR history for examples).
• Create a new "on deck" section in the RELEASE-NOTES.md
• Re-run notebooks with the new release (see https://github.com/pymc-devs/pymc-examples)
• Build documentation
• Close the release milestone and open a new "vNext" milestone