Address several issues with Stages#276
Open
annevk wants to merge 2 commits into
Open
Conversation
* Fix Stage 3 entrance/quality contradiction: PR is now an entrance requirement, not something created during the stage (closes #255). * Stage 4 "signifies": past-tense to reflect the PR is already merged ("has resulted in a change to" rather than "approved to change"). * Drop the "approved incubation venue" requirement from Stage 1 and Stage 2: an explainer or draft can live anywhere it's linkable. * Move Stage 0's and Stage 1's explainer requirements into the entrance criteria column; spec quality is "—" where there's no relevant specification text (Stage 0, Stage 1, and Stage 4). * State the implementer bar in every stage's entrance criteria, and scope the prose's two-implementer rule to "advancing beyond Stage 1" so it no longer contradicts Stage 1's one-implementer threshold. * Drop redundant entrance items now duplicated by other columns (Stage 3 "Complete specification text", Stage 4 quality column). * Improve the Stage 1 explainer link. And make various other minor editorial improvements.
tantek
requested changes
Jun 17, 2026
tantek
left a comment
tantek
left a comment
Member
There was a problem hiding this comment.
Looks good overall. One concern with a bit of text that was dropped that I would prefer to keep.
eemeli
reviewed
Jun 17, 2026
Member
Author
|
Thanks for catching that! I attempted to capture these comments in a fixup commit. I also took the opportunity to remove "prototype" from Stage 1 as that was never really a thing in our Working Mode and not necessarily relevant for larger proposals. |
bkardell
reviewed
Jun 18, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
requirement, not something created during the stage (closes Stages: "Specification quality at entrance" is confusing #255).
("has resulted in a change to" rather than "approved to change").
Stage 2 and replace it with the WHATWG identifying a suitable place.
entrance criteria column; spec quality is "—" where there's no
relevant specification text (Stage 0, Stage 1, and Stage 4).
scope the prose's two-implementer rule to "advancing beyond Stage 1"
so it no longer contradicts Stage 1's one-implementer threshold.
(Stage 3 "Complete specification text", Stage 4 quality column).
And make various other editorial improvements.