Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Final normative spec text plan #2628

Open
65 of 75 tasks
ptomato opened this issue Jul 13, 2023 · 1 comment
Open
65 of 75 tasks

Final normative spec text plan #2628

ptomato opened this issue Jul 13, 2023 · 1 comment
Labels
meta
Milestone
Stage "3.5"

Comments

@ptomato
Copy link
Collaborator

ptomato commented Jul 13, 2023 •
edited

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:

Then, address the lower-priority editorial issues listed in the milestone https://github.com/tc39/proposal-temporal/milestone/11
@ptomato ptomato added this to the Stage "3.5" milestone Jul 13, 2023
@ptomato ptomato pinned this issue Jul 13, 2023
@ptomato ptomato added the meta label Jul 13, 2023
@justingrant

This comment was marked as outdated.

Sign in to view
@ptomato ptomato mentioned this issue Aug 9, 2023
Closed
@ptomato ptomato mentioned this issue Oct 27, 2023
Closed
@ghiscoding ghiscoding mentioned this issue Nov 13, 2023
Closed
5 tasks
ptomato added a commit that referenced this issue May 26, 2024
@ptomato
Normative: Remove TimeZone.p.equals
261df9a 
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
meta
Projects
None yet
Milestone
Stage "3.5"
Development

No branches or pull requests
2 participants
@justingrant @ptomato