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 DBD3F100C5 for ; Tue, 4 Feb 2014 16:24:49 +0000 (UTC) Received: (qmail 1057 invoked by uid 500); 4 Feb 2014 16:24:46 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 1012 invoked by uid 500); 4 Feb 2014 16:24:45 -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 1003 invoked by uid 99); 4 Feb 2014 16:24:45 -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 16:24:45 +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 16:24:45 +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 16:24:42 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4F6441C8-B68B-4810-BF57-C778FB53CFF4@apache.org> To: dev@couchdb.apache.org X-Mailer: Apple Mail (2.1827) Gotcha, sounds fair. This is the kind of mistake that arises when we = don=92t talk and merely see bits go by. Once a few more folks confirm that 1843-feature-bigcouch stands up and = can at least do validate_doc_update on a few other platforms, I=92ll = consider the rebar.config.script work in a good enough shape to discuss = it for merging. It=92s broadly what you had except it turns out rebar = itself can do the os:type selection using regex=92s and it=92s possible = to pass different environments for each port (so couch_icu_driver is no = longer linked to spidermonkey for no reason). B. On 4 Feb 2014, at 16:06, Benoit Chesneau wrote: > On Tue, Feb 4, 2014 at 4:50 PM, Robert Samuel Newson = wrote: >=20 >> Hi, >>=20 >> It's largely because we're all busy with wholly bigcouch internal = things >> on our 1843-feature-bigcouch branch, there's nothing *yet* to >> cooperate/feedback about. The closest thing is the bit I'm hacking on >> ("Build with rebar"). >>=20 >> 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. >>=20 >=20 > Actually : >=20 > https://github.com/refuge/couch_core/tree/master/apps/couch_httpd >=20 > The difference is that couch_changes is not its own app like it is in > rcouch: >=20 > https://github.com/refuge/couch_core/tree/master/apps/couch_changes >=20 > because i ported the latest but non released in that branch yet of the > code. I also not integrated the usage of barrel, to easy any merge. So > nothing really new in that split. I just simplified it compared to = rcouch > (if you see in the history this is how it started anyway) in view of > speeding the final merge and propose other changes as patches later. >=20 >=20 >=20 >>=20 >> Before bigcouch can be merged, it needs to build and run and perform = as >> many of the features as possible, that simply can't happen until = 'make' >> works. I deliberately started from your rebar.config.script rather = than the >> code that bigcouch uses (which uses Scons) as it's the right = approach. That >> it's not identical is not a problem, in my opinion, but we can judge = that >> at merge time. It needs to work first. >>=20 >> I appreciate your "during 2 years" comment but let's not go there, I = can >> pull a larger value, as can everyone else at Cloudant, but that's = going to >> be tiresome and divisive and it achieves nothing. >>=20 >> Short version: If it was as simple as dropping in the rcouch versions = of >> these pieces, I'd have finished a week ago. Software is not so = simple. >>=20 >=20 >=20 > ok... I will forget to answer to that part. I will rather focus on > finishing these latest patches. >=20 > - benoit