Closed tenzen-y closed 5 months ago
@mimowo @alculquicondor Please let me know if there is any possible issues we should include in this release.
#1846 should be included in this.
1846 does not affect 0.6, right?
Yes, that's right. I found it by @astefanutti's comment.
https://github.com/kubernetes-sigs/kueue/pull/1846#issuecomment-1998026703
PTAL at release notes.
PTAL at release notes.
I removed unnecessary spaces from release notes. Could you perform a command to get the release note again?
It looks like there was only one. Updated. And #1847 as well.
It looks like there was only one. Updated. And #1847 as well.
LGTM!
/close
@alculquicondor: Closing this issue.
Release Checklist
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 theartifacts
folder to 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
registry.k8s.io/images/k8s-staging-kueue/images.yaml
to promote the container images to production: https://github.com/kubernetes/k8s.io/pull/6578registry.k8s.io/kueue/kueue:$VERSION
is available.main
branch into thewebsite
branch to publish the updated documentation.sig-scheduling@kubernetes.io
andwg-batch@kubernetes.io
with the subject[ANNOUNCE] kueue $VERSION is released
. https://groups.google.com/a/kubernetes.io/g/wg-batch/c/gHCQETA8x2smain
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 release branch 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 themain
branch will have a meaningful version number.Changelog