Skip to content

Latest commit

 

History

History
20 lines (14 loc) · 1.08 KB

RELEASE.md

File metadata and controls

20 lines (14 loc) · 1.08 KB
Raw

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
  2. All OWNERS must LGTM this release
  3. An OWNER runs git tag -s $VERSION and inserts the changelog and pushes the tag with git push $VERSION
  4. A PR needs to be created to merge master branch into book-v2 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

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

HEAD releases

The binaries releases for HEAD are available here: