kubernetes-sigs/node-feature-discovery-operator

Release v0.6.0

ArangoGutierrez opened this issue · 16 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
    • An OWNER creates a vanilla release branch from master
      git branch release-0.$MAJ master
    • An OWNER pushes the newly created branch
      git push release-0.$MAJ
  • Update references in docs/_config.yml (version, release and container_image fields) to point to the upcoming release and subbmit a PR against the release branch
  • 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 registry.k8s.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 (registry.k8s.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 for the $VERSION release 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

marquiz commented

Yeah +100, I'm all in 😇 Let's just get at least #186 in

ArangoGutierrez commented

We are ready here, I'll start the cut tomorrow
PING @zvonkok

marquiz commented

We are ready here, I'll start the cut tomorrow

😎 Just a mental note that it might be good to have a helper script á la hack/prepare-release.sh in NFD to "remember" all steps. E.g. now we have the Helm chart as a new item to remember, things seem to pile up. I'm not sure if a bash script like that is the best option but even that does the job.

  • 🚀1
ArangoGutierrez commented

Yes sir

marquiz commented

I don't mean it needs to be done for this release. But OTOH it might not be a huge job to "document" all the steps required to prepare the release branch in a script. Up to you

  • 👍1
ArangoGutierrez commented

We need: #190

  • 🚀1
ArangoGutierrez commented 
[eduardo@fedora ~]$ skopeo list-tags docker://registry.k8s.io/nfd/node-feature-discovery-operator |grep v0.6
        "v0.6.0",
        "v0.6.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.