Release checklist

1. Ensure that the commit message of any commit that changes the database starts with "Migrate:". Rebase if necessary.
2. If we have a commit with migrate, migrate the change to the devfixtures database and create new devfixtures with manage.py dumpdata auth.Group easydmp_auth dmpt eestore --format json --indent 1 --natural-foreign --natural-primary > devfixtures.json, then commit the devfixtures
3. Ensure we're on the master branch
4. Make a new commit updating the version number, in src/easydmp/__init__.py and CHANGELOG.rst. The commit message should be "Bump version to {version}".
5. Tag that commit with "v{version}" and add a brief summary of the changes as the tag message
6. Push the code to the official repo
7. Update the deployment repo(s) (currently only kubernetes) to use the new code, via the version-number, and commit as per the rules of that repo, push.
8. After the push, if any of the commits in the new release starts with "Migrate:", run the migration on the production database
9. After the migration, wait for staging to be up (check!), then activate the final push to production