Skip to content
This repository was archived by the owner on Jan 26, 2022. It is now read-only.

Advance to stage 4 #11

Closed
mathiasbynens opened this issue Sep 27, 2018 · 2 comments
Closed

Advance to stage 4 #11

mathiasbynens opened this issue Sep 27, 2018 · 2 comments
Labels

Comments

@mathiasbynens
Copy link
Member

mathiasbynens commented Sep 27, 2018

Criteria taken from the TC39 process document minus those from previous stages:

tc39/test262#2112
tc39/test262#2124

  • Two compatible implementations which pass the acceptance tests

https://github.com/tc39/proposal-promise-allSettled#implementations

Bug tickets to track:

  • Significant in-the-field experience with shipping implementations, such as that provided by two independent VMs

https://github.com/tc39/proposal-promise-allSettled#implementations

tc39/ecma262#1583

  • All ECMAScript editors have signed off on the pull request

TODO

@ljharb
Copy link
Member

ljharb commented Sep 27, 2018

Blocked by #10

@mathiasbynens
Copy link
Member Author

This proposal achieved stage 4 at today’s TC39 meeting, pending tc39/ecma262#1583 being formally approved by the editor group and merged. I’m closing this issue and this repository since there’s nothing left to be done here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants