kubernetes-sigs/node-feature-discovery-operator

Release v0.4.0

ArangoGutierrez opened this issue · 9 comments

ArangoGutierrez commented

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), an OWNER creates a release branch with
    git branch release-0.$MAJ master
  • An OWNER creates a vanilla release branch from master and pushes it with
    git push release-0.$MAJ
  • An OWNER creates an annotated and signed tag with
    git tag -a -s $VERSION
    and inserts the changelog into the tag description.
  • An OWNER pushes the tag with
    git push $VERSION
    This will trigger prow to build and publish a staging container image
    gcr.io/k8s-staging-nfd/node-feature-discovery-operator:$VERSION
  • Submit a PR against k8s.io, updating k8s.gcr.io/images/k8s-staging-nfd/images.yaml to promote the container image to production
  • Wait for the PR to be merged and verify that the image (k8s.gcr.io/nfd/node-feature-discovery-operator:$VERSION) is available.
  • Write the change log into the Github release info.
  • Add a link to the tagged release in this issue.
  • Create a new bundle at https://github.com/k8s-operatorhub/community-operators
  • Send an announcement email to kubernetes-dev@googlegroups.com with the subject [ANNOUNCE] node-feature-discovery-operator $VERSION is released
  • Add a link to the release announcement in this issue
  • Close this issue

Changelog

  • Drop operand.namespace from NodeFeatureDiscoveries CRD #115
  • Enable TopologyUpdater worker deployment #116
  • Enable Status report to the CR instance #117
  • Enable Finalizers for the CR instance #117
  • Add new CRD's NodeResourceTopology and NodeFeatureRules #119
  • Update dependencies to latest stable as of release cut date #120
ArangoGutierrez commented 
[eduardo@fedora k8s.io]$ skopeo list-tags docker://k8s.gcr.io/nfd/node-feature-discovery-operator  |grep v0.4
        "v0.4.0",
        "v0.4.0-minimal"
k8s-ci-robot commented

@ArangoGutierrez: 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.