Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A428C10EDB for ; Tue, 4 Feb 2014 15:50:54 +0000 (UTC) Received: (qmail 4176 invoked by uid 500); 4 Feb 2014 15:50:53 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 4130 invoked by uid 500); 4 Feb 2014 15:50:52 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 4122 invoked by uid 99); 4 Feb 2014 15:50:51 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Feb 2014 15:50:51 +0000 Received: from localhost (HELO [192.168.1.4]) (127.0.0.1) (smtp-auth username rnewson, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Feb 2014 15:50:51 +0000 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: Goals for 2014 From: Robert Samuel Newson In-Reply-To: Date: Tue, 4 Feb 2014 15:50:48 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <4F6441C8-B68B-4810-BF57-C778FB53CFF4@apache.org> References: To: dev@couchdb.apache.org X-Mailer: Apple Mail (2.1827) Hi, It=92s largely because we=92re all busy with wholly bigcouch internal = things on our 1843-feature-bigcouch branch, there=92s nothing *yet* to = cooperate/feedback about. The closest thing is the bit I=92m hacking on = ("Build with rebar"). I agree that we should not be inventing new things during the merge, but = then I saw you were splitting out parts of couch_httpd elsewhere, which = counts as that. Before bigcouch can be merged, it needs to build and run and perform as = many of the features as possible, that simply can=92t happen until = 'make' works. I deliberately started from your rebar.config.script = rather than the code that bigcouch uses (which uses Scons) as it=92s the = right approach. That it=92s not identical is not a problem, in my = opinion, but we can judge that at merge time. It needs to work first. I appreciate your "during 2 years" comment but let=92s not go there, I = can pull a larger value, as can everyone else at Cloudant, but that=92s = going to be tiresome and divisive and it achieves nothing. Short version: If it was as simple as dropping in the rcouch versions of = these pieces, I=92d have finished a week ago. Software is not so simple. B. On 4 Feb 2014, at 15:43, Benoit Chesneau wrote: > On Tue, Feb 4, 2014 at 4:13 PM, Robert Samuel Newson = wrote: >=20 >> "Recent commits in the bigcouch branch redoing some >> work already done in rcouch (coming from a 2 years experience" >>=20 >> Work done in rcouch is not sacred, does not necessarily go into = couchdb >> master without editing or review by anyone else, and that applies to >> bigcouch as well. As you should know, bigcouch also builds with rebar = but >> *differently*. I am expending time and effort to find a way to make = it all >> work together. Please stop this attitude. >>=20 >=20 >=20 > Sorry? Where do you see I am saying it's sacred. >=20 > All I am saying is that it would be a lot more productive time for = both > if instead of putting code from each other branches without > consultations, we could sit around a branch and start to put the code > where we have the experience in. >=20 > And don't get me wrong here, I don't imply you don't know what you do. > But I put a lot of time, working on this code with others in rcouch, > during 2 years, so it is a lot easier for me to go on it. I don't see > the point at all to start a new thing on a branch which wasn't planned > at the beginning of the merge. This is why I didn't included any > optimizations from rcouch and bigger changes in couch core so it can = be > merged easily. >=20 > I was hoping from more cooperation and feedback, like commenting on = the > code or saying if a particular piece is wrong and alike.