I will gladly test for you guys once you have something :). On Nov 21, 2013, at 10:52 AM, Robert Newson <[email protected]> wrote:
> Hi, > > There has been a protracted lull in the bigcouch merger work but we're > doing some more at couchhack in December and then a whole lot more in > Q1, hopefully to completion. > > We're not yet sure what migration will look like. At worse, it will be > replication based but we're mindful to do better. > > 0.4 is stable enough but note that it's 2+ years old from the author's > (Cloudant's) point of view and is no longer under active development > or maintenance. > > For clarity, the merge is emphatically not the bigcouch code base but, > rather, the code that Cloudant runs in production as of around April. > Once the merge is done, we can look at porting all the core > improvements we've made since then. > > B. > > > > On 21 November 2013 16:31, Dan Santner <[email protected]> wrote: >> I use bigcouch in a production system. In my case it's been pretty stable >> but we don't have massive usage yet. >> >> It was one of the easiest things for me to setup honestly. And if you don't >> actually need your own instance running on your own nodes just use cloudant >> which makes the deployment steps go away :). >> >> Dan. >> On Nov 21, 2013, at 10:24 AM, Jens Rantil <[email protected]> wrote: >> >>> Hi, >>> >>> I think I have a use case that would fit BigCouch quite well. This brings >>> me to three questions: >>> >>> - When is the BigCouch merge expected to be released? Maybe I should >>> focus on getting that one working if it's near in time. >>> - If I choose to go with the original BigCouch, will it be easy to >>> migrate to CouchDB when the BigCouch merge is done? >>> - The BigCouch version is 0.4, but I guess it's production ready? >>> >>> >>> Cheers, >>> Jens >>
