Skip to content
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.5.1 #1368

Closed
21 tasks done
tenzen-y opened this issue Nov 27, 2023 · 6 comments
Closed
21 tasks done

Release v0.5.1 #1368

tenzen-y opened this issue Nov 27, 2023 · 6 comments
Assignees

Comments

@tenzen-y
Copy link
Member

tenzen-y commented Nov 27, 2023

Release Checklist

  • OWNERS must LGTM the release proposal.
    At least two for minor or major releases. At least one for a patch release.
  • Verify that the changelog in this issue and the CHANGELOG folder is up-to-date
  • For major or minor releases (v$MAJ.$MIN.0), create a new release branch.
    • an OWNER creates a vanilla release branch with
      git branch release-$MAJ.$MIN main
    • An OWNER pushes the new release branch with
      git push release-$MAJ.$MIN
  • Update README.md, CHANGELOG, charts/kueue/Chart.yaml (appVersion) and charts/kueue/values.yaml (controllerManager.manager.image.tag) in the release branch: Prepare release for v0.5.1 #1374
  • An OWNER prepares a draft release
    • Write the change log into the draft release.
    • Run
      make artifacts IMAGE_REGISTRY=registry.k8s.io/kueue 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-kueue/kueue:$VERSION
  • Submit a PR against k8s.io,
    updating k8s.gcr.io/images/k8s-staging-kueue/images.yaml to
    promote the container images
    to production: Promote kueue image v0.5.1 kubernetes/k8s.io#6131
  • Wait for the PR to be merged and verify that the image registry.k8s.io/kueue/kueue:$VERSION is available.
  • Publish the draft release prepared at the Github releases page.
    Link: https://github.com/kubernetes-sigs/kueue/releases/tag/v0.5.1
  • For major or minor releases, merge the main branch into the website branch to publish the updated documentation.
  • Send an announcement email to sig-scheduling@kubernetes.io and wg-batch@kubernetes.io with the subject [ANNOUNCE] kueue $VERSION is released. Link: https://groups.google.com/a/kubernetes.io/g/wg-batch/c/1hholD9XBa0
  • Update README.md, CHANGELOG, site/config.toml, charts/kueue/Chart.yaml (appVersion) and charts/kueue/values.yaml (controllerManager.manager.image.tag) in main branch: Update latest version to v0.5.1 #1375
  • For a major or minor release, prepare the repo for the next version:
    • 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.
    • Create a milestone for the next minor release and update prow to set it automatically for new PRs:

Changelog

Changes since `v0.5.0`:

### Bug or Regression

- Fix client-go libraries bug that can not operate clusterScoped resources like ClusterQueue and ResourceFlavor. (#1294, @tenzen-y)
- Fixed fungiblity policy `whenCanPreempt: Preempt`. The admission should happen in the flavor for which preemptions were issued. (#1332, @alculquicondor)
- Fix a bug that plain pods managed by kueue will remain a terminating condition forever. (#1342, @tenzen-y)
- Fix fungibility policy `Preempt` where it was not able to utilize the next flavor if preemption was not possible. (#1366, @alculquicondor, @KunWuLuan)
@tenzen-y
Copy link
Member Author

cc: @alculquicondor

@tenzen-y
Copy link
Member Author

We need to wait to cut a patch release until #1366 is merged.

@alculquicondor
Copy link
Contributor

/assign

@tenzen-y
Copy link
Member Author

Thanks @alculquicondor!
/close

@k8s-ci-robot
Copy link
Contributor

@tenzen-y: Closing this issue.

In response to this:

Thanks @alculquicondor!
/close

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/test-infra repository.

@alculquicondor
Copy link
Contributor

/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants