mirrors/node-feature-discovery
mirrors/node-feature-discovery
1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/node-feature-discovery.git synced 2025-03-05 08:17:04 +00:00
Code Activity

github: re-organize the release process slightly

Browse source 
Reorganize the steps in the release process slightly to make it more
consistent and streamlined. Also update the kubernetes-dev mailing list
address.
This commit is contained in:
Markus Lehtonen 2022-01-11 21:43:09 +02:00
parent cc08c39902
commit 1a6461ff23
1 changed files with 14 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
.github/ISSUE_TEMPLATE/new-release.md vendored
View file

@ -12,20 +12,20 @@ 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
- [ ] 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
- [ ] For major releases (v0.$MAJ.0) create new release branch
- [ ] an OWNER creates a vanilla release branch with
`git branch release-0.$MAJ master`
- [ ] An OWNER pushes the new release branch 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](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
`git tag -s $VERSION`
and inserts the changelog into the tag description.
- [ ] 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](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
`git tag -s $VERSION`
and inserts the changelog into the tag description.
- [ ] An OWNER pushes the tag with
`git push $VERSION`
- Triggers prow to build and publish a staging container image
@ -37,7 +37,7 @@ Please do not remove items from the checklist
- [ ] 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.
- [ ] Send an announcement email to `kubernetes-dev@googlegroups.com` with the subject `[ANNOUNCE] node-feature-discovery $VERSION is released`
- [ ] Send an announcement email to `dev@kubernetes.io` with the subject `[ANNOUNCE] node-feature-discovery $VERSION is released`
- [ ] Add a link to the release announcement in this issue
- [ ] For a major release (or a point release of the latest major release), update README in master branch
- [ ] Update references e.g. by running `scripts/prepare-release.sh $VERSION` but **only** committing README.md, and,