Agent version check document should not refer specific agent version #14123
Conversation
This file contains 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
v2 agent is obsolete
|
@shunkino : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I found this document little confusing because it mentions v2 agent even though current mainstream agent version is v3.
v2 agent is already obsolete, so I thinks it's better to just remove v2 and make it easier to understand. The way user check agent version does not change between v2 and v3 agents.
I've noticed that this section is included from the file includes/v2/qa-agent-version.md. If the content of this FAQ does not depend on the Agent version, it might be better to save it in a directory other than the version-specific ones. Alternatively, we could create the same file in the v3 directory and rewrite the description of v2 for v3. I would appreciate it if you could consider how to best revise it.