mirrors/node-feature-discovery
1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/node-feature-discovery.git synced 2024-12-14 11:57:51 +00:00
Code Activity
node-feature-discovery/.github/ISSUE_TEMPLATE/new-patch-release.md

46 lines
2.3 KiB
Markdown
Raw Permalink Normal View History

github: add a separate issue template for patch releases Also simplify the wording on the major release issue template, eliminating "for a major release" from the text.
2023-09-19 11:40:23 +00:00
---
name: New Patch Release
about: Cut a new patch release
title: Release v0.x.y
assignees: adrianchiris, ArangoGutierrez, fmuyassarov, jjacobelli, kad, marquiz, PiotrProkop, zvonkok
---
## Release Checklist
<!--
Please do not remove items from the 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](https://github.com/kubernetes-sigs/node-feature-discovery/releases)
- [ ] 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
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 07:12:23 +00:00
`git tag -s -m "NFD release $VERSION" $VERSION`
Release template: Document tagging for API submodule Signed-off-by: Carlos Eduardo Arango Gutierrez <eduardoa@nvidia.com>
2024-11-04 10:35:28 +00:00
- [ ] An OWNER runs
`git tag -s -m "NFD API release $VERSION" api/nfd/$VERSION`
github: add a separate issue template for patch releases Also simplify the wording on the major release issue template, eliminating "for a major release" from the text.
2023-09-19 11:40:23 +00:00
- [ ] An OWNER pushes the tag with
Release template: Document tagging for API submodule Signed-off-by: Carlos Eduardo Arango Gutierrez <eduardoa@nvidia.com>
2024-11-04 10:35:28 +00:00
`git push $VERSION api/nfd/$VERSION`
github: add a separate issue template for patch releases Also simplify the wording on the major release issue template, eliminating "for a major release" from the text.
2023-09-19 11:40:23 +00:00
- Triggers prow to build and publish a staging container image
`gcr.io/k8s-staging-nfd/node-feature-discovery:$VERSION`
- Triggers build of the documentation and publish it at
https://kubernetes-sigs.github.io/node-feature-discovery/0.$MAJ/
- [ ] Submit a PR against [k8s.io](https://github.com/kubernetes/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](https://github.com/kubernetes-sigs/node-feature-discovery/releases)
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
<!--
Describe changes since the last release here.
-->
Copy permalink