Release procedure

The following is the process followed for doing a new release of MOCCASIN:

1. Update version number in moccasin/__version__.py
2. Update AUTHORS.md if appropriate
3. Update NEWS.md
4. Update README.md
5. Commit all changes to branch master. Remember to reference GitHub issues if they are fixed, and use the special keywords understood by GitHub to help close issues if appropriate.
6. Do release on GitHub
7. Test the release
8. Make a release in Caltech's Research Data Repository
9. Get Caltech DataCite DOI
10. Update README.md in 2 places where DOI is mentioned
11. Update CITATION.md to add the new DOI
12. Push the changes to the GitHub repo. (This will mean that GitHub is slightly ahead of the files included in the release. It can't be helped, and most people will probably look at the repo instead anyway.)
13. Announce on [email protected]
14. Announce on sbml-discuss and sbml-interoperability if it is a major release
15. Add a link in the news box on sbml.org
16. Copy the installers to a new directory for the release on sbml.org: /var/www/sites/sbml/Special/Software/MOCCASIN/releases/X.Y.Z. This is just an archival step.