- Whether if it is ok to release 1.0.0 with V8 3.31.74 minus ES6 Classes and Object Literals Extensions, considering that the initial version of io.js will be "beta" quality and probably the stable version will coincide with the stable release of V8 3.31 (~6 weeks), which will have these features reinstated.
- How to handle V8 updates with semver so that if the same issue arised with a different timing it could mean a bump to 2.0.0.
- Community suggestions:
* Different version naming (e.g. 1.x+v8beta, 1.x+v8dev, 1.x+v8canary)
* Avoid BC by moving from tip-of-stable-Chrome-branch to the next tip-of-stable-Chrome-branch (~6 weeks release cycle)
Rod: prepared a proposed new LICENSE file, needed for release, adds a new license block for io.js at the top, shifts the Joyent copyright block down but still acknowledges their claim on inherited work. https://github.com/nodejs/io.js/pull/294
Rod: this is about V8 version matching and V8 version stability. We’re going live with 3.31.
Discussion with the V8 team suggests that 3.31 is probably not appropriate because of stability concerns. We have already had to disable class support because the V8 team announced their intention to disable it in the next release anyway.
Group agreed to stick with 3.31, too late to do otherwise. Come up with a more solid stability policy later.
- discussed process.versions.iojs property, https://github.com/nodejs/io.js/issues/269 - group agreed to do nothing on this. Rod to find discussion or create issue to have discussion on this.