You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of 2023-07-12, we have resolved all known discussions that might result in normative changes, and all of the normative changes have been presented to TC39 and received consensus. This issue is a checklist and plan for merging those normative PRs into the spec text, so that observers can see the status at a glance.
(Updated at later dates to include new normative changes to be presented to TC39 in November 2023 and February 2024)
After completing this checklist, barring fixes for bugs found during implementation, the spec should be in its final normative form, representing exactly what needs to be implemented.
The champions' plan of record after that point is to quickly address two open editorial issues that affect the ISO 8601 grammar, since V8 has let us know that the grammar changes can be disruptive even if they are only editorial ones:
The whole Temporal.TimeZone is going to be removed in the following
commit, but since this method is being replaced with an idiom that needs
documentation, I'm removing it in a separate commit for ease of review.
See: #2628
The whole Temporal.TimeZone is going to be removed in the following
commit, but since this method is being replaced with an idiom that needs
documentation, I'm removing it in a separate commit for ease of review.
See: #2628
The whole Temporal.TimeZone is going to be removed in the following
commit, but since this method is being replaced with an idiom that needs
documentation, I'm removing it in a separate commit for ease of review.
See: #2628
As of 2023-07-12, we have resolved all known discussions that might result in normative changes, and all of the normative changes have been presented to TC39 and received consensus. This issue is a checklist and plan for merging those normative PRs into the spec text, so that observers can see the status at a glance.
(Updated at later dates to include new normative changes to be presented to TC39 in November 2023 and February 2024)
@justingrant@gibson042)still in draft statusneeds review from a test262 maintainer (action for @ptomato)editorial/code review from championsa quick look at the recently added bugfixweekOfYear
/yearOfWeek
is not clearly specified for non-ISO calendars #2744 - consensus in February 2024Duration::round
with ZonedDateTime relativeTo conflicts withZonedDateTime::until
results #2742 - consensus in February 2024PlainDateTime::until/since
incorrect results near month boundaries when time-diff has opposite sign #2820 - to be presented in June 2024After completing this checklist, barring fixes for bugs found during implementation, the spec should be in its final normative form, representing exactly what needs to be implemented.
The champions' plan of record after that point is to quickly address two open editorial issues that affect the ISO 8601 grammar, since V8 has let us know that the grammar changes can be disruptive even if they are only editorial ones:
Then, address the lower-priority editorial issues listed in the milestone https://github.com/tc39/proposal-temporal/milestone/11
The text was updated successfully, but these errors were encountered: