Closed alculquicondor closed 2 months ago
@tenzen-y @trasc @mimowo I think we have all the implementation PRs we need. Am I missing something?
I want to hold from merging #2173 and its dependencies. Also #2196 has some complications.
OTOH, I'm still yet to submit a PR for fair sharing documentation.
@tenzen-y @trasc @mimowo I think we have all the implementation PRs we need. Am I missing something?
I want to hold from merging #2173 and its dependencies. Also #2196 has some complications.
OTOH, I'm still yet to submit a PR for fair sharing documentation.
@alculquicondor I don't have any blocker. Postponing those features sounds good to me. But, it would be better to include #2309 and #2310 in v0.7.
@tenzen-y @trasc @mimowo I think we have all the implementation PRs we need. Am I missing something?
I want to hold from merging #2173 and its dependencies. Also #2196 has some complications.
OTOH, I'm still yet to submit a PR for fair sharing documentation.
SGTM
sgtm, I don't have any blockers, https://github.com/kubernetes-sigs/kueue/pull/2268/ is a nice-to-have.
/close
@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
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: kubernetes/k8s.io#6857registry.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
.main
branch : https://github.com/kubernetes-sigs/kueue/pull/2336README.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