Release v0.11.3

[marquiz]

Release Checklist

• All OWNERS must LGTM the release proposal
• Verify that the changelog in this issue is up-to-date
• For major releases (v0.$MAJ.0) create new release branch
  • 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
• 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 $VERSION
  and inserts the changelog into the tag description.
• An OWNER pushes the tag with
  git push $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 [email protected] with the subject [ANNOUNCE] node-feature-discovery $VERSION is released
• Add a link to the release announcement in this issue
• [z] For a major release (or a point release of the latest major release), 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
  • [z] Wait for the PR to be merged
• For a major release, 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.
• [z] Close this issue

Changelog

Changelog

This point release fixes a bug in nfd-topology-updater that caused it to silently stop in some scenarios. It also updates dependencies and refreshes the base container image to Debian bullseye-slim.

List of PRs

• docs: fix incorrect shell snippet for removing labels ([release-0.11] docs: fix incorrect shell snippet for removing labels #893)
• Update base image to Debian bullseye ([release-0.11] Update base image to Debian bullseye #942)
• cpu: ignore unknown cpuid flags on non-x86 ([release-0.11] cpu: ignore unknown cpuid flags on non-x86 #943)
• topology-updater: continue looping on scan error ([release-0.11] topology-updater: continue looping on scan error #941)
• go.mod: bump kubernetes to v1.23.13 ([release-0.11] go.mod: bump kubernetes to v1.23.13 #944)

[marquiz]

One more patch release on v0.11 would feel justifiable

[marquiz]

Filed one PR to update deps too: #944

[fmuyassarov]

Although not related, but when is the planned date to cut the release for v0.12.x ?

[marquiz]

Although not related, but when is the planned date to cut the release for v0.12.x ?

When we get the stuff merged 😊 I'd hope to see that by the holiday break in December...

[marquiz]

GitHub release page:
https://github.com/kubernetes-sigs/node-feature-discovery/releases/tag/v0.11.3

Release announcement email:
https://groups.google.com/a/kubernetes.io/g/dev/c/yGR2xxHD4QQ

[marquiz]

/close

[k8s-ci-robot]

@marquiz: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.