Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upes 2017, the seventh edition #483
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
rossberg
Mar 18, 2016
Member
es6 = es2015
es7 = es2016
es8 = es2017
The first has been released, the second is feature-frozen, we are now working on the third. So everything seems correct (except the year in the scope, as you point out).
|
es6 = es2015 The first has been released, the second is feature-frozen, we are now working on the third. So everything seems correct (except the year in the scope, as you point out). |
bterlson
closed this
in
b3faee8
Mar 18, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
bterlson
Mar 18, 2016
Member
Edition numbers are confusing but they continue to exist along side the years. Sadly they are off by one from what you might expect.
I fixed sec-scope.
@raulsebastianmihaila you can see the rendering of the ES2016 draft here: https://tc39.github.io/ecma262/2016. It's built from the es-2016 branch.
|
Edition numbers are confusing but they continue to exist along side the years. Sadly they are off by one from what you might expect. I fixed sec-scope. @raulsebastianmihaila you can see the rendering of the ES2016 draft here: https://tc39.github.io/ecma262/2016. It's built from the es-2016 branch. |
raulsebastianmihaila commentedMar 18, 2016
I see than the title in the draft was changed to Ecmascript 2017. Now the draft says that 'It is the eighth edition'. It should be the seventh, because es6 was the sixth, right? Also the scope of the document should be updated (https://tc39.github.io/ecma262/#sec-scope). It still has 2016 instead of 2017.
Does this mean that there will be no standard released this year?