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 42D05EBC6 for ; Mon, 18 Mar 2013 22:41:29 +0000 (UTC) Received: (qmail 71415 invoked by uid 500); 18 Mar 2013 22:41:28 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 71369 invoked by uid 500); 18 Mar 2013 22:41:28 -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 71360 invoked by uid 99); 18 Mar 2013 22:41:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Mar 2013 22:41:28 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of wendallc@83864.com designates 209.85.160.42 as permitted sender) Received: from [209.85.160.42] (HELO mail-pb0-f42.google.com) (209.85.160.42) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Mar 2013 22:41:24 +0000 Received: by mail-pb0-f42.google.com with SMTP id xb4so6782987pbc.29 for ; Mon, 18 Mar 2013 15:41:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=83864.com; s=google; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=NDVh9gOeeIxUITucg1OjmdYkZfKxqk7p7/j9HFmmchU=; b=VxRqpCRgWLT3+5z7FJlCOqHfQSHF5MypF+MHqh9zgrgMKtuirV5EFdLRg4KZY5/PRW OBpNwl6ETYFawWD2Tp9WdQPHnXCmJTdb+nB4s4IxgOIJCsBmpXNp/iF1xF4ixCXaDxP9 fjAiO60K5KG/fcAh3cvInORVIIFR+xK9nWJjg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=NDVh9gOeeIxUITucg1OjmdYkZfKxqk7p7/j9HFmmchU=; b=e2lAhTdunSIRQzjGCxd+QGcWqYeGzjjtmAbQu1NdNbhpiCuJJ38eOMQorgNCDn4AP/ CB++WBOOKldaO+SeSWsi1tchY6jZOe3USGO58cBQY3gSKjW0vD7GVSDwwblVH1bbpnOs JY1qS7AWdwVCTdr4Tq/Ryajy0m5ZzYOKyKrntIBWgcGz7PeKNv8dYVHVCgB5Vw1FmI4I +5J/s52Vp7qbIPwFxfQBN1vGEna0uBl3BEw2ol88RQ4xlnl9OHp8Qqyiya02/GxJsgTI Lca/fdkp5TMZh4KWPeA9K0ai/qrUbBci4QF8odk427R4S2RCN1Iexvh32UUjYH/sqC0A RRcg== X-Received: by 10.66.241.71 with SMTP id wg7mr12890830pac.155.1363646463361; Mon, 18 Mar 2013 15:41:03 -0700 (PDT) Received: from wlaptop.localdomain (c-67-170-178-212.hsd1.or.comcast.net. [67.170.178.212]) by mx.google.com with ESMTPS id hw16sm9774474pab.19.2013.03.18.15.41.01 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 18 Mar 2013 15:41:02 -0700 (PDT) Message-ID: <514797FC.4080704@83864.com> Date: Mon, 18 Mar 2013 15:41:00 -0700 From: Wendall Cada User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130311 Thunderbird/17.0.4 MIME-Version: 1.0 To: dev@couchdb.apache.org Subject: Re: Status of 1.2.x and 1.3.x branches References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQl9W139a0vBsVnOQyThCzS8N9tAM0GDJ2L0U2D2rmcGiQ3aftHLuD8F13z+XyhFcP+beWnD X-Virus-Checked: Checked by ClamAV on apache.org Note: I am not a committer for the project, I've just been following this current release cycle closely. For 1.2.x It appears as though all blockers have been resolved, allowing for a 1.2.2 rc. For 1.3.x Only issues remaining in the blockers list (http://s.apache.org/couchdb_130_blockers) are https://issues.apache.org/jira/browse/COUCHDB-1696 (Support Erlang/OTP R16B) The only other issues for 1.3.x, not on the list are the intermittent test failures. I think the only questions here remaining are: 1. Can 1.3.0 ship without COUCHDB-1696? 2. Can 1.3.0 ship with known test issues? Wendall On 03/17/2013 09:58 AM, Jan Lehnardt wrote: > On Mar 16, 2013, at 21:46 , Noah Slater wrote: > >> Hey devs, >> >> When will 1.2.x > 1.2.x is ready for 1.2.2 now. > >> and 1.3.x be ready for me to cut release candidates? > There are a few issues up on http://s.apache.org/couchdb_130_blockers that are being worked through. > > Cheers > Jan