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 1682F61F4 for ; Tue, 28 Jun 2011 16:20:13 +0000 (UTC) Received: (qmail 98271 invoked by uid 500); 28 Jun 2011 16:20:12 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 98074 invoked by uid 500); 28 Jun 2011 16:20:11 -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 98066 invoked by uid 99); 28 Jun 2011 16:20:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Jun 2011 16:20:11 +0000 X-ASF-Spam-Status: No, hits=0.9 required=5.0 tests=SPF_NEUTRAL,TO_NO_BRKTS_PCNT X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [80.244.253.218] (HELO mail.traeumt.net) (80.244.253.218) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Jun 2011 16:20:03 +0000 Received: from [192.168.178.25] (brln-4d0ce288.pool.mediaWays.net [77.12.226.136]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.traeumt.net (Postfix) with ESMTPSA id D85A23C205 for ; Tue, 28 Jun 2011 18:19:42 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Apple Message framework v1084) Subject: Re: [VOTE] Apache CouchDB 1.0.3 Release From: Jan Lehnardt In-Reply-To: Date: Tue, 28 Jun 2011 18:19:42 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <69412B34-7CF5-46B8-A9FB-AF4DE6D923D5@apache.org> References: <1F84F64A-093C-47D3-9732-FED68DC2F025@googlemail.com> <0DA7F2FC-99AA-4904-A04E-14DB9FC4B32C@apache.org> To: dev@couchdb.apache.org X-Mailer: Apple Mail (2.1084) X-Virus-Checked: Checked by ClamAV on apache.org On 28 Jun 2011, at 18:11, Noah Slater wrote: >=20 > On 28 Jun 2011, at 17:09, Sebastian Cohnen wrote: >=20 >>> Perhaps there is some good reason for them failing? >>=20 >> I was not aware that the javascript CLI tests are "officially" ready = to use yet. In that case it's definitely not okay if they are failing = and since others have seen the same failing tests, I'd change my vote to = =E2=88=921. >=20 > If they are not ready to use yet, that is a good reason for them = failing. If they should be part of the test procedure, then they should = a) pass and b) be added to the wiki. Sorry for being so ARGH about it, = but I like to run a tight ship, so we should get clarification on this = either way. Thanks! It's all good Noah, I'm 100% behind you here :) Sebastian, sorry, I didn't see you were running the still experimental = CLI tests. Cheers Jan --=20