Skip to content

11.md

Latest commit

 

History

History
186 lines (146 loc) · 15.6 KB

11.md

File metadata and controls

186 lines (146 loc) · 15.6 KB

Ecma logo

Agenda for the 111th meeting of Ecma TC39

  • Host: Bloomberg
  • Dates and times:
    • 10:00 to 17:00 JST (Asia/Tokyo) on Tuesday 18 November 2025
    • 10:00 to 17:00 JST (Asia/Tokyo) on Wednesday 19 November 2025
    • 10:00 to 16:00 JST (Asia/Tokyo) on Thursday 20 November 2025
  • Location: Tokyo, Japan
  • Attendee information: https://github.com/tc39/Reflector/issues/564
  • Total duration of scheduled discussions: dynamically computed total of timeboxes on the agenda
gantt
  1 month before the meeting: milestone, 2025-10-18 10:00+0900, 1m
  Proposal advancement deadline: milestone, 2025-11-08 10:00+0900, 1m
  Schedule constraint deadline: milestone, 2025-11-15 10:00+0900, 1m
  Day 1 : day1, 2025-11-18 10:00+0900, 7h
  Day 2 : day2, 2025-11-19 10:00+0900, 7h
  Day 3 : day3, 2025-11-20 10:00+0900, 7h
  todayMarker stroke-width:5px,stroke:#0f0,opacity:0.5
Loading

For meeting times in your timezone, visit Temporal docs and run the code below in the devtools console.

Temporal.ZonedDateTime.from('2025-11-18T10:00[Asia/Tokyo]')
  .withTimeZone(Temporal.Now.timeZoneId())
  .toLocaleString();

Background:

Agenda topic rules

Deadline for advancement eligibility: November 8th 10:00 Asia/Tokyo

  • Note: this time is selected to be precisely 10 days prior to the start of the meeting
  1. Proposals not looking to advance may be added at any time; if after the deadline, please always use a pull request so that members are notified of changes. Note: an unmerged PR counts as “added” for the purposes of this requirement.
  2. Proposals seeking feedback at stage 0 must be added (and noted as such) prior to the deadline, or else delegates may object to advancement solely on the basis of missing the deadline.
    1. Such proposals should include supporting materials when possible.
  3. Proposals looking to advance to stage 1 must be added (and noted as such) prior to the deadline, or else delegates may object to advancement solely on the basis of missing the deadline.
    1. Such proposals must link to a proposal repository and they should link to supporting materials when possible.
  4. Proposals looking to advance to stages 2, 2.7, 3, or 4, as well as other normative changes to the standard or proposals in stage 3 or later looking to achieve consensus, must be added (and noted as such) along with links to the supporting materials prior to the deadline, or else delegates may withhold consensus for advancement solely on the basis of missing the deadline.
    1. If the supporting materials change substantially after the deadline, delegates may withhold consensus for advancement, based on the committee’s judgment.
    2. For urgent normative changes, the committee is expected to be more forgiving of a missed deadline, since there is generally less material to review than in a stage advancement.
    3. Proposals looking to advance to stage 4 must link to a pull request into the spec, since the process requires one.
  5. Proposal-based agenda items should be sorted primarily by stage (descending), secondarily by timebox (ascending), and finally by insertion date.

Supporting materials includes slides, a link to the proposal repository, a link to spec text, etc.; essentially, anything you are planning to present to the committee, or that would be useful for delegates to review.

Agenda key

When applicable, use these emoji as a prefix to the agenda item topic.

Emoji Meaning
❄️ hard schedule constraints apply to this agenda item (e.g. presenter)
🔒 schedule constraints apply to this agenda item
⌛️ late addition for stage advancement and/or schedule prioritization
🔁 continuation of a previous agenda item

