Release v0.18

[marquiz]

Release Checklist

• All OWNERS must LGTM the release proposal
• Verify that the changelog in this issue is up-to-date
• Create new release branch (release v0.$MAJ.0)
  • an OWNER creates a vanilla release branch with
    git branch release-0.$MAJ master
  • An OWNER pushes the new release branch with
    git push release-0.$MAJ
  • Create Prow pre-submit job configuration for the new release branch in K8s
    test-infra, submit a PR
  • Wait for the test-infra Prow config PR to be merged
• Run hack/prepare-release.sh $VERSION to turn references to point to the upcoming release
  (README, deployment templates, docs configuration, test/e2e flags), submit a PR against the release branch
• An OWNER prepares a draft release
  • Create a draft release at Github releases page
  • Write the change log into the draft release
  • Upload release artefacts generated by prepare-release.sh script above to the draft release
• An OWNER runs
  git tag -s -m "NFD release $VERSION" $VERSION
• An OWNER runs
  git tag -s -m "NFD API release $VERSION" api/nfd/$VERSION
• An OWNER pushes the tag with
  git push $VERSION api/nfd/$VERSION
  • Triggers prow to build and publish a staging container image
    gcr.io/k8s-staging-nfd/node-feature-discovery:$VERSION
  • Triggers build of the documentation and publish it at
    https://kubernetes-sigs.github.io/node-feature-discovery/0.$MAJ/
• Submit a PR against k8s.io, updating registry.k8s.io/images/k8s-staging-nfd/images.yaml to promote the container images (both "full" and "minimal" variants) to production
• Wait for the PR to be merged and verify that the image (registry.k8s.io/nfd/node-feature-discovery:$VERSION) is available.
• Publish the draft release prepared at the Github releases page
  which will also trigger a Helm repo index update to add the latest release
• Add a link to the tagged release in this issue.
• Send an announcement email to dev@kubernetes.io with the subject [ANNOUNCE] node-feature-discovery $VERSION is released
  • Add a link to the release announcement in this issue
• Update README in master branch
  • Update references e.g. by running hack/prepare-release.sh $VERSION but only committing README.md, and,
    submit a PR
  • Wait for the PR to be merged
• Create an unannotated devel tag in the master branch, on the first commit that gets merged after the release branch has been created (presumably the README update commit above), and, push the tag:
  DEVEL=v0.$(($MAJ+1)).0-devel; git tag $DEVEL master && git push $DEVEL
  This ensures that the devel builds on the master branch will have a meaningful version number.
• Close this issue

Changelog