-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Detect when Stage 3+ ES proposals get merged into main spec #307
Comments
Some elements of research on this:
So, a good process for this may be:
|
dontcallmedom
changed the title
Detect when Stage 3 ES proposals reach Stage 4 (i.e. gets merged into main spec)
Detect when Stage 3 ES proposals reach get merged into main spec
Jun 8, 2021
dontcallmedom
changed the title
Detect when Stage 3 ES proposals reach get merged into main spec
Detect when Stage 3+ ES proposals reach get merged into main spec
Jun 8, 2021
dontcallmedom
changed the title
Detect when Stage 3+ ES proposals reach get merged into main spec
Detect when Stage 3+ ES proposals get merged into main spec
Jun 8, 2021
Could there be stage 3 proposals that get dropped after all? On top of (or instead of?) looking at stage 4 proposals, it could make sense to compare the stage 3 list with the current list of TC39 proposals in browser-specs. |
tidoust
added a commit
that referenced
this issue
Mar 24, 2023
The proposal was renamed to Import Attributes, its URL updated, and more importantly the proposal was demoted to Stage 2 last month: tc39/proposals@faa00dc ... which provides a practical example for: #307 (comment)
tidoust
added a commit
that referenced
this issue
Mar 24, 2023
The proposal was renamed to Import Attributes, its URL updated, and more importantly the proposal was demoted to Stage 2 last month: tc39/proposals@faa00dc ... which provides a practical example for: #307 (comment)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now, our workflows determine when an ES spec reaches stage 3, but no signal is detected when a spec reaches stage 4 and thus should no longer be listed on its own in browser-specs.
The text was updated successfully, but these errors were encountered: