diff options
| author | baude <bbaude@redhat.com> | 2019-09-17 12:58:08 -0500 |
|---|---|---|
| committer | baude <bbaude@redhat.com> | 2019-09-17 13:02:05 -0500 |
| commit | 71399a972c12fb3adeac8990ba2ba0afbd5ae3bc (patch) | |
| tree | d2d1249d4f98611022141b335e988acd794aa2c9 /vendor/github.com/onsi/gomega/RELEASING.md | |
| parent | 0fae0bb06923ce3b2b6b7900dc00cfaaad3838fd (diff) | |
origin dnsname commit
Signed-off-by: baude <bbaude@redhat.com>
Diffstat (limited to 'vendor/github.com/onsi/gomega/RELEASING.md')
| -rw-r--r-- | vendor/github.com/onsi/gomega/RELEASING.md | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/vendor/github.com/onsi/gomega/RELEASING.md b/vendor/github.com/onsi/gomega/RELEASING.md new file mode 100644 index 0000000..998d64e --- /dev/null +++ b/vendor/github.com/onsi/gomega/RELEASING.md @@ -0,0 +1,12 @@ +A Gomega release is a tagged 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) +2. Update GOMEGA_VERSION in `gomega_dsl.go` +3. Push a commit with the version number as the commit message (e.g. `v1.3.0`) +4. 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. |