From dev-return-13482-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Fri Nov 26 14:23:50 2010 Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 79546 invoked from network); 26 Nov 2010 14:23:49 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 26 Nov 2010 14:23:49 -0000 Received: (qmail 35133 invoked by uid 500); 26 Nov 2010 14:23:47 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 34838 invoked by uid 500); 26 Nov 2010 14:23:47 -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 34384 invoked by uid 99); 26 Nov 2010 14:23:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Nov 2010 14:23:46 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lemenkov@gmail.com designates 209.85.214.52 as permitted sender) Received: from [209.85.214.52] (HELO mail-bw0-f52.google.com) (209.85.214.52) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Nov 2010 14:23:40 +0000 Received: by bwz4 with SMTP id 4so1857851bwz.11 for ; Fri, 26 Nov 2010 06:23:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=k137bXECXTDJZ12qYuqX1Fla542KKwK18DC8mORUpMs=; b=HnjWeZOoKeOzvExxgD2G1MRLT9GpKOqhd3rdhaWPS/09aoSMEVCYJFh+WtEQ6Qks5x ynhswT9kcfBhTa2qp4hk4CFA/mokP9bWk+Cm7jC0xnQ/TIws1ZInZeStNmcmCVIYJ0Cu Y4495UBq6IgioFEUwGnRtoD3QVnTWolrJz/Mo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=h2cGQEQYamSi6wJSXtyQUc7wIDP/3F0LBAXR0zsYTgO3qhQGNFeCiZM/bpsQwvYouO FqqCI6Yx8rCi6oqBuYLyDB9htMU464H5cGgP8r1phYWgg2TF5IcRa6PUmv2L/J2Jv66W tcjQbtth0j+G5zDggsoX5aQxMmCnE9ruANohM= MIME-Version: 1.0 Received: by 10.204.72.6 with SMTP id k6mr1977451bkj.58.1290781398869; Fri, 26 Nov 2010 06:23:18 -0800 (PST) Received: by 10.204.116.148 with HTTP; Fri, 26 Nov 2010 06:23:18 -0800 (PST) In-Reply-To: <2A5B2BD2-9865-49B1-9EA5-E6A8DC2BA6B1@apache.org> References: <04335370-BB92-453D-AD53-FA16306FC703@googlemail.com> <2A5B2BD2-9865-49B1-9EA5-E6A8DC2BA6B1@apache.org> Date: Fri, 26 Nov 2010 17:23:18 +0300 Message-ID: Subject: Re: [VOTE] Apache CouchDB 1.0.2 release, Round 1 From: Peter Lemenkov To: dev@couchdb.apache.org Content-Type: text/plain; charset=UTF-8 Hello 2010/11/26 Jan Lehnardt : > We always patch Mochiweb to fit our needs that are divergent from the > upstream project. It isn't safe to assume an independent cut of Mochiweb > will just work. Well, it isn't even safe to assume that it will work on an arbitrary system with different set of underlying libraries and tools. So we just play for the stable API/ABI interfaces. Shipping internally a small set of libraries isn't enough - you need to ship js, libicu, erlang and so on. > e.g. we're changing the default handling of encoding integers in mochijson2 > among other things. Fortunately it's not very diverged from upstream - it just too old. I re-checked (as I did every couchdb release since 0.10.2) what was added in CouchDB internal copy - I don't see what changes from CouchDB copy are still missing in upstream repository (perhaps someone from Mochi is monitoring your work and quickly applies changes if any). > I'd strongly suggest to not build a package that is seemingly like our > release but has subtle differences or bugs. It hasn't any known bugs related to my changes (i mean I wasn't aware of them - not that they doesn't exist). So that's a pure speculation. On the other hand your copy of mochiweb does contains known defects already fixed in upstream. Not sure whether they affect CouchDB operation though. -- With best regards, Peter Lemenkov.