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

2016-11-09 Thread Gary Dusbabek
+1 On Tue, Nov 8, 2016 at 8:08 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.10. > > sha1: 4e0bced5e6a82ebd22b074b8ef96d930c5f3159d > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.0.10-tentative > Artifacts: > https:/

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

2016-11-09 Thread Gary Dusbabek
+1 On Tue, Nov 8, 2016 at 8:09 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.10. > > sha1: 072b5271a88328b909b230d0e30df1c7476fdb3f > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.10-tentative > Artifacts: > https://rep

Re: Moderation

2016-11-09 Thread Isabel Drost-Fromm
On Mon, Nov 07, 2016 at 09:01:39AM +, Ross Gardler wrote: > Because of the way we are structured from an operations point of view or is > necessary to have s commit bit to be a PMC member. However, that doesn't mean > one needs to commit code. > > A good PMC member looks after the health of

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

2016-11-09 Thread Oleksandr Petrov
-1 Sorry but I have to -1 that one, with the following explanation One of the features in 3.10 breaks SASI in quite a significant way. The issue was introduced in #11990 [1] and described in #12877 [2]. If there are more than 8 items in partition that have same index value, index file will get co

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

2016-11-09 Thread Sam Tunnicliffe
-1 from me too due to #12877. I also agree with Alex's suggestion of reverting #11990 and re-rolling. On Wed, Nov 9, 2016 at 1:20 PM, Oleksandr Petrov wrote: > -1 > > Sorry but I have to -1 that one, with the following explanation > > One of the features in 3.10 breaks SASI in quite a significan

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

2016-11-09 Thread Brandon Williams
+1 On Tue, Nov 8, 2016 at 2:08 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.10. > > sha1: 4e0bced5e6a82ebd22b074b8ef96d930c5f3159d > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.0.10-tentative > Artifacts: > https:/

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

2016-11-09 Thread Nate McCall
Good catch. Thanks everyone for speaking up about these. Changing mine to -1 On Nov 10, 2016 2:44 AM, "Sam Tunnicliffe" wrote: > > -1 from me too due to #12877. I also agree with Alex's suggestion of > reverting #11990 and re-rolling. > > On Wed, Nov 9, 2016 at 1:20 PM, Oleksandr Petrov < olek

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

2016-11-09 Thread Jeff Jirsa
-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 following explanation > >One of the features in 3.10 breaks SASI in quite a significant way. The >issue was introduced in #11990 [1] and described in #12877 [2]. If there >are mor

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

2016-11-09 Thread Nate McCall
I like the idea of a goal-based approach. I think that would make coming to a consensus a bit easier particularly if a larger number of people are involved. On Tue, Nov 8, 2016 at 8:04 PM, Dikang Gu wrote: > My 2 cents. I'm wondering is it a good idea to have some high level goals > for the major

[RESULT] [VOTE] Close client-...@cassandra.apache.org mailing list

2016-11-09 Thread Jeff Jirsa
With 8 binding +1s (including myself), 3 non-binding +1, and no -1, the vote passes, and we'll work to close out this list. - Jeff On 2016-11-06 21:11 (-0800), "Jeff Jirsa" wrote: > There exists a nearly unused mailing list, client-...@cassandra.apache.org > [0]. > > This is a summary of th