Re: [VOTE] Release Apache Cassandra 3.10 (Take 2)

2016-11-11 Thread Eduard Tudenhoefner
-1 because internode_encryption is broken due to https://issues.apache.org/jira/browse/CASSANDRA-12903 On Wed, Nov 9, 2016 at 9:16 PM, Jeff Jirsa wrote: > -1 as well, #12877 > > > > On 11/9/16, 5:20 AM, "Oleksandr Petrov" > wrote: > > >-1 > > > >Sorry but I have to -1 that one, with the followi

Re: [VOTE] Release Apache Cassandra 3.0.10 (Take 2)

2016-11-11 Thread Jake Luciani
-1 due to https://issues.apache.org/jira/browse/CASSANDRA-11039 It's a small fix but a critical bug. I'll patch shortly On Nov 11, 2016 2:32 AM, "Tommy Stendahl" wrote: > +1 (non-binding) > > > On 2016-11-08 21:08, Michael Shuler wrote: > >> I propose the following artifacts for release as 3.0.

Re: [VOTE] Release Apache Cassandra 3.0.10 (Take 2)

2016-11-11 Thread Jake Luciani
Should I merge the fix to just the 3.0.10 tag? or should we include the 3 new tickets that went into 3.0.11 already? I see no issue with the latter since they are bugfixes On Fri, Nov 11, 2016 at 8:48 AM, Jake Luciani wrote: > -1 due to https://issues.apache.org/jira/browse/CASSANDRA-11039 > > I

Re: [VOTE] Release Apache Cassandra 3.0.10 (Take 2)

2016-11-11 Thread Michael Shuler
I think cassandra-3.0 HEAD is good with me, too. We can adjust the fixver for those that may say 3.0.11 currently. -- Michael On 11/11/2016 08:31 AM, Jake Luciani wrote: > Should I merge the fix to just the 3.0.10 tag? or should we include the 3 > new tickets that went into 3.0.11 already? I see

Re: [VOTE FAILED] Release Apache Cassandra 3.10 (Take 2)

2016-11-11 Thread Michael Shuler
Thanks for all the feedback, I'm changing to a -1, too. Vote comes to 1 binding +1, 3 binding -1, 3 non-binding -1. -- Kind regards, Michael On 11/08/2016 02:09 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.10. > > sha1: 072b5271a88328b909b230d0e30df1c7476fdb3f

Re: [VOTE] Release Apache Cassandra 3.0.10 (Take 2)

2016-11-11 Thread Michael Shuler
For the record, I'm changing my vote to a -1, as well. -- Michael On 11/11/2016 09:40 AM, Michael Shuler wrote: > I think cassandra-3.0 HEAD is good with me, too. We can adjust the > fixver for those that may say 3.0.11 currently. >

Re: [VOTE] Release Apache Cassandra 3.0.10 (Take 2)

2016-11-11 Thread Aleksey Yeschenko
-1 for the reasons listed. — AY On 11 November 2016 at 16:59:04, Michael Shuler (mich...@pbandjelly.org) wrote: For the record, I'm changing my vote to a -1, as well. -- Michael On 11/11/2016 09:40 AM, Michael Shuler wrote: > I think cassandra-3.0 HEAD is good with me, too. We can adju

New 'cassandra-builds' git repo, or in-tree?

2016-11-11 Thread Michael Shuler
We're working on configuring new donated servers for Apache Cassandra testing in the ASF Jenkins infrastructure. I have a preference to request INFRA set up a new git repository specifically for build/test_run/jenkins_template scripts, separate from the main Apache Cassandra source, but I'm wonderi

Re: New 'cassandra-builds' git repo, or in-tree?

2016-11-11 Thread Jeffrey Jirsa
+1 to new repo. On 11/11/16, 11:55 AM, "Michael Shuler" wrote: >We're working on configuring new donated servers for Apache Cassandra >testing in the ASF Jenkins infrastructure. I have a preference to >request INFRA set up a new git repository specifically for >build/test_run/jenkins_template s

Re: New 'cassandra-builds' git repo, or in-tree?

2016-11-11 Thread Nate McCall
> It may also allow a > lower barrier for contributors interested in helping with specifically > build/test infrastructure. Good point for new repo. Thanks!

Re: New 'cassandra-builds' git repo, or in-tree?

2016-11-11 Thread Michael Shuler
On 11/11/2016 01:02 PM, Nate McCall wrote: >> It may also allow a >> lower barrier for contributors interested in helping with specifically >> build/test infrastructure. > > Good point for new repo. Requested a new 'cassandra-builds' git repo! Thanks. -- Michael

Re: [VOTE FAILED] Release Apache Cassandra 3.0.10 (Take 2)

2016-11-11 Thread Michael Shuler
I count 3 binding +1, 1 non-binding +1, and 3 binding -1 votes. I'll re-roll a new release, since the CASSANDRA-11039 fix has already been committed. -- Kind regards, Michael On 11/08/2016 02:08 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.10. > > sha1: 4e0bc

[VOTE] Release Apache Cassandra 3.0.10 (Take 3)

2016-11-11 Thread Michael Shuler
I propose the following artifacts for release as 3.0.10. sha1: d6a3ef4863142c3f9fc1def911f28341fc78f2e8 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.10-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1134/org/apac

Re: [VOTE] Release Apache Cassandra 3.0.10 (Take 3)

2016-11-11 Thread Jeff Jirsa
+1 -- Jeff Jirsa > On Nov 11, 2016, at 5:36 PM, Michael Shuler wrote: > > I propose the following artifacts for release as 3.0.10. > > sha1: d6a3ef4863142c3f9fc1def911f28341fc78f2e8 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.10-tentative > Arti

Re: Broader community involvement in 4.0 (WAS Re: Rough roadmap for 4.0)

2016-11-11 Thread Anuj Wadehra
Thanks for the information Jeremy. My main concern is around making JIRAs easy to understand. I am not sure how community feels about it. But, I have personally observed that long discussion thread on JIRAs is not user friendly for someone trying to understand the ticket or may be trying to co