4 ms·
Why is taking so long for 1.0.1 to be released? On a side note, they clearly jumped the version number to "1.0" way too soon. It is nowhere near production-wo
by dstein 16y ago
Why is taking so long for 1.0.1 to be released?
On a side note, they clearly jumped the version number to "1.0" way too soon. It is nowhere near production-worthy software (which is implied by a 1.0 release).
- jchrisa 16y agoApache procedure requires a 72-hour vote window, which will be closing soon. As far as 1.0 being production ready, yes the bug is unfortunate, but the fix is 29 characters long. Aside from this unfortunate line of code, I'm 100% certain that CouchDB is production ready. Lots of sites have been running it in production for years without issue. An incomplete list of happy users is here: http://www.couch.io/case-studies http://www.couch.io/case-studies Here's the bug-fix, to give you an idea: http://github.com/apache/couchdb/commit/1423d6f0a593e16817068d2b5dc5463a21bc0ea4#L0L704 http://github.com/apache/couchdb/commit/1423d6f0a593e1681706...
- carterschonwald 16y agoI have to say I also really like the fact that recovery is possible to begin with! Are there any other extant db/data store tools which enjoy the same append only awesomeness (as i understand, append only writes are the only reason this recovery is possible, plus in principle allows pretty awesomely fast writes). <Now goes back to coding in a functional language, which tends to enjoy append only writing when theres no state>
- mey 16y agoIt is a catch 22. Not many things can be said to be production ready until proven over time. There are many people using CouchDB in production today, some of the bigger people are the BBC and Ubuntu. This issue and response is a step along the way of proving it's production usability.