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.
2. Merge the pull request via GitHub. (Click the (?) icon for instructions.)
3. Pull that code into your locally cloned repo (and run the usual steps after the pull, e.g., source .rvmrc, bundle install, etc.)
4. Run specs via bundle exec rake (assuming they pass, continue), or verify specs are passing on the CI server.
5. Bump version number in SUFIA_VERSION
6. Modify release notes to include changes in the version (which can usually be culled from commit messages)
7. Build the gem, commit changes, tag the release, push it up to rubygems.org: rake all:release

• If you happen to get an error "rake aborted! There are files that need to be committed first," you may have stuff cluttering up AF's built-in jetty submodule. If so, do the following: cd jetty; git checkout .; git clean -df; cd ..; rake all:release
• If this is your first time pushing to rubygems.org, you will be prompted for your rubygem credentials, in which case do the following: gem push; rake all:release

1. Send a release message to hydra-tech and hydra-releases describing the changes (which you can copy from the release notes)