News for hackers. Stuff that matters.
Re:RethinkDB 1.7: hot backup, atomic set/get, 10x insert per... by throwit1979 on Wednesday July 03, 2013 @02:45PM (#5986665)
Is there a target milestone for a production-ready release of RethinkDB? Is it 1.8 or 1.9?

1.0 is supposed to mean production-ready. Are you suggesting this should be a 0.7 release?

Re:RethinkDB 1.7: hot backup, atomic set/get, 10x insert per... by dragonwriter on Wednesday July 03, 2013 @02:51PM (#5986697)
Under semver (which isn't the only versioning scheme, but certainly among the more common of the ones that have a firm definition of what 1.0 means), it means "stable API", which doesn't necessarily mean "production ready".

Version numbers don't have on single universally accepted set of defined semantics.

Re:RethinkDB 1.7: hot backup, atomic set/get, 10x insert per... by hexedpackets on Wednesday July 03, 2013 @02:48PM (#5986684)
If I remember correctly, the RethinkDB team opted to match their in-house version numbers with public releases. So the 1.x releases would be more comparable to 0.x releases for other projects, and 2.0 would be considered stable and production ready.
Re:RethinkDB 1.7: hot backup, atomic set/get, 10x insert per... by coffeemug on Wednesday July 03, 2013 @02:58PM (#5986753)
slava @ rethink -- this is exactly right. Sorry for confusion.
Re:RethinkDB 1.7: hot backup, atomic set/get, 10x insert per... by egeozcan on Thursday July 04, 2013 @03:39AM (#5989589)
This is similar to node.js versioning, I think.