Release Protocol

This document is meant to provide a default list for the process of releasing a new version of EQcorrscan.

For each release a new issue with the title:

Release x.y.z

Where x.y.z is the release number.

EQcorrscan uses semantic versioning where x is the major release number, y is the minor version number and is incremented to show major changes either to the API, or internals, z is incremented according to patches to the minor release.

The list of things to do before a release is as follows:

• Check docs;
• Make sure changes are represented in CHANGES.md;
• Bump version number;
• Merge develop into master;
• Release a release candidate on github;
• Test release candidate on conda-forge: see pr 4;

If release candidate works on conda-forge then:

• Generate full release on github;
• Get DOI of new version from zenodo and update master README.md
• Release on PyPi;
• Generate PR for eqcorrscan-feedstock from PyPi release;
• Email google-groups email list.