Agenda items

  1. Opening, welcome and roll call (Chair, 10m)

    1. Opening of the meeting
    2. TC39 follows its Code of Conduct
    3. Introduction of attendees
    4. Host facilities, local logistics
    5. Quick recap of meeting IPR policy
    6. Overview of communication tools
    7. Reminder to review Github Delegate teams (Jordan Harband)
    8. TC39 stenography support and legal disclaimer

  2. Find volunteers for note taking

  3. Adoption of the agenda

  4. Approval of the minutes from last meeting

  5. Next meeting host and logistics

  6. Secretary's Report (15m, Aki Rose Braun) (slides)

  7. Project Editors’ Reports

    1. ECMA262 Status Updates (slides) (5m)
    2. ECMA402 Status Updates (5m)
    3. ECMA404 Status Updates (1m)
    4. Test262 Status Updates (5m)

  8. Task Group Reports

    1. TG3: Security (1m)
    2. TG4: Source Maps (5m)
    3. TG5: Experiments in Programming Language Standardization (5m)

  9. Updates from the CoC Committee (1m)

  10. Web compatibility issues / Needs Consensus PRs

    timebox topic presenter
    10m Normative: In PluralRules, set compactDisplay only if notation is "compact" ( slides ) Frank Yung-Fong Tang
    15m Normative: make re-exporting a namespace object in 2 steps behave like 1 step / (issue, slides) Nicolò Ribaudo or Kevin Gibbons

  11. Overflow from previous meeting

    timebox topic presenter

  12. Short (≤30m) Timeboxed Discussions

    timebox topic presenter
    20m Module-declarations-like proposals in other areas of the web platform (low priority, push to next meeting if needed, slides) Nicolò Ribaudo

  13. Proposals

    stage timebox topic presenter
    3 12m Iterator Sequencing for Stage 4 (slides, PR) Michael Ficarra
    3 15m JSON.parse source text access for Stage 4 (PR) Richard Gibson
    3 30m Temporal status report and normative PR (slides) Philip Chimento
    3 30m Intl Locale Info API for Stage 4 (Slides) Frank Yung-Fong Tang
    2.7 20m Joint Iteration for Stage 3 (tests PR) (slides) Michael Ficarra
    2.7 60m Keep trailing zeros in Intl.NumberFormat and Intl.PluralRules update (slides, PR #10, issue #11, PR #12) Eemeli Aro
    2 30m export defer for Stage 2.7 (slides) Nicolò Ribaudo
    2 30m Intl Era Monthcode for Stage 3 slides Ben Allen
    2 30m async iterator helpers recap/update/polyfill Kevin Gibbons
    2 30m Error.prototype.stack accessor for stage 2.7 Jordan Harband
    1 30m await dictionary for Stage 2 or 2.7 (spec) Ashley Claymore
    1 30m Declarations in Conditionals for Stage 2 (spec) Devin Rousso
    1 30m Amount Stage 1 update (spec, slides) Ben Allen
    1 30m Object.propertyCount for Stage 2 Ruben Bridgewater
    1 45m Error.captureStackTrace for Stage 2 (Slides) Daniel Minor
    1 60m Concurrency Control Stage 1 updates (slides) Michael Ficarra
    1 60m Composites comparator choice (slides) Ashley Claymore
    0 20m Iterator Join for stage 1, 2, or 2.7 (spec, slides) Kevin Gibbons
    0 30m TypedArray Concatenation for Stage 1 (Slides) James Snell
    0 30m TypedArray Find Within for Stage 1 (Slides) James Snell
    0 30m Comparisons for stage 1 (slides) Jacob Smith
    0 30m Import Text for Stage 1, 2, or 2.7 (slides, spec, test262 PR) Eemeli Aro
    0 30m Intl Energy Units for Stage 1 Ben Allen
    0 30m Intl Unit Protocol for Stage 1 (slides) Shane F Carr
    0 30m Object.getNonIndexStringProperties for Stage 1 or 2 Ruben Bridgewater
    0 30m Class spread syntax for Stage 1 (slides) Lea Verou
    0 30m Class field introspection for Stage 1 (slides) Lea Verou

  14. Longer or open-ended discussions

    timebox topic presenter
    20m Decorators proposal status update? Jacob Smith
    45m Spec-defined or Implementation-defined limits? (slides) Shane F Carr
    30m WHATWG Stages (slides) Chengzhong Wu
    60m Class composition: Past, present, and future (slides) Lea Verou

  15. Overflow from timeboxed agenda items (in insertion order)

    topic presenter
  1. Other business
    1. Thank host
  2. Adjournment

Schedule constraints

Schedule constraints should be supplied here as soon as possible, and at least three days before the meeting begins so that the Chairs can take them into account when preparing the schedule.

Normal Constraints

  • Jacob Smith is only available during the last hour of days one and two.
  • Kevin Gibbons is only available before 16:00 JST (ideally 15:00) and would like to be present for the Concurrency Control item
  • Ideally class composition open discussion should come right before class spread and fields introspection proposals, as they are highly related.

Late-breaking Schedule Constraints

  • Ben Allen is only available on Thursday.