Was 0.6.7-0.6.9 skipped? There was a release candidate for version 0.6.7
The big change with this version is the oplog tailing instead of the poll and diff which has dramatic performance improvements over the previous version. More details at the wiki: https://github.com/meteor/meteor/wiki/Oplog-Observe-Driver
We are rationing version numbers before 1.0, since we have multiple major projects that're slated to land in between now and then, including Meteor UI and integrated package management. (Though as Node has shown, an 0.10 wouldn't be the end of the world.) But we decided that oplog tailing is a big enough deal that we should bump the middle number.
Yeah, we have several big projects in flight, and we're shipping them in the order that they're ready.
We push them out first as prereleases (which you can run by passing a --release flag to meteor, and it will automatically download and install everything) and announce them to meteor-core and see what people think. In this case both oplog tailing and Meteor UI were out as prereleases, but there was more feedback and more feature requests for Meteor UI, so oplog tailing ended up winning the race.
Comments
Was 0.6.7-0.6.9 skipped? There was a release candidate for version 0.6.7
The big change with this version is the oplog tailing instead of the poll and diff which has dramatic performance improvements over the previous version. More details at the wiki: https://github.com/meteor/meteor/wiki/Oplog-Observe-Driver
We are rationing version numbers before 1.0, since we have multiple major projects that're slated to land in between now and then, including Meteor UI and integrated package management. (Though as Node has shown, an 0.10 wouldn't be the end of the world.) But we decided that oplog tailing is a big enough deal that we should bump the middle number.
About the version number: https://github.com/meteor/meteor/commit/8bd400e56065b0f2d61e...
I would have expected Meteor UI to be in 0.7, but that not a big deal and that will probably be in the next version.
Yeah, we have several big projects in flight, and we're shipping them in the order that they're ready.
We push them out first as prereleases (which you can run by passing a --release flag to meteor, and it will automatically download and install everything) and announce them to meteor-core and see what people think. In this case both oplog tailing and Meteor UI were out as prereleases, but there was more feedback and more feature requests for Meteor UI, so oplog tailing ended up winning the race.