Codebase list golang-gomega / 8ce85adf-8ca5-4ec4-845c-d46ad8a30ce5/upstream RELEASING.md
8ce85adf-8ca5-4ec4-845c-d46ad8a30ce5/upstream

Tree @8ce85adf-8ca5-4ec4-845c-d46ad8a30ce5/upstream (Download .tar.gz)

RELEASING.md @8ce85adf-8ca5-4ec4-845c-d46ad8a30ce5/upstream — raw · history · blame 

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
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.