Skip to content
This repository has been archived by the owner. It is now read-only.

Advance to stage 3 #12

domenic opened this issue Jul 23, 2014 · 2 comments

Advance to stage 3 #12

domenic opened this issue Jul 23, 2014 · 2 comments


Copy link

@domenic domenic commented Jul 23, 2014


  • Those from stage 2

This is #10

  • Complete spec text

Pending design problems being resolved.

  • Designated reviewers have signed off on the current spec text.

Not sure who these will be?

  • The ECMAScript editor has signed off on the current spec text.

Tracked by #11

Implementation types expected during this stage:

  • Spec compliant

Tracked as #7, #8, #9, #27, #28. Ideally this should be done at the same time as the experimental ones (i.e. there should be no experimental ones, just ones that follow the finalized spec text).


  • Get TC39 to agree that we have advanced to stage 3, after meeting all the above requirements.
@domenic domenic mentioned this issue Jul 23, 2014
6 of 6 tasks complete
@domenic domenic added the process label Jul 23, 2014
Copy link

@ljharb ljharb commented May 27, 2015

Do non-browsers count as implementations? If so, includes which is one, and I believe babel may have one as well.

Copy link
Member Author

@domenic domenic commented May 27, 2015


@domenic domenic closed this Jul 28, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.