Re: Branching for the CouchDB 1.3 release

2012-10-24 Thread Jason Smith
On Tue, Oct 23, 2012 at 11:42 PM, Robert Newson rnew...@apache.org wrote: All, 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. As I understand, the

Re: Branching for the CouchDB 1.3 release

2012-10-24 Thread Dave Cottlehuber
On 24 October 2012 09:01, Jason Smith j...@apache.org wrote: On Tue, Oct 23, 2012 at 11:42 PM, Robert Newson rnew...@apache.org wrote: All, 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

Branching for the CouchDB 1.3 release

2012-10-23 Thread Robert Newson
All, 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. As I understand, the principal outstanding issues blocking the 1.3.0 release are; 1) Randall Leed's

Re: Branching for the CouchDB 1.3 release

2012-10-23 Thread Dirkjan Ochtman
On Tue, Oct 23, 2012 at 6:42 PM, Robert Newson rnew...@apache.org wrote: Can I get some votes on my proposal to branch today please? Yes, please! Cheers, Dirkjan

Re: Branching for the CouchDB 1.3 release

2012-10-23 Thread Benoit Chesneau
On Tue, Oct 23, 2012 at 6:42 PM, Robert Newson rnew...@apache.org wrote: All, 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. As I understand, the

Re: Branching for the CouchDB 1.3 release

2012-10-23 Thread Benoit Chesneau
On Tue, Oct 23, 2012 at 6:42 PM, Robert Newson rnew...@apache.org wrote: 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

Re: Branching for the CouchDB 1.3 release

2012-10-23 Thread Jan Lehnardt
On Oct 23, 2012, at 18:42 , Robert Newson rnew...@apache.org wrote: All, 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. As I understand, the

Re: Branching for the CouchDB 1.3 release

2012-10-23 Thread Robert Newson
... to get the other things out and move to the plan of regular releases we promised so many months ago. On 23 October 2012 17:51, Benoit Chesneau bchesn...@gmail.com wrote: On Tue, Oct 23, 2012 at 6:42 PM, Robert Newson rnew...@apache.org wrote: All, It's been a while since we released and I

Re: Branching for the CouchDB 1.3 release

2012-10-23 Thread Benoit Chesneau
On Tue, Oct 23, 2012 at 6:51 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Tue, Oct 23, 2012 at 6:42 PM, Robert Newson rnew...@apache.org wrote: All, 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

Re: Branching for the CouchDB 1.3 release

2012-10-23 Thread Robert Newson
Appreciate you are busy, and appreciate even more getting the code out tomorrow. My point remains that we should be time-based not feature-based now, it's no harm to bump to 1.4. That said, CORS in 1.3 would be awesome. On 23 October 2012 17:53, Benoit Chesneau bchesn...@gmail.com wrote: On

Re: Branching for the CouchDB 1.3 release

2012-10-23 Thread Robert Newson
Branching would free master for commits that are not destined to go in 1.3. The reason to branch is to get some focus and momentum around the 1.3.0 release. And it seems to be working. B. On 23 October 2012 18:01, Benoit Chesneau bchesn...@gmail.com wrote: On Tue, Oct 23, 2012 at 6:51 PM,

Re: Branching for the CouchDB 1.3 release

2012-10-23 Thread Benoit Chesneau
On Tue, Oct 23, 2012 at 7:01 PM, Robert Newson rnew...@apache.org wrote: ... to get the other things out and move to the plan of regular releases we promised so many months ago. In other worlds we do the inverse though ... - benoit

Re: Branching for the CouchDB 1.3 release

2012-10-23 Thread Benoit Chesneau
On Tue, Oct 23, 2012 at 7:03 PM, Robert Newson rnew...@apache.org wrote: Branching would free master for commits that are not destined to go in 1.3. The reason to branch is to get some focus and momentum around the 1.3.0 release. And it seems to be working. B. Let's reformulate , why not

Re: Branching for the CouchDB 1.3 release

2012-10-23 Thread Jan Lehnardt
On Oct 23, 2012, at 19:03 , Benoit Chesneau bchesn...@gmail.com wrote: On Tue, Oct 23, 2012 at 7:01 PM, Robert Newson rnew...@apache.org wrote: ... to get the other things out and move to the plan of regular releases we promised so many months ago. In other worlds we do the inverse though

Re: Branching for the CouchDB 1.3 release

2012-10-23 Thread Robert Newson
I'm happy to defer branching until 11/5 as long as we're clear that anything not on master by that date will not appear in the 1.3 release. After 1.3, I want us to execute on the roadmap process we discussed in Dublin (documented here: https://wiki.apache.org/couchdb/Roadmap_Process) where we

Re: Branching for the CouchDB 1.3 release

2012-10-23 Thread Benoit Chesneau
On Tue, Oct 23, 2012 at 7:43 PM, Robert Newson rnew...@apache.org wrote: I'm happy to defer branching until 11/5 as long as we're clear that anything not on master by that date will not appear in the 1.3 release. agree. After 1.3, I want us to execute on the roadmap process we discussed in