3 ms·
Correct. Major versions make more sense when you create a release based on the content. V8 is creating its releases based on time (~6 week cadence). So a 'majo
by natorion 11y ago
Correct.
Major versions make more sense when you create a release based on the content. V8 is creating its releases based on time (~6 week cadence). So a 'major' version is nothing special anymore. In 4.9 we greatly expanded our ES2015 support which was huge but only incremented the minor version because of the same reason.
Disclaimer: I work on the V8 team.
- ufmace 11y agoIncidentally, I found a nice list of upcoming Chrome/V8 features and status here: https://www.chromestatus.com/features https://www.chromestatus.com/features
- bryanlarsen 11y agoIf you're going to use meaningless version numbers, then it would be better if you used something that didn't imply otherwise. Chrome 50 carries exactly the right connotation, IMO.
- STRML 11y agoWhy not date-based version numbers, then, or as bryanlarsen stated, something obviously meaningless, like the Chrome/FF numbers? Edit: By the way, sorry to derail the conversation. You guys are doing great work! I'm always excited about V8 updates because they generally mean great perf/feature improvements to both the most popular browsers and my runtime of choice, NodeJS.
- natorion 11y agoThe reason is simply 'legacy'. Maybe we will change our version numbers to something without major.minor versions.
- TheAceOfHearts 11y agoMaybe this is a stupid question... But why not straight up copy Chrome and jump up to v50 instead of v5.0?