-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Final normative spec text plan #2628
Labels
Milestone
Comments
This comment was marked as outdated.
This comment was marked as outdated.
ptomato
added a commit
that referenced
this issue
May 26, 2024
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
ptomato
added a commit
that referenced
this issue
May 27, 2024
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
ptomato
added a commit
that referenced
this issue
May 27, 2024
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
Aditi-1400
pushed a commit
to Aditi-1400/proposal-temporal
that referenced
this issue
May 31, 2024
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: tc39#2628
Aditi-1400
pushed a commit
that referenced
this issue
May 31, 2024
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
ptomato
added a commit
that referenced
this issue
Jun 5, 2024
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 Co-Authored-By: Richard Gibson <richard.gibson@gmail.com>
ptomato
added a commit
that referenced
this issue
Jun 6, 2024
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 Co-Authored-By: Richard Gibson <richard.gibson@gmail.com>
5 tasks
ptomato
added a commit
that referenced
this issue
Jun 13, 2024
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 Co-Authored-By: Richard Gibson <richard.gibson@gmail.com>
ptomato
added a commit
that referenced
this issue
Jun 13, 2024
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 Co-Authored-By: Richard Gibson <richard.gibson@gmail.com>
ptomato
added a commit
that referenced
this issue
Jul 4, 2024
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 Co-Authored-By: Richard Gibson <richard.gibson@gmail.com>
ptomato
added a commit
that referenced
this issue
Jul 11, 2024
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 Co-Authored-By: Richard Gibson <richard.gibson@gmail.com>
ptomato
added a commit
that referenced
this issue
Jul 20, 2024
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 Co-Authored-By: Richard Gibson <richard.gibson@gmail.com>
ptomato
added a commit
that referenced
this issue
Jul 20, 2024
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 Co-Authored-By: Richard Gibson <richard.gibson@gmail.com>
This is all done. Unless new bugs are found by implementors, there are no more normative changes planned. Follow #2950 for the roadmap of editorial changes. |
Congratulations and many thanks @ptomato ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 - consensus 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: