You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run make artifacts IMAGE_REGISTRY=registry.k8s.io/jobset GIT_TAG=$VERSION
to generate the artifacts and upload the files in the artifacts folder
to the draft release.
An OWNER creates a signed tag running git tag -s $VERSION
and inserts the changelog into the tag description.
To perform this step, you need a PGP key registered on github.
An OWNER pushes the tag with git push $VERSION
Triggers prow to build and publish a staging container image gcr.io/k8s-staging-jobset/jobset:$VERSION
Add a link to the release announcement in this issue:
For a major or minor release, update README.md and docs/setup/install.md
in main branch:
For a major or minor release, create an unannotated devel tag in the 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 the main branch will have a meaningful version number.
Close this issue
Changelog
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: