Release management process

1. Ensure submitter of pull request is on the Hydra Project's Contributor License Agreement list for Sufia. If not, ping Hydra admin 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. Modify the README to replace all instances of the past version with the new version. Commit and push to the upstream repo.
5. Bump version number in SUFIA_VERSION. Do not commit. If you look at previous release commits you'll see changes also to lib/sufia/version.rb, and sufia-models/lib/sufia/models/version.rb -- don't mess with those as the rake script will take care of them for you.
6. Modify the changelog to include changes in the version (which can usually be pulled from commit messages). Do not commit.
7. Release the gem to rubygems.org: rake all:release

• If this is your first time pushing to rubygems.org
  • Someone needs to make you an owner of the projecthydra organization
  • Your name needs to be added to some list somewhere via /script/grant_revoke_gem_authority.rb
  • You will be prompted for your rubygems.org credentials. Create an account at rubygems.org, then either do gem push; rake all:release OR set up ~/.gem/credentials according to instructions at https://rubygems.org/profile/edit before running 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).