On Aug 11, 2010, at 4:49 PM, Randall Leeds wrote: > 0.11.2 is the latest release in the 0.11.x series. > It will be maintained with bug fixes until 1.1 comes out (and possibly > beyond, depending on community need). > No version of the 0.11.x branch ever suffered data loss. > See the changelog for details about what was fixed. > > 1.0.1 will be the next release in the 1.0.x series. It address the > data loss problem mentioned in the notice. > The 1.0.0_2 in the filename for couch.io's ubuntu package along with > the message there about the bug signifies they cut a version of 1.0.0 > with the fix from 1.0.1. > Therefore, I suspect 1.0.1 and couch.io's 1.0.0_2 are pretty much > equivalent. The latter is not tagged 1.0.1 because it is not an > official apache release, but prepared by the couch.io people. > The project official 1.0.1 release artifacts are being voted on right > now, and should be out this week. > > So, feel free to use the package from couch.io. > It is essentially what will soon be officially released at 1.0.1. >
Almost -- I think all we did on the Couchio one was set the default configuration to delayed_commits = false > Cheers, > Randall > > On Wed, Aug 11, 2010 at 16:10, Garret Heaton <[email protected]> wrote: >> Hi, >> >> I'm currently running 0.10.1 and am looking to upgrade to the latest stable >> build. The notice on the downloads page ( >> http://couchdb.apache.org/downloads.html) says to wait for 1.0.1, but I see >> that 0.11.2 came out today. Are they equivalent? Also, the Ubuntu download >> links on couch.io (http://www.couch.io/get#ubuntu) use the version number >> "1.0.0_2" in their filenames. Is this the same as 0.11.2? Are these builds >> updated to avoid the issue 1.0.0 had? >> >> What's the latest stable version I should be using? >> >> On another note, I tried using the 0.11.2 build and am now getting this >> error when starting couchdb: http://gist.github.com/519916. Any hints? I >> have a really difficult time getting any useful information out of these >> Erlang stack traces. >> >> Thanks! >> >> - Garret >>
