1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/node-feature-discovery.git synced 2025-03-06 16:57:10 +00:00
node-feature-discovery/.github/ISSUE_TEMPLATE/new-release.md
Markus Lehtonen aa9050eca3 github: update gh-pages on published releases
This will make the Helm repo to be updated at release time.
2021-03-18 15:32:15 +02:00

2.7 KiB

name about title assignees
New Release Propose a new release Release v0.x.0 adrianchiris, ArangoGutierrez, Ethyling, kad, marquiz, zvonkok

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
  • Prepare release-0.$MAJ release branch
    • An OWNER creates a vanilla release branch from master and pushes it with git push release-0.$MAJ
    • Run scripts/prepare-release.sh $VERSION to turn references to point to the upcoming release (README, deployment templates, docs configuration, test/e2e flags), submit a PR agains 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
  • 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:$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 kubernetes-dev@googlegroups.com with the subject [ANNOUNCE] node-feature-discovery $VERSION is released
  • Add a link to the release announcement in this issue
  • For a major release, update README in master branch
    • Update references e.g. by running scripts/prepare-release.sh $VERSION but only committing README.md, and, submit a PR
    • Wait for the PR to be merged
  • Close this issue

Changelog