Skip to content

Latest commit

 

History

History
14 lines (12 loc) · 1.06 KB

RELEASE.md

File metadata and controls

14 lines (12 loc) · 1.06 KB

Release Process

The Metrics Server 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. At least one OWNER must LGTM this release
  3. A PR that bumps version hardcoded in code is created and merged
  4. An OWNER creates a draft GitHub release
  5. An OWNER creates a release tag using GIT_TAG=$VERSION make release-tag and waits for prow.k8s.io to build and push new images to gcr.io/k8s-staging-metrics-server
  6. An OWNER builds the release manifests using make release-manifests and uploads them to Github release
  7. A PR in kubernetes/k8s.io is created to release images to k8s.gcr.io
  8. An OWNER publishes the GitHub release
  9. An announcement email is sent to [email protected] with the subject [ANNOUNCE] metrics-server $VERSION is released
  10. The release issue is closed