News for hackers. Stuff that matters.
Re:io.js 1.4 released – featuring debuggable ES6 promises by colinramsay on Wednesday February 25, 2015 @03:09PM (#9109211)
Hang on - 1.3 was only about three days ago! Rapid progress is obviously fantastic, but is there a reason why these two releases weren't bundled together?

Edit: five days ago, but my point stands.

Re:io.js 1.4 released – featuring debuggable ES6 promises by inglor on Wednesday February 25, 2015 @03:14PM (#9109242)
Great question. It started off as 1.3.x but ended up being 1.4 for semver issues. There was discussion[1] about this. In short - it was named 1.4 because of how NPM updated and because of the big features landing.

[1] https://github.com/iojs/io.js/issues/932

Re:io.js 1.4 released – featuring debuggable ES6 promises by colinramsay on Wednesday February 25, 2015 @03:19PM (#9109269)
So issues beyond the control of io.js then? Makes more sense, just unfortunate I suppose.
Re:io.js 1.4 released – featuring debuggable ES6 promises by shouldbeworking on Wednesday February 25, 2015 @03:37PM (#9109372)
Not really unfortunate. Unlike with money, inflation of version numbers doesn't cause that much trouble. It just takes some getting used to. I've gotten used to the high version numbers in Chrome and Firefox, and I'm sure I'll get used to them in projects that use semver the right way as well.
Re:io.js 1.4 released – featuring debuggable ES6 promises by Whitespace on Wednesday February 25, 2015 @03:13PM (#9109230)
Probably due to V8 upgrade which contains an embargoed fix. These are usually critical bugs that remain undisclosed until major users (read as: large companies) have patched their systems.