Path to Stage 4!

[gibson042]

Stage 4

• committee approval
• two implementations
  • JavaScriptCore
  • SpiderMonkey
  • XS
  • V8
• significant in-the-field experience
• ecma262 PR approved
• prepare ecma262 PR

Stage 3

• committee approval
• merge test262 tests
• write test262 tests
• receive implementer feedback

Stage 2.7

• committee approval
• spec editor signoff (@tc39/ecma262-editors)
  • Shu-yu Guo (@syg)
  • Kevin Gibbons (@bakkot)
  • Michael Ficarra (@michaelficarra)
• spec reviewer signoff
  • Shu-yu Guo (@syg)
  • Waldemar Horwat (@waldemarhorwat)
  • Jordan Harband (@ljharb) (see Spec Review #27 (comment))
• resolve all normative issues
  • Normative issues Should transferToImmutable support a newByteLength argument? #15 .immutable or .mutable? #10 add .sliceToImmutable? #9 resolved and closed
  • Normative issue Order of operations, when to throw or silently do nothing? #16 purposely left open for more implementor feedback
  • Open issue Applicability to WebGPU buffer mapping #25 is not normative
  • Open issue Mention proposed integration with "structured cloning" #19 is not normative
  • Open issue Zero-copy operations on the web #18 is not normative
  • Open issue Update shim according to issue resolutions #26 is not normative
• receive implementer feedback
  • XS implementation good. Does not suggest any changes.
  • shim implementation and practical use is necessarily incomplete, but does not suggest any changes.
  • others...

Stage 2

• committee approval
• spec reviewers selected
  • Shu-yu Guo (@syg)
  • Waldemar Horwat (@waldemarhorwat)
  • Jordan Harband (@ljharb)
• spec text written

Stage 1

• committee approval

[erights]

@syg @waldemarhorwat @ljharb , with the normative issues resolved aside from the purposely postponed #16 (see checklist above), This seems ready for spec review. I have placed this item on the agenda to go for 2.7, so would like to be as prepared as possible.

For the "spec editor signoff", who are the spec editors?

[syg]

You can tag @tc39/ecma262-editors. Currently the editors are myself, @bakkot, and @michaelficarra.

[erights]

@syg @waldemarhorwat @bakkot @michaelficarra ping.

@syg @bakkot please see @gibson042 responses to your stated concerns. What remaining concerns do you have that should block 2.7 until resolved?

@waldemarhorwat @michaelficarra I'd love to see your feedback before asking for stage 2.7.

Thanks!