podman/vendor/github.com/onsi/ginkgo/RELEASING.md at eed2ad9ef257fab11f76589c68f98bd595dd4396

mirror of https://github.com/containers/podman.git synced 2025-12-04 04:09:40 +08:00

Files

Valentin Rothberg 9ac0ebb079 Cirrus: add vendor_check_task

* Make sure that all vendored dependencies are in sync with the code and
  the vendor.conf by running `make vendor` with a follow-up status check
  of the git tree.

* Vendor ginkgo and gomega to include the test dependencies.

Signed-off-by: Chris Evic <cevich@redhat.com>
Signed-off-by: Valentin Rothberg <rothberg@redhat.com>

2019-02-06 11:14:06 +01:00

891 B

Raw Blame History

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

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)

Update VERSION in config/config.go
Create a commit with the version number as the commit message (e.g. v1.3.0)
Tag the commit with the version number as the tag name (e.g. v1.3.0)
Push the commit and tag to GitHub
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.

891 B Raw Blame History

891 B

Raw Blame History