List view
Purpose: Indicate that the addition is ready for inclusion in the formal ECMAScript standard Entrance criteria: - Test262 acceptance tests have been written for mainline usage scenarios, and merged - Two compatible implementations which pass the acceptance tests - Significant in-the-field experience with shipping implementations, such as that provided by two independent VMs - A pull request has been sent to tc39/ecma262 with the integrated spec text - All ECMAScript editors have signed off on the pull request See https://tc39.es/process-document/
No due datePurpose: Indicate that further refinement will require feedback from implementations and users Entrance criteria: - Complete spec text - Designated reviewers have signed off on the current spec text - All ECMAScript editors have signed off on the current spec text See https://tc39.es/process-document/
No due datePurpose: Precisely describe the syntax and semantics using formal spec language Entrance criterion: Initial spec text. Draft: all major semantics, syntax and API are covered, but TODOs, placeholders and editorial issues are expected See https://tc39.es/process-document/
No due datePurpose: - Make the case for the addition - Describe the shape of the solution - Identify potential challenges Entrance criteria: - Identified “champion” who will advance the addition - Prose outlining the problem or need and the general shape of a solution - Illustrative examples of usage - High-level API - Discussion of key algorithms, abstractions and semantics - Identification of potential “cross-cutting” concerns and implementation challenges/complexity - A publicly available repository for the proposal that captures the above requirements See https://tc39.es/process-document/
No due date•0/1 issues closed