mirrors/node-feature-discovery
1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/node-feature-discovery.git synced 2024-12-14 11:57:51 +00:00
Code Activity
node-feature-discovery/RELEASE.md
Markus Lehtonen 8aa96ac976 Update RELEASE.md 
Describe the current release process. Contains some transitory steps
involving quay.io that will be removed when the CI has been adapted to
work with the new image repo.
2020-08-07 10:59:06 +03:00

2 KiB
Raw Blame History

Release Process

The node-feature-discovery code is released on an as-needed basis. The process is as follows:

  1. An issue is filed to propose a new release with a changelog since the last release. Copy the following checklist into the issue text:
  • All OWNERS must LGTM the release proposal.
  • Update the deployment templates (master, worker-daemonset, worker-job and combined)to use the new tagged container image
  • An OWNER runs git tag -s $VERSION and insert the changelog into the tag description.
  • An OWNER pushes the tag with git push $VERSION (this will also build and push a release container image to quay.io).
  • An OWNER pulls the newly tagged image from quay.io, tags it with gcr.io/k8s-staging-nfd/node-feature-discovery:$VERSION and pushes it to gcr.io/k8s-staging-nfd
  • Create a PR against k8s.io, updading k8s.gcr.io/images/k8s-staging-nfd/images.yaml to promote the release image into production.
  • Wait for the PR to be merged and verify that the image (k8s.gcr.io/nfd/node-feature-discovery:$VERSION) is available.
  • Write the change log into the Github release info.
  • Add a link to the tagged release in this issue.
  • An announcement email is sent to kubernetes-dev@googlegroups.com with the subject [ANNOUNCE] node-feature-discovery $VERSION is released. Add a link to the release announcement here.
  • Close this issue.