1A Ginkgo release is a tagged git sha and a GitHub release.  To cut a release:
 2
 31. Ensure CHANGELOG.md is up to date.
 4  - Use `git log --pretty=format:'- %s [%h]' HEAD...vX.X.X` to list all the commits since the last release
 5  - Categorize the changes into
 6    - Breaking Changes (requires a major version)
 7    - New Features (minor version)
 8    - Fixes (fix version)
 9    - Maintenance (which in general should not be mentioned in `CHANGELOG.md` as they have no user impact)
101. Update `VERSION` in `config/config.go`
111. Create a commit with the version number as the commit message (e.g. `v1.3.0`)
121. Tag the commit with the version number as the tag name (e.g. `v1.3.0`)
131. Push the commit and tag to GitHub
141. Create a new [GitHub release](https://help.github.com/articles/creating-releases/) with the version number as the tag  (e.g. `v1.3.0`).  List the key changes in the release notes.