-
Notifications
You must be signed in to change notification settings - Fork 31
Development Guide
Chris Granade edited this page May 10, 2016
·
1 revision
The following steps should be followed after tagging each new release:
- Ensure that the latest release successfully deployed to PyPI.
- Create a new GitHub release.
- Confirm that the new release successfully uploaded to Zenodo, and edit metadata as necessary to correct import errors.
- Update the DOI and BibTeX citation template in README.rst and in doc/source/intro.rst. Note that this will mean that each release will have one "additional" commit beyond the tagged release. This is not ideal, but is unavoidable as we will not know the DOI for a new release before it is tagged.