AI #1530: Revise Status values #1585
Merged
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
Contributor
Author
|
@jpradocueva |
jpradocueva
approved these changes
Nov 19, 2025
Contributor
jpradocueva
left a comment
jpradocueva
left a comment
There was a problem hiding this comment.
@shawnalpay, I have removed the reference to "work item", updated the diagrams, and listed status and labels in the same order as in the Project View. Please let me know if you have any comments.
Contributor
|
Approved by the group without objections or abstentions during the November 20 Members’ call. |
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.
We have added a new entry to the Status attribute of the FOCUS WG project view (
In Evaluation) to represent the Feature Request Review process we have introduced to FOCUS 1.4.This PR updates the documentation for the Status attribute in the development processes guidelines.
This PR is NOT to be approved and merged as part of 1.3, as it was not part of that release process. We can approve and merge in any Members meeting after Nov 6.