Skip to content

RELEASE.md

Latest commit

 

History

History
26 lines (18 loc) · 1.74 KB

RELEASE.md

File metadata and controls

26 lines (18 loc) · 1.74 KB

Release Process

The Kubebuilder Project is released on an as-needed basis. The process is as follows:

  1. An issue is proposing a new release with a changelog since the last release. You will need to use the kubebuilder-release-tools to generate the notes. See here
  2. All OWNERS must LGTM this release
  3. An OWNER runs git tag -s $VERSION and pushes the tag with git push $VERSION. Note that after the OWNER push the tag the CI will automatically add the release notes and the assets.
  4. A PR needs to be created to merge master branch into book-v3 to pick up the new docs.
  5. The release issue is closed
  6. An announcement email is sent to kubebuilder@googlegroups.com with the subject [ANNOUNCE] kubebuilder $VERSION is released

Notes: This process does not apply to EAP or alpha (pre-)releases which may be cut at any time for development and testing.

For further information about versioning and update the Kubebuilder binaries check the versioning doc.

HEAD releases

The binaries releases for HEAD are available here: