summaryrefslogtreecommitdiff
path: root/vendor/github.com/onsi/gomega/RELEASING.md
diff options
context:
space:
mode:
Diffstat (limited to 'vendor/github.com/onsi/gomega/RELEASING.md')
-rw-r--r--vendor/github.com/onsi/gomega/RELEASING.md12
1 files changed, 0 insertions, 12 deletions
diff --git a/vendor/github.com/onsi/gomega/RELEASING.md b/vendor/github.com/onsi/gomega/RELEASING.md
deleted file mode 100644
index 998d64e..0000000
--- a/vendor/github.com/onsi/gomega/RELEASING.md
+++ /dev/null
@@ -1,12 +0,0 @@
-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.