Repository navigation
Path to Stage 4! #175
Description
Stage 4
- committee approval
- two implementations
- Firefox
- Chrome
- Safari
- node
- babel
- TypeScript
- significant in-the-field experience
- ecma262 PR approved
Stage 3
- prepare ecma262 PR
- merge test262 tests
- write test262 tests
Stage 2.7
- Resolve open questions:
- committee approval
- spec editor signoff
- spec reviewer signoff
- receive implementor feedback
Stage 2
- committee approval
- spec reviewers selected
- spec text written
Stage 1
- committee approval
Activity
IceSentry commentedon Apr 21, 2021
ljharb commentedon Apr 21, 2021
NagayamaToshiaki commentedon Apr 14, 2025
What makes this spec to prevent committee approval?
ljharb commentedon Apr 14, 2025
@NagayamaToshiaki the champions need to continue the design work we've been working on for a long time, and present to the committee to ask for advancement, before there's anything for the committee to approve.
controversial commentedon Sep 30, 2025
Are there any additional champion meetings planned/scheduled to keep trying to push the proposal forward? Based on meeting notes issues it seems like there hasn’t been any design movement in over a year.
ljharb commentedon Sep 30, 2025
The next step is for the champion group to prepare a plenary presentation, which our lives have been too busy to prepare thus far.
controversial commentedon Sep 30, 2025
I’m assuming there isn’t, but please let us know if there’s any way the community outside of the champions group can help to move things forward.
I know there’s a lot of excitement about this proposal among developers!
michaelficarra commentedon Oct 21, 2025
mbrowne commentedon Jan 3, 2026
Just curious if there has been any progress since the last post
ljharb commentedon Jan 4, 2026
If there were, it’d be posted here.
senocular commentedon Jan 4, 2026