Stage 3 proposals which are not ready to ship #123
Conversation
|
btw can you remove the usernames from the commit message? otherwise any time the repo is forked we'll all get a notification ping |
The proposals repository should document which Stage 3 proposals are not ready to ship; this text documents how that would work. Follow-up on discussion in tc39/Reflector#451. Thanks to ljharb syg and ptomato for helpful feedback in this text.
littledan
force-pushed
the
ready-to-ship
branch
from
1b301ee
to
b3781e5
Compare
|
Good point, sorry about that, fixed. |
|
In the TC39 meeting, @codehag suggested that we change "not ready to ship" with "requires implementer coordination", to avoid the implication that features without the tag are ready to ship (where in reality engines make case-by-case decisions on Stage 3 proposals). Honestly I'm not really excited about the subsequent wording avoiding shipping, because it makes it somewhat unclear what we're talking about (the goal remains, avoiding shipping things too soon--what else are we coordinating on?). But anyway I'd be fine with landing this in its new state, if people review it. |
|
Closing in favor of #130 |
The proposals repository should document which Stage 3 proposals are not ready to ship; this text documents how that would work. Follow-up on discussion in https://github.com/tc39/Reflector/issues/451. Thanks to @ljharb @syg and @ptomato for helpful feedback in this text.