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.

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

Dates of feature freeze for each version of specification #7

Closed
chicoxyzzy opened this issue Jul 17, 2016 · 6 comments
Closed

Dates of feature freeze for each version of specification #7

chicoxyzzy opened this issue Jul 17, 2016 · 6 comments

Comments

@chicoxyzzy
Copy link
Member

Are there any dates of feature freeze? It'll be helpful to add this info to Process Document.

All I found is that

TC39 may submit for approval to the Ecma General Assembly a new Edition of the ECMAScript language in March and September of every year. Additions which have been accepted by the committee as “finished” (stage 4) may be included in a new Edition.

But it's not clear what's happening on March and on September.

@allenwb
Copy link
Member

allenwb commented Jul 18, 2016

@ecmageneva
Copy link

Well,
this means that anything that is finished by TC39 can go twice a year for Ecma General Assembly (which are always in June and in December) approval. In practice so far TC39 used the March TC39 approval and the following June GA approval. Basically on the specs that were approved by TC39 in March no further work is done, but work on anything else which is for later TC39 and GA approval work can be processed.
Kind regards,
Istvan

@bterlson
Copy link
Member

bterlson commented Jul 18, 2016

I have updated the process document under the Spec Revisions and Scheduling heading. Please let me know any thoughts (or just submit a PR to fix it).

@chicoxyzzy
Copy link
Member Author

chicoxyzzy commented Nov 1, 2016

Just to clarify, January meeting is a last chance for stage 3 proposals to be promoted to stage 4 and get into ES2017 right?

@bterlson
Copy link
Member

bterlson commented Nov 1, 2016

@chicoxyzzy Correct, although November would be better for huge features...

chicoxyzzy added a commit to chicoxyzzy/process-document that referenced this issue Jan 30, 2017
@ctcpip
Copy link
Member

ctcpip commented Feb 9, 2024

I believe we have clarity on this these days, with approval of the yearly standards. It's also not of much consequence, as ECMA-262 and ECMA-402 are living standards.

@ctcpip ctcpip closed this as completed Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants