1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/node-feature-discovery.git synced 2024-12-14 11:57:51 +00:00
node-feature-discovery/.github/ISSUE_TEMPLATE/new-patch-release.md
Markus Lehtonen 48d06ae366 github: update tagging instructions in release checklists
Simplify and standardize the git tag message body. Adding the full
changelog in the tag description feels unnecessary and cannot be
corrected after the fact.
2023-12-22 10:00:13 +02:00

2.2 KiB

name about title assignees
New Patch Release Cut a new patch release Release v0.x.y adrianchiris, ArangoGutierrez, fmuyassarov, jjacobelli, kad, marquiz, PiotrProkop, zvonkok

Release Checklist

  • Verify that the changelog in this issue is up-to-date
  • 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 pushes the tag with git push $VERSION
  • 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.
  • For a point release of the latest newest release branch, 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
  • Close this issue

Changelog