Release management process

1. Ensure submitter of pull request is on the Hydra Project's Contributor License Agreement list for Sufia. If not, ping Richard Green and request that this be done. (We must be sure that all code contributed to Hydra components is written by CLA signatories.)
2. Merge the pull request via GitHub. (Click the (?) icon for instructions.)
3. Verify that all specs are passing on the CI server.
4. Bump version number in SUFIA_VERSION.
5. Modify the changelog to include changes in the version (which can usually be pulled from commit messages).
6. Commit and push your local changes (which are only textual, so another round of spec-checking should not be necessary -- if you include "[ci skip]" in your commit message, tests will not run in the CI environment).
7. Release the gem to rubygems.org: rake all:release

• If this is your first time pushing to rubygems.org, you will be prompted for your rubygems.org credentials, in which case do the following: gem push; rake all:release

1. Create release notes in GitHub. In the new release, include at least a block with upgrade notes and a block showing the changelog (copy from earlier step). (See an example.)
2. Send a release message to hydra-tech, hydra-community, and hydra-releases describing the changes (which you can copy from the GitHub release).