Roadmap towards 2.7

[mgaudet]

Here's a rough outline (which I will update as I firm things up) of next steps we'll need to go through to get to Stage 2.7

• Investigate, possibly with telemetry, using a second argument to the resolve function to allow exposing the "safe resolve" behaviour to user code
• Firm up specification text, particularly around tick counts and ensuring we have the behaviour specified we actually want. Consider deploying the specification outline that Mark Miller suggested in plenary (create a new internal promise, resolve the outer promise with the internal promise, then pass the internal promise's resolve function + the value to the deferred job)
  • Editor review: Jordan Harband and Justin Ridgewell volunteered to review.
• On a personal note, I'd like to try browsing around with a SafeResolve enabled browser for a while to get a feeling for potential webcompat issues.
• On the web-compat front, I'd like to investigate the possibility of issuing a console note if we re-order execution as a result of this proposal
• I should open another issue about potentially bringing a normative PR to consume this as part of spec internal algorithms (feedback from Kevin Gibbons)