Closed mwysokin closed 1 week ago
Hi @mwysokin. Thanks for your PR.
I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
Name | Link |
---|---|
Latest commit | 8ab504553602863f584f63430ea9ff71cd97bf9c |
Latest deploy log | https://app.netlify.com/sites/kubernetes-sigs-kueue/deploys/673b6bf7b37ef800087e8f11 |
Deploy Preview | https://deploy-preview-3586--kubernetes-sigs-kueue.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
/lgtm Leaving final (approve) tagging to @tenzen-y . IIUC we then cherry-pick it to 0.9 and update the release notes on the page.
LGTM label has been added.
/ok-to-test
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mwysokin, tenzen-y
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/cherry-pick release-0.9
@tenzen-y: new pull request created: #3597
/cherry-pick website
@tenzen-y: new pull request created: #3598
In any case, the notification would be helpful. Thanks!
I will update the release page changelog, later.
/lgtm /approve
I updated the release page.
What type of PR is this?
/kind documentation
What this PR does / why we need it:
We previously suggested during KubeCon and on other occasions that Rank Ordering in TAS would be part of Kueue release
0.9.1
. Since the users are highly anticipating this feature and release0.9.1
was released without it we want to make sure that we didn't mislead anyone and so that people don't waste their time testing feature which was not part of the release. That's why I'd like to request adding this note section to the0.9.1
release notes to make things very clear.Does this PR introduce a user-facing change?