I should note that bigcouch is not an Apache project and the term "backport" does not apply. Don't misunderstand me, I'm a big fan of bigcouch, but let's not assume that we can take anything from bigcouch and put it into couchdb without discussion or even a tracking ticket.
I don't much like where this thread is going. I certainly don't want to start a revert war, especially when I'm sure we've all made non-trivial changes to couchdb without a ticket (though not as often without an IRC discussion). Instead, I think it's worth remembering that showing your change before you make it will make everyones lives easier. Filipe, for example, has made tickets and patches for two small issues today. I much prefer that approach. B. On Mon, Jan 3, 2011 at 1:45 PM, Benoit Chesneau <[email protected]> wrote: > On Mon, Jan 3, 2011 at 1:45 PM, Filipe David Manana <[email protected]> > wrote: >> Hi Benoît, >> >> Not that I'm against it, but shouldn't such a significant change be >> discussed before committing it? >> >> Tell me if I'm wrong, but I don't recall any discussing about this >> either at the development mailing list or in a Jira ticket. >> >> cheers >> > > These patches are backport of bigcouch and well tested. I don't see > any reason not using them. These are not really big changzs, just > reorganisation of code. >
