Re: 1.1 release (was Re: 0.15 release)

2015-01-27 Thread Brock Noland
On Tue, Jan 27, 2015 at 6:05 PM, Thejas Nair wrote: > On Tue, Jan 27, 2015 at 5:13 PM, Brock Noland wrote: > > > Additionally if you find blockers that you would like in 1.2, please > > have them committed to trunk and ping me to merge them to 1.2. > > > > > Brock, I assume you meant 1.1 (not 1

Re: 1.1 release (was Re: 0.15 release)

2015-01-27 Thread Thejas Nair
On Tue, Jan 27, 2015 at 5:13 PM, Brock Noland wrote: > Additionally if you find blockers that you would like in 1.2, please > have them committed to trunk and ping me to merge them to 1.2. > > Brock, I assume you meant 1.1 (not 1.2) in above sentence. -- CONFIDENTIALITY NOTICE NOTICE: This mes

Re: 1.1 release (was Re: 0.15 release)

2015-01-27 Thread Brock Noland
Hi, As I mentioned before, my main concern was that the 1.0 release would block the next release from trunk. Since we are in the RC phase for 1.0, this doesn't seem likely. As such, I am ok with moving forward with the 1.x naming scheme. As such I have: * Renamed "next" to "branch-1.1" * Updated

Re: 0.15 release

2015-01-26 Thread Brock Noland
Hi Alan, Thank you very much for the clarification. Naming the branch "next" for now is fine with me. I've done so. Cheers, Brock On Mon, Jan 26, 2015 at 10:27 AM, Alan Gates wrote: > I'm not asking you to slow the work for the release. If you want to > branch, you can branch. What I'm askin

Re: 0.15 release

2015-01-26 Thread Alan Gates
I'm not asking you to slow the work for the release. If you want to branch, you can branch. What I'm asking is to hold on the numbering scheme. So you could name the branch 'next' or something and then rename once we come to agreement. Consensus in the community is important, and we should

Re: 0.15 release

2015-01-26 Thread Xuefu Zhang
>From a different perspective, 0.14.1/0.15 proposal allow us to release independently and concurrently. Once they are leased, we can have a consented 1.0 release. On the other hand, 1.0/1.1 would force us to wait to release 1.1 after 1.0 is released. This dependency seems artificial and can be avo

Re: 0.15 release

2015-01-26 Thread Brock Noland
Hi Alan, In all of my experience at Apache, I have been encouraged to release. Contributors rightly want to see their hard work gets in the hands of the users. That's why they contribute after all. Many contributors who have features in trunk would like get those features out into the community. T

Re: 0.15 release

2015-01-26 Thread Alan Gates
Brock, Given there isn't consensus on numbering yet, could you holding off making the 0.15 branch. We should come to a conclusion on whether we're doing 0.14.1/0.15 or 1.0/1.1 before assigning anymore numbers. Alan. Brock Noland January 20, 2015 at 21:25 Just a

Re: 0.15 release

2015-01-20 Thread Brock Noland
Just a reminder that I plan on branching on 1/26/2015 and start rolling release candidates on 2/9/2015. After branching I plan on merging only blockers. Brock On Mon, Jan 12, 2015 at 2:37 PM, Brock Noland wrote: > Hi, > > Projects are instructed in the incubator that releases gain new users and

0.15 release

2015-01-12 Thread Brock Noland
Hi, Projects are instructed in the incubator that releases gain new users and other attention. Additionally, as discussed in this forum I'd like to increase the tempo of our release process[1]. As such, I plan on following this process: 1) Provide two weeks notice of branching 2) Provide two wee

Re: 0.15 release

2014-12-01 Thread Brock Noland
d two large releases. Thank you very much to the RM's for >>> pushing those out! I've found that Apache projects gain traction >>> through releasing often, thus I think we should aim to increase the >>> rate of releases in 2015. (Not that I cannot complain since I

Re: 0.15 release

2014-12-01 Thread Thejas Nair
of releases in 2015. (Not that I cannot complain since I did not >> volunteer to RM any release.) >> >> As such I'd like to volunteer as RM for the 0.15 release. >> >> Cheers, >> Brock -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the u

Re: 0.15 release

2014-12-01 Thread Thejas Nair
g those out! I've found that Apache projects gain traction > through releasing often, thus I think we should aim to increase the > rate of releases in 2015. (Not that I cannot complain since I did not > volunteer to RM any release.) > > As such I'd like to volunteer as RM

0.15 release

2014-12-01 Thread Brock Noland
to RM any release.) As such I'd like to volunteer as RM for the 0.15 release. Cheers, Brock