| 18:42 | <littledan> | What is our current process with respect to web platform integration and the stage process? Do we need full web integration by stage 2.7, or Stage 3? Asking because AsyncContext seems almost ready for advancement to 2.7, with the one missing piece being full DOM integration (specifically, understanding which AsyncContext snapshot various callbacks are called in). |
| 18:44 | <littledan> | (significant progress has been made, but it's not at a complete conclusion that everyone can sign off on) |
| 18:51 | <littledan> | I think it'd make sense to be OK waiting for Stage 3 for fully final web integration [that is: full web integration is a requirement to get into Stage 3, and so it can still be under development during 2.7]; we as TC39 can conclude on the design and get to 2.7 (so the design has consensus from our perspective and we won't make non-implementation-feedback-driven changes), but it might need to be demoted to Stage 2 if a "fatal flaw" is discovered during attempts at web integration. The existence of Stage 3 means that people won't get the wrong idea that it's too stable too early. (We have long asked for web integration as a requirement to enter Stage 3, and regretted it when we didn't wait for that; it's not a requirement in the process document, but various committee members hold it up as a requirement on a case-by-case basis) |
| 21:51 | <ljharb> | 2.7 seems like a reasonable place to figure out web integration issues prior to signaling stability (earlier's better, obv) |