The TC39 Process Back
| Stage | Purpose | Entrance Criteria | Acceptance Signifies | Spec Quality | Post-Acceptance Changes Expected | Implementation Types Expected* | |
|---|---|---|---|---|---|---|---|
| 0 | Strawperson | Allow input into the specification | None | N/A | N/A | N/A | N/A |
| 1 | Proposal |
|
|
The committee expects to devote time to examining the problem space, solutions and cross-cutting concerns | None | Major | Polyfills / demos |
| 2 | Draft | Precisely describe the syntax and semantics using formal spec language |
|
The committee expects the feature to be developed and eventually included in the standard | Draft: all major semantics, syntax and API are covered, but TODOs, placeholders and editorial issues are expected | Incremental | Experimental |
| 3 | Candidate | Indicate that further refinement will require feedback from implementations and users |
|
The solution is complete and no further work is possible without implementation experience, significant usage and external feedback. | Complete: all semantics, syntax and API are completed described | Limited: only those deemed critical based on implementation experience | Spec compliant |
| 4 | Finished | Indicate that the addition is ready for inclusion in the formal ECMAScript standard |
|
The addition will be included in the soonest practical standard revision | Final: All changes as a result of implementation experience are integrated | None | Shipping |
* This column does not indicate a requirement for advancement, but simply a general expectation.
As the plugin is integrated with a code management system like GitLab or GitHub, you may have to auth with your account before leaving comments around this article.
Notice: This plugin has used Cookie to store your token with an expiration.