Stage 3 requirements

[eemeli]

The entrance criteria for Stage 3 include:

• TC39 Process

  • The feature has sufficient testing
  • ... and appropriate pre-implementation experience.

• ECMA-402 Stage 3 Requirements

  • The proposal champion must demonstrate Payload Mitigation.
    • This proposal does not include any requirements for additional payload.
  • There should be a new request for W3C i18n Review opened at least 3 weeks prior to the TG2 meeting at which the proposal is seeking approval for Stage 3.
    • ECMA-402 Keep trailing zeros in Intl.NumberFormat and Intl.PluralRules 2025-09-24 > 2024-10-24 w3c/i18n-request#280

[eemeli]

The first opportunity for stage advancement will be at the next TC39 meeting, 18-20 November. The preceding TG2 meeting will be on 6 November, and so the deadline for requesting a W3C i18n review is 16 October.

The W3C i18n review in turn requires doing an initial self-review, which in this case means affirming that none of the checklist items apply here, as the proposal as a whole is a relatively small bugfix to an existing spec.

We don't (yet?) have an i18n-tracker label available here, so we'll need to sort out how that ought to work.

[eemeli]

I've submitted tc39/test262#4608 to add tests, and I've patched a fork of FormatJS to test the spec changes; with the changes proposed in #10, the tests pass.

Separately from that, the W3C i18n review has been completed with no issues found.