-
Notifications
You must be signed in to change notification settings - Fork 285
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.3 #2231
Comments
I'm thinking about including #2216 as a nice-to-have. |
Isn't that not a bug? Basically, we used to cherry pick only bug fixes to patch version, right? |
Ah, sure! |
I agree with you. We can say #2227 is an enhancement request to support elastic JobSet.
Thank you for sharing your progress. So, after #2278 is resolved, we can release a patch release. |
It doesn't work, I'll leave #2278 for the next patch release. |
I ended up including #2278 |
I sent an announcement email to sig-scheduling and wg-batch google groups. |
@tenzen-y: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Release Checklist
At least two for minor or major releases. At least one for a patch release.
Example:
release-notes --org kubernetes-sigs --repo kueue --branch release-0.3 --start-sha 4a0ebe7a3c5f2775cdf5fc7d60c23225660f8702 --end-sha a51cf138afe65677f5f5c97f8f8b1bc4887f73d2 --dependencies=false --required-author=""
git branch release-$MAJ.$MIN main
git push release-$MAJ.$MIN
RELEASE_BRANCH
andRELEASE_VERSION
inMakefile
and runmake prepare-release-branch
CHANGELOG
make artifacts IMAGE_REGISTRY=registry.k8s.io/kueue 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-kueue/kueue:$VERSION
updating
registry.k8s.io/images/k8s-staging-kueue/images.yaml
topromote the container images
to production: Promote Kueue v0.6.3 kubernetes/k8s.io#6846
registry.k8s.io/kueue/kueue:$VERSION
is available.Link: https://github.com/kubernetes-sigs/kueue/releases/tag/v0.6.3
main
branch into thewebsite
branch to publish the updated documentation.[email protected]
and[email protected]
with the subject[ANNOUNCE] kueue $VERSION is released
.main
branch :README.md
CHANGELOG
version
insite/config.toml
appVersion
incharts/kueue/Chart.yaml
last-updated
,last-reviewed
,commit-hash
,project-release
, anddistribution-points
inSECURITY-INSIGHTS.yaml
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
The text was updated successfully, but these errors were encountered: