generated from kubernetes/kubernetes-template-project
-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release v0.6.0 #655
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Release Checklist
git branch release-$MAJ.$MIN main
git push release-$MAJ.$MIN
Submit a PR against the release branch:
make artifacts IMAGE_REGISTRY=registry.k8s.io/jobset GIT_TAG=$VERSION
to generate the artifacts and upload the files in the
artifacts
folderto the draft release.
git tag -s $VERSION
and inserts the changelog into the tag description.
To perform this step, you need a PGP key registered on github.
git push $VERSION
gcr.io/k8s-staging-jobset/jobset:$VERSION
updating
k8s.gcr.io/images/k8s-staging-jobset/images.yaml
topromote the container images
to production:
registry.k8s.io/jobset/jobset:$VERSION
is available.[email protected]
,[email protected]
and[email protected]
with the subject[ANNOUNCE] JobSet $VERSION is released
README.md
anddocs/setup/install.md
in
main
branch:main
branch, on the first commit that gets merged after the releasebranch has been created (presumably the README update commit above), and, push the tag:
DEVEL=v0.$(($MAJ+1)).0-devel; git tag $DEVEL main && git push $DEVEL
This ensures that the devel builds on the
main
branch will have a meaningful version number.Changelog
Highlights
What's Changed
MASTER_ADDR
by @song-william in Update _index.mdMASTER_ADDR
#604The text was updated successfully, but these errors were encountered: