msb-public
/
helm
mirror of https://github.com/helm/helm
1
0
Code Issues Projects Releases Wiki Activity

Merge pull request #4407 from bacongobbler/release-notes-rc-notation

Browse Source 
use dot notation for release candidates
pull/4200/merge
Matthew Fisher 6 years ago committed by GitHub
parent 56154102a2 fb64bb66de
commit bda27b6f2a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File

8
docs/release_checklist.md
Unescape View File

@ -4,7 +4,7 @@
## Release Meetings ## Release Meetings
As part of the release process, two of the weekly developer calls will be co-opted As part of the release process, two of the weekly developer calls will be co-opted
as "release meetings." as "release meetings."
### Start of the Release Cycle ### Start of the Release Cycle
The first developer call after a release will be used as the release meeting to The first developer call after a release will be used as the release meeting to
@ -52,7 +52,7 @@ In this doc, we are going to reference a few environment variables as well, whic
```shell ```shell
export RELEASE_NAME=vX.Y.0 export RELEASE_NAME=vX.Y.0
export RELEASE_BRANCH_NAME="release-X.Y" export RELEASE_BRANCH_NAME="release-X.Y"
export RELEASE_CANDIDATE_NAME="$RELEASE_NAME-rc1" export RELEASE_CANDIDATE_NAME="$RELEASE_NAME-rc.1"
``` ```
If you are creating a patch release, you may want to use the following instead: If you are creating a patch release, you may want to use the following instead:
@ -61,7 +61,7 @@ If you are creating a patch release, you may want to use the following instead:
export PREVIOUS_PATCH_RELEASE=vX.Y.Z export PREVIOUS_PATCH_RELEASE=vX.Y.Z
export RELEASE_NAME=vX.Y.Z+1 export RELEASE_NAME=vX.Y.Z+1
export RELEASE_BRANCH_NAME="release-X.Y" export RELEASE_BRANCH_NAME="release-X.Y"
export RELEASE_CANDIDATE_NAME="$RELEASE_NAME-rc1" export RELEASE_CANDIDATE_NAME="$RELEASE_NAME-rc.1"
``` ```
## 1. Create the Release Branch ## 1. Create the Release Branch
@ -188,7 +188,7 @@ You will also want to update the release version number and the CHANGELOG as we
After that, tag it and notify users of the new release candidate: After that, tag it and notify users of the new release candidate:
```shell ```shell
export RELEASE_CANDIDATE_NAME="$RELEASE_NAME-rc2" export RELEASE_CANDIDATE_NAME="$RELEASE_NAME-rc.2"
git tag --sign --annotate "${RELEASE_CANDIDATE_NAME}" --message "Helm release ${RELEASE_CANDIDATE_NAME}" git tag --sign --annotate "${RELEASE_CANDIDATE_NAME}" --message "Helm release ${RELEASE_CANDIDATE_NAME}"
git push upstream $RELEASE_CANDIDATE_NAME git push upstream $RELEASE_CANDIDATE_NAME
``` ```

Write Preview
Loading…
Cancel
Save