Contents

Before releasing, ensure that you're on the master branch.  Run all  tests and ensure that they pass. Also check the [[continuous integration server|https://travis-ci.org/projectblacklight/blacklight]] to make sure tests are passing.
    ```bash
    $ bundle exec rake
    ```

1. Update the version number in ./VERSION
    ```
    {major}.{minor}.{patch}
    ```

1. Fix GitHub issue tracker to know about the release
      * Create a milestone in GitHub for the NEXT version.
      * Move any open tickets for released version to the next version.
      * Mark the milestone as closed.

1. Write Github [release notes](https://github.com/projectblacklight/blacklight/tags) for the tag, using this template:

```code
[Commit History](https://github.com/projectblacklight/blacklight/compare/v5.x.0...v5.x.0) | [Milestone](https://github.com/projectblacklight/blacklight/issues?q=milestone:{milestone here})

(anything important about this release, themes, etc)

### New Features and improvements

(#ticketnumber and a human-readable description of the ticket, usually the ticket title. If the ticket title doesn't make sense, either edit the ticket directly, or provide an alternative title here)

##  Bug Fixes

### Upgrade Notes

(anything special that needs to be called out)
```

1. Prepare announcement
  * Include URL to GitHub closed issues for version 
  * Include URL to github commits between tags. github can show all commits between two versions with a URL of this form: [[http://github.com/projectblacklight/blacklight/compare/v2.5.0...v2.6.0]]  Replace with previous version and current release version tags. 
  * Include URL to the Github release notes

1. Release the gem 
```bash
$ rake release
```

1. Announce
  * Write emails announcing the release to Blacklight Development 

Version data entries

1 entries across 1 versions & 1 rubygems

Version	Path
blacklight-5.9.4	doc/How-to-release-a-version.md