Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Release v0.16.6 #1930

Closed
15 tasks done
ArangoGutierrez opened this issue Oct 25, 2024 · 8 comments
Closed
15 tasks done

Release v0.16.6 #1930

ArangoGutierrez opened this issue Oct 25, 2024 · 8 comments
Assignees
@kad @marquiz @zvonkok @PiotrProkop @jjacobelli @ArangoGutierrez @adrianchiris @fmuyassarov

Comments

@ArangoGutierrez
Copy link
Contributor

ArangoGutierrez commented Oct 25, 2024 •
edited
Loading

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
@ArangoGutierrez
Copy link
Contributor Author

I propose:

@ArangoGutierrez
Copy link
Contributor Author

/cc @elezar

@ArangoGutierrez
Copy link
Contributor Author

what else has gone into the v0.16 branch since v0.16.5?
@marquiz ?

@elezar
Copy link
Contributor

elezar commented Oct 25, 2024

The following shows some github tooling changes: v0.16.5...release-0.16

@ArangoGutierrez
Copy link
Contributor Author

Yeah, those look ok, no functional changes. that's acceptable for a point patch release

@ArangoGutierrez
Copy link
Contributor Author

@ArangoGutierrez
Copy link
Contributor Author

@ArangoGutierrez
Copy link
Contributor Author

/~https://github.com/kubernetes-sigs/node-feature-discovery/releases/tag/v0.16.6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kad kad

@marquiz marquiz

@zvonkok zvonkok

@PiotrProkop PiotrProkop

@jjacobelli jjacobelli

@ArangoGutierrez ArangoGutierrez

@adrianchiris adrianchiris

@fmuyassarov fmuyassarov

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@kad @elezar @marquiz @zvonkok @PiotrProkop @jjacobelli @ArangoGutierrez @adrianchiris @fmuyassarov