Release v0.7.0

[klihub]

Release Process

• Create and push new release branch
• Local release preparations (on the release branch)
  • Run e2e tests
  • Sync/tidy up dependencies.
    • Run go mod tidy.
    • Run git commit -m 'go.mod,go.sum: update dependencies.' go.{mod,sum}, if necessary.
  • Run git tag -a -m "NRI plugins $VERSION" $VERSION.
• Publishing
  • Push the tag with git push $VERSION.
  • Check that new container images are published for the tag.

    • for i in nri-resource-policy-topology-aware nri-resource-policy-balloons nri-resource-policy-template nri-config-manager nri-memory-qos nri-memtierd; do \
          skopeo inspect --format "$i: {{.Digest}}" docker://ghcr.io/containers/nri-plugins/$i:$VERSION;
      done
      

  • Finalize the new draft release created by CI
    • Check that all artefacts (Helm charts) were uploaded
    • Write the change log to the release.
    • Get the change log OK'd by other maintainers.
  • Publish the draft as a release.
  • Verify that the Helm repo was updated
  • Add a link to the tagged release in this issue.
  • Generate the operator bundle by running make bundle within deployment/operator directory and submit the generated content to the community-operators.
• Create and push unannotated development tag X.Y.0-devel for next release cycle.
• Close this issue.

[klihub]

v0.7.0 release tagged and published

[klihub]

/cc @fmuyassarov Could you take care of the operator bundle ?

[fmuyassarov]

/cc @fmuyassarov Could you take care of the operator bundle ?

k8s-operatorhub/community-operators#4597