search

tc39 / ecma262

Status, process, and documents for ECMA-262
https://tc39.es/ecma262/
Other
15.03k stars 1.28k forks source link

Make the last digit of the ECMAScript edition number consistent with the last digit of the publishing year #1457

Closed ExE-Boss closed 4 years ago

ExE-Boss commented 5 years ago

Right now, the following mapping applies to ES6 – ES9:

Version Year
ES6 ES2015
ES7 ES2016
ES8 ES2017
ES9 ES2018

This is somewhat confusing because the ECMAScript edition number doesn’t directly correspond to the publising year.

I propose to make it so that the publishing of ES10 gets delayed by half a year so that it would be possible to call it ES2020 and then publishing ES11 a year and a half after ES10, with ES12 and later being published a year apart, eg.:

Version Proposed offset from current schedule (in years)
ES9 (ES2018) 0
ES10 (ES2019.5 ≐ ES2020) +0.5
ES11 (ES2021) +1
ES12 (ES2022) +1
devsnek commented 5 years ago

just only refer to editions after es5 by year

ljharb commented 5 years ago

Such an offset would make things more confusing imo, since “edition + 2009” wouldn’t give you the ES6+ year anymore.

ExE-Boss commented 5 years ago

But edition + 2010 is easier to calculate in the head and feels simpler.

ljharb commented 5 years ago

The simplest of all, though, is https://github.com/tc39/ecma262/issues/1457#issuecomment-467897891

claudepache commented 5 years ago

If some correction is to be done, let’s do it frankly and let’s skip the 2009 next version numbers (ES version 2019 would succeed to ES version 9). Any half-measure will just increase the confusion.

ljharb commented 4 years ago

Thanks for your suggestion, but I doubt we'll want to skip edition numbers again. (see #1489 as well)