Skip to content

Latest commit

 

History

History
13 lines (11 loc) · 1.03 KB

RELEASE.md

File metadata and controls

13 lines (11 loc) · 1.03 KB

Release Process

prometheus-adapter 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 OWNERS 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 -s $VERSION, inserts the changelog and pushes the tag with git push $VERSION. Then waits for prow.k8s.io to build and push new images to gcr.io/k8s-staging-prometheus-adapter
  6. A PR in kubernetes/k8s.io is created to release images to k8s.gcr.io
  7. An OWNER publishes the GitHub release
  8. An announcement email is sent to kubernetes-sig-instrumentation@googlegroups.com with the subject [ANNOUNCE] prometheus-adapter $VERSION is released
  9. The release issue is closed