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

github: update release process to create a 'devel' tag

Browse source 
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.
This commit is contained in:
Markus Lehtonen 2021-03-30 19:32:33 +03:00
parent 386ccf4c20
commit d1e8deaac1
1 changed files with 4 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -39,10 +39,13 @@ Please do not remove items from the checklist
- [ ] 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
- [ ] 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,
submit a PR
- [ ] Wait for the PR to be merged
- [ ] For a major release, 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:
`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.
- [ ] Close this issue