[YUNIKORN-3086] Update docs to remove deprecated queue metrics #522
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Maybe we can make this change under the next tag? |
chenyulin0719
requested changes
Jun 6, 2025
There was a problem hiding this comment.
Hi @baconYao, thanks for subbmitting the PR.
We usually handle one task per Jira ticket, so the "document branching" should be done under seperate Jira. It's quite difficult to review what has been changed in this PR.
The version-1.7.0 will be branched from /docs instead of versioned version-1.6.3.
So you can change queue.md under /docs directly.
github-actions bot
pushed a commit
to yangwwei/yunikorn-site
that referenced
this pull request
Jun 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is this PR for?
Removal of the deprecated "subsystem metrics" from the documentation in 1.7.0 version.
Subsystemrelated informationWhat type of PR is it?
What is the Jira issue?
How should this be tested?