Skip to content

Latest commit

 

History

History
18 lines (14 loc) · 1.04 KB

RELEASE-HOWTO.md

File metadata and controls

18 lines (14 loc) · 1.04 KB
Raw

RELEASE HOWTO

A runbook style document for project owners to have some consistency in the process used to make a new release and set expectations for contributors.

Version Number

Each release will see an increment in the version number acording to SEMVER

Release Process

  1. Update VERSION in Makefile, Chart.yaml and values.yaml to the intended release version. Check the CHANGELOG.md references the right version and date.
  2. Run make alltests
  3. Run make e2e or helm.install & e2e.quick
  4. Publish the image to dockerhub (currently).
  5. Commit go.mod and go.sum
  6. Create a tag = VERSION
  7. Create a release with the chart as a release artifact.

Post Release

  1. As the first commit after release update VERSION in Makefile, version in Chart.yaml, heading in CHNAGELOG.md, and tag in values.yaml with the suffix 'next' such that so that further commits are clearly contributions to the next release. Consequently installers from source helm should check out the release tag commit to find the appropriate image by default.