rollouts/vendor/github.com/onsi/ginkgo/RELEASING.md

A Ginkgo release is a tagged git sha and a GitHub release. To cut a release:

1. Ensure CHANGELOG.md is up to date.

• Use git log --pretty=format:'- %s [%h]' HEAD...vX.X.X to list all the commits since the last release
• Categorize the changes into
  • Breaking Changes (requires a major version)
  • New Features (minor version)
  • Fixes (fix version)
  • Maintenance (which in general should not be mentioned in CHANGELOG.md as they have no user impact)

1. Update VERSION in config/config.go <<<<<<< HEAD
2. Commit, push, and release:

git commit -m "vM.m.p"
git push
gh release create "vM.m.p"
git fetch --tags origin master

=======

1. Create a commit with the version number as the commit message (e.g. v1.3.0)
2. Tag the commit with the version number as the tag name (e.g. v1.3.0)
3. Push the commit and tag to GitHub
4. Create a new GitHub release with the version number as the tag (e.g. v1.3.0). List the key changes in the release notes.

33cbc1d (add batchrelease controller)