Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
Subject: Re: Branching for the CouchDB 1.3 release
From: Jan Lehnardt <jan@apache.org>
In-Reply-To: 
 <CABvT1DGGr__-AmxpGcaax0ZdMVi7E9GCuaotVTFQJXFfw-xU5A@mail.gmail.com>
Date: Tue, 23 Oct 2012 18:55:34 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F3F83441-F43E-4585-8D6C-1B366137A8A1@apache.org>
References: 
 <CABvT1DGGr__-AmxpGcaax0ZdMVi7E9GCuaotVTFQJXFfw-xU5A@mail.gmail.com>
To: dev@couchdb.apache.org


On Oct 23, 2012, at 18:42 , Robert Newson <rnewson@apache.org> wrote:

> All,
>=20
> It's been a while since we released and I want to change this now. I
> propose making a 1.3.x branch from today's master
> (66529378dd06342929e04772370f3509cbe786a5) and building 1.3.0 there.
>=20
> As I understand, the principal outstanding issues blocking the 1.3.0
> release are;
>=20
> 1) Randall Leed's backports of fixes from 1.2.0. This code is written
> and I have reviewed it, though more eyes are appreciated.
> 2) The CORS patch. This has been around for a very long time but has
> not reached our repository in any form. Earlier this month I proposed
> that if it does not appear in usable form by the end of the calendar
> month, it gets bumped to the next release.
> 3) The blockers marked in JIRA.

For your convenience: =
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=3Dtrue&jql=
Query=3Dproject+%3D+COUCHDB+AND+priority+%3D+Blocker+AND+status+%21%3D+Res=
olved+AND+fixVersion+%3D+%221.3%22+ORDER+BY+key+DESC%2C+updated+DESC

> I think all of those things can land on 1.3.x and master.
>=20
> Can I get some votes on my proposal to branch today please?

+1