Closed mimowo closed 3 weeks ago
As we discussed with @tenzen-y we seem to have enough fixes to motivate the release. We aim for 4th Nov together with 0.9.0.
cc @tenzen-y @andrewsykim @dgrove-oss @kannon92
@mimowo Could we cherry-pick https://github.com/kubernetes-sigs/kueue/pull/3354 and https://github.com/kubernetes-sigs/kueue/pull/3323? It seems that those are obviously bug fixes.
+1
@mimowo Could we cherry-pick https://github.com/kubernetes-sigs/kueue/pull/3354 and https://github.com/kubernetes-sigs/kueue/pull/3323? It seems that those are obviously bug fixes.
Yes, sure.
@mimowo Could we cherry-pick #3354 and #3323? It seems that those are obviously bug fixes.
Yes, sure.
Thank you. Note that I think we should address this comment before cherry-picking: https://github.com/kubernetes-sigs/kueue/pull/3323#discussion_r1819460282
Any chance we can add https://github.com/kubernetes-sigs/kueue/pull/3384 to 0.8.2?
I'm supportive for that, because it is a bug and limited in scope.
Any chance we can add #3384 to 0.8.2?
@andrewsykim I'm fine with including #3384 in 0.8.2. @mimowo can lead the review and merge into the release branch.
$ docker pull registry.k8s.io/kueue/kueue:v0.8.2
v0.8.2: Pulling from kueue/kueue
0bab15eea81d: Already exists
da7816fa955e: Already exists
474437a9a06f: Download complete
bfb59b82a9b6: Already exists
a62778643d56: Already exists
9aee425378d2: Already exists
7c12895b777b: Already exists
4aa0ea1413d3: Already exists
3214acf345c0: Download complete
8ffb3c3cf71a: Already exists
c6b97f964990: Download complete
5664b15f108b: Already exists
Digest: sha256:46cf9e4b2741baa368f0b1d799f33b8f5a585f71f6b9a6bafd02768c96043f93
Status: Downloaded newer image for registry.k8s.io/kueue/kueue:v0.8.2
registry.k8s.io/kueue/kueue:v0.8.2
What's next:
View a summary of image vulnerabilities and recommendations → docker scout quickview registry.k8s.io/kueue/kueue:v0.8.2
$ kubectl get pod -n kueue-system -w
NAME READY STATUS RESTARTS AGE
kueue-controller-manager-6bb7c675fd-dcthk 0/2 ContainerCreating 0 8s
kueue-controller-manager-6bb7c675fd-dcthk 1/2 Running 0 11s
kueue-controller-manager-6bb7c675fd-dcthk 2/2 Running 0 13s
@tenzen-y: 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
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 upstream $VERSION
us-central1-docker.pkg.dev/k8s-staging-images/kueue/kueue:$VERSION
make artifacts IMAGE_REGISTRY=registry.k8s.io/kueue GIT_TAG=$VERSION
to generate the artifacts in theartifacts
folder.artifacts
folder to the draft release - either via UI orgh release upload <tag> artifacts/*
.registry.k8s.io/images/k8s-staging-kueue/images.yaml
to promote the container images to production: https://github.com/kubernetes/k8s.io/pull/7479registry.k8s.io/kueue/kueue:$VERSION
is available.main
branch :RELEASE_VERSION
inMakefile
and runmake prepare-release-branch
CHANGELOG
SECURITY-INSIGHTS.yaml
values by runningmake update-security-insights GIT_TAG=$VERSION
website
branchmain
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
.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