KubeRay Release Process¶
You need KubeRay GitHub write permissions to cut a release branch and create a release tag.
Each major release (e.g.
0.4) is managed in its own GitHub branch.
To release KubeRay, cut a release branch (e.g.
release-0.4) from master and build commits on that branch
until you reach a satisfactory final release commit.
Immediately after cutting the release branch, create a commit for a release candidate (e.g.
and build the associated artifacts (images and charts).
If further changes need to be made to the release, pick changes from the master branch into the release branch.
Make as many release candidates as necessary until a stable final release commit is reached.
Then build final release artifacts, publish release notes, and announce the release.
Ensure that the desired master commit is stable by verifying the following:
- The last master commit you want to release passes the Go-build-and-test workflow.
- The KubeRay documentation is up-to-date.
- All example configurations use the latest released version of Ray.
- The example configurations work.
During the KubeRay
0.4.0 release, we used spreadsheets to track manual testing and documentation updates. Most of the manual release testing was done immediately before making the branch cut. No substantive code changes were made between the time of the branch cut and final release.
For future releases, we plan to automate more of the relese testing process. Use your best judgement to decide when to test manually during the release process. To track the progress of KubeRay test development, see the CI label on the KubeRay GitHub.
Depending on whether the release is for a major, minor, or patch version, take the following steps.
- Major or Minor version (e.g.
1.0.0). Create a release branch named
git checkout -b release-0.4 git push -u upstream release-0.4
- Patch version (e.g.
0.4.1). You don't need to cut a release branch for a patch version. Instead add commits to the release branch.
- Major or Minor version (e.g.
Create a first release candidate (
a. Merge a PR into the release branch updating Helm chart versions, Helm chart image tags, and kustomize manifest image tags. For
v0.4.0-rc0, we did this in two PRs 1 2, but it's fine to do it in a single PR. Note that we no longer include appVersion in the Helm charts.
rc0images using the release-image-build workflow on GitHub actions. You will prompted for a commit reference and an image tag. The commit reference should be the SHA of the tip of the release branch. The image tag should be
c. Tag the tip of release branch with
git tag v0.4.0-rc.0 git push upstream v0.4.0-rc.0
d. Release rc0 Helm charts following the instructions.
e. Open a PR into the Ray repo updating the operator version used in the autoscaler integration test. Make any adjustments necessary for the test to pass. Example. Make sure the test labelled kubernetes-operator passes before merging.
f. Announce the
rc0release on the KubeRay slack, with deployment instructions. Example..
If necessary, create more release candidates (
- Resolve issues with the release branch by cherry picking master commits into the release branch.
- When cherry-picking changes, it is best to open a PR against the release branch -- don't push directly to the release branch.
- When the next release candidate is ready, repeat step 4 above.
Create a final release by repeating Step 4 once more using the tag of the release (
vX.Y.Z) with no
make releasein cli folder and generate
kuberay-$VERSION-linux-amd64.zipfiles. Upload them to the GitHub release.
Follow the instructions to generate release notes and add notes in the GitHub release.
Send a PR to add the release notes to CHANGELOG.md.
Update KubeRay versions in Ray and KubeRay master. Ray Example, KubeRay Example.
Announce the release on the KubeRay slack!