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-release.md

60 lines
3.3 KiB
Markdown
Raw Permalink Normal View History

Replace RELEASE.md with an issue template In addition to just moving the content, update release process. Adjust to the latest prow-based workflow. Capture steps required for documentation.
2020-10-09 08:42:06 +00:00
---
name: New Release
about: Propose a new release
title: Release v0.x.0
github: update assignees in new-release issue template Sync with OWNERS file.
2023-07-21 06:06:42 +00:00
assignees: adrianchiris, ArangoGutierrez, fmuyassarov, jjacobelli, kad, marquiz, PiotrProkop, zvonkok
Replace RELEASE.md with an issue template In addition to just moving the content, update release process. Adjust to the latest prow-based workflow. Capture steps required for documentation.
2020-10-09 08:42:06 +00:00
---
## Release Checklist
<!--
Please do not remove items from the checklist
-->
- [ ] All [OWNERS](https://github.com/kubernetes-sigs/node-feature-discovery/blob/master/OWNERS) must LGTM the release proposal
- [ ] Verify that the changelog in this issue is up-to-date
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
- [ ] Create new release branch (release v0.$MAJ.0)
github: re-organize the release process slightly Reorganize the steps in the release process slightly to make it more consistent and streamlined. Also update the kubernetes-dev mailing list address.
2022-01-11 19:43:09 +00:00
- [ ] an OWNER creates a vanilla release branch with
`git branch release-0.$MAJ master`
- [ ] An OWNER pushes the new release branch with
github: update new-release issue template
2020-12-04 17:48:58 +00:00
`git push release-0.$MAJ`
github: update new-release issue template Add instructions about creating prow jobs for new release branches.
2022-12-21 08:24:48 +00:00
- [ ] Create Prow pre-submit job configuration for the new release branch in K8s
[test-infra](https://github.com/kubernetes/test-infra), submit a PR
- [ ] Wait for the test-infra Prow config PR to be merged
scripts: move hacky scripts to hack directory Move prepare-release.sh and kustomize.sh from scripts/ to hack/.
2022-09-06 08:45:46 +00:00
- [ ] Run `hack/prepare-release.sh $VERSION` to turn references to point to the upcoming release
Fix a couple typos Signed-off-by: Carlos Eduardo Arango Gutierrez <carangog@redhat.com>
2022-03-23 23:15:22 +00:00
(README, deployment templates, docs configuration, test/e2e flags), submit a PR against the release branch
github: re-organize the release process slightly Reorganize the steps in the release process slightly to make it more consistent and streamlined. Also update the kubernetes-dev mailing list address.
2022-01-11 19:43:09 +00:00
- 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`
Replace RELEASE.md with an issue template In addition to just moving the content, update release process. Adjust to the latest prow-based workflow. Capture steps required for documentation.
2020-10-09 08:42:06 +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: update new-release issue template
2020-12-04 17:48:58 +00:00
- Triggers prow to build and publish a staging container image
Replace RELEASE.md with an issue template In addition to just moving the content, update release process. Adjust to the latest prow-based workflow. Capture steps required for documentation.
2020-10-09 08:42:06 +00:00
`gcr.io/k8s-staging-nfd/node-feature-discovery:$VERSION`
github: update new-release issue template
2020-12-04 17:48:58 +00:00
- Triggers build of the documentation and publish it at
github: small fix in new-release issue template
2022-06-07 15:43:19 +00:00
https://kubernetes-sigs.github.io/node-feature-discovery/0.$MAJ/
Update NFD registry to registry.k8s.io Kubernetes has moved to a new container image registry: https://groups.google.com/a/kubernetes.io/g/dev/c/DYZYNQ_A6_c/m/FpHqeVR2BAAJ
2022-09-12 08:21:12 +00:00
- [ ] 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.
github: update release process in new-release issue template Capture process for Helm charts and remove some outdated bits.
2021-02-26 14:08:19 +00:00
- [ ] Publish the draft release prepared at the [Github releases page](https://github.com/kubernetes-sigs/node-feature-discovery/releases)
github: update gh-pages on published releases This will make the Helm repo to be updated at release time.
2021-03-18 13:32:15 +00:00
which will also trigger a Helm repo index update to add the latest release
Replace RELEASE.md with an issue template In addition to just moving the content, update release process. Adjust to the latest prow-based workflow. Capture steps required for documentation.
2020-10-09 08:42:06 +00:00
- [ ] Add a link to the tagged release in this issue.
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
- [ ] Send an announcement email to `dev@kubernetes.io` with the subject `[ANNOUNCE] node-feature-discovery $VERSION is released`
github: update new-release issue template Only instruct to spam kubernetes dev mailing list on major releases.
2023-06-01 12:43:49 +00:00
- [ ] Add a link to the release announcement in this issue
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
- [ ] Update README in master branch
scripts: move hacky scripts to hack directory Move prepare-release.sh and kustomize.sh from scripts/ to hack/.
2022-09-06 08:45:46 +00:00
- [ ] Update references e.g. by running `hack/prepare-release.sh $VERSION` but **only** committing README.md, and,
github: update gh-pages on published releases This will make the Helm repo to be updated at release time.
2021-03-18 13:32:15 +00:00
submit a PR
- [ ] Wait for the PR to be merged
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
- [ ] Create an unannotated *devel* tag in the master branch, on the first commit that gets merged after the release branch has been created (presumably the README update commit above), and, push the tag:
github: update release process to create a 'devel' tag Aimed at fixing a problem with misleading version numbers of staging master builds. Also, clarify the instructions on upcating the README of the master branch.
2021-03-30 16:32:33 +00:00
`DEVEL=v0.$(($MAJ+1)).0-devel; git tag $DEVEL master && git push $DEVEL`
This ensures that the devel builds on the master branch will have a meaningful version number.
Replace RELEASE.md with an issue template In addition to just moving the content, update release process. Adjust to the latest prow-based workflow. Capture steps required for documentation.
2020-10-09 08:42:06 +00:00
- [ ] Close this issue
## Changelog
<!--
Describe changes since the last release here.
-->
Copy permalink