about ticket "CASSANDRA-14847"

2019-02-03 Thread Fumiya Yamashita
Hello. I have created a ticket for the improvement of nodetool. (https://issues.apache.org/jira/browse/CASSANDRA-14847) I’d like this patch to be merged to Cassandra 4.0, So which version should I choose as Fix version? {4.0 | 4.0.x | 4.x} Thank you. --- Fumiya

Re: [VOTE] Release Apache Cassandra 2.1.21

2019-02-03 Thread Anthony Grasso
Hi Michael, What you and Jon said makes sense. You have addressed a follow up concern I had about making sure the site was updated if we go ahead with making 2.1 EOL. I'm happy to help with site changes if needed. Cheers, Anthony On Mon, 4 Feb 2019 at 11:31, Michael Shuler wrote: > My first

Re: [VOTE] Release Apache Cassandra 3.11.4

2019-02-03 Thread Joseph Lynch
3.11.4-tentative unit and dtest run: https://circleci.com/gh/jolynch/cassandra/tree/3.11.4-tentative unit tests: 0 failures dtests: 1 failure * test_closing_connections - thrift_hsha_test.TestThriftHSHA ( https://issues.apache.org/jira/browse/CASSANDRA-14595) +1 non binding -Joey On Sat, Feb

Re: [VOTE] Release Apache Cassandra 3.0.18

2019-02-03 Thread Joseph Lynch
3.0.18-tentative unit and dtest run: https://circleci.com/gh/jolynch/cassandra/tree/3.0.18-tentative unit tests: 0 failures dtests: 1 failure * test_closing_connections - thrift_hsha_test.TestThriftHSHA ( https://issues.apache.org/jira/browse/CASSANDRA-14595) +1 non binding -Joey On Sat, Feb

Re: [VOTE] Release Apache Cassandra 2.1.21

2019-02-03 Thread Michael Shuler
My first couple sentences in the vote email were intended as a statement, based on a lack of concerns voiced on EOL of 2.1. I made a request for comment on EOL of 2.1 series a month ago, in "Subject: EOL 2.1 series?":

Re: [VOTE] Release Apache Cassandra 2.1.21

2019-02-03 Thread Anthony Grasso
+1 non-binding, for the release of 2.1.21 Regarding EOL of 2.1.x, did we announce in the past that 2.1.21 would be the final release? According to the download page 2.1 is meant to be supported with critical fixes only until 4.0 is released. I suspect that

Re: [VOTE] Release Apache Cassandra 3.0.18

2019-02-03 Thread Anthony Grasso
+1 non-binding On Mon, 4 Feb 2019 at 05:52, Jonathan Haddad wrote: > +1 > > On Sun, Feb 3, 2019 at 9:44 AM Nate McCall wrote: > > > On Sat, Feb 2, 2019 at 4:32 PM Michael Shuler > > wrote: > > > > > > I propose the following artifacts for release as 3.0.18. > > > > > > sha1:

Re: [VOTE] Release Apache Cassandra 3.11.4

2019-02-03 Thread Anthony Grasso
+1 non-binding On Mon, 4 Feb 2019 at 06:19, Jonathan Haddad wrote: > +1 > > On Sun, Feb 3, 2019 at 9:35 AM Nate McCall wrote: > > > On Sat, Feb 2, 2019 at 4:38 PM Michael Shuler > > wrote: > > > > > > I propose the following artifacts for release as 3.11.4. > > > > > > sha1:

Re: [VOTE] Release Apache Cassandra 2.2.14

2019-02-03 Thread Anthony Grasso
+1 non-binding On Mon, 4 Feb 2019 at 04:39, Nate McCall wrote: > On Sat, Feb 2, 2019 at 4:32 PM Michael Shuler > wrote: > > > > I propose the following artifacts for release as 2.2.14. > > > > sha1: af91658353ba601fc8cd08627e8d36bac62e936a > > Git: > > >

Re: [VOTE] Release Apache Cassandra 2.1.21

2019-02-03 Thread Jonathan Haddad
I think having the discussion around EOL is pretty important, in order to set the right expectations for the community. Looking at the commits for 2.1, there's hardly any activity going on, meaning it's effectively been EOL'ed for a long time now. I think it's better that we be honest with folks

Re: [VOTE] Release Apache Cassandra 3.11.4

2019-02-03 Thread Jonathan Haddad
+1 On Sun, Feb 3, 2019 at 9:35 AM Nate McCall wrote: > On Sat, Feb 2, 2019 at 4:38 PM Michael Shuler > wrote: > > > > I propose the following artifacts for release as 3.11.4. > > > > sha1: fd47391aae13bcf4ee995abcde1b0e180372d193 > > Git: > > >

Re: [VOTE] Release Apache Cassandra 3.0.18

2019-02-03 Thread Jonathan Haddad
+1 On Sun, Feb 3, 2019 at 9:44 AM Nate McCall wrote: > On Sat, Feb 2, 2019 at 4:32 PM Michael Shuler > wrote: > > > > I propose the following artifacts for release as 3.0.18. > > > > sha1: edd52cef50a6242609a20d0d84c8eb74c580035e > > Git: > > >

Re: CASSANDRA-14916

2019-02-03 Thread Dinesh Joshi
Hi Jean, Sorry this one fell through the cracks. I’ll take a look. Dinesh > Am 01.02.2019 um 00:49 schrieb Jean Carlo : > > Hello guys, someone can check this jira please? I did not get a feedback > from @Dinesh_Joshi for the moments :) > >

Re: [VOTE] Release Apache Cassandra 3.0.18

2019-02-03 Thread Nate McCall
On Sat, Feb 2, 2019 at 4:32 PM Michael Shuler wrote: > > I propose the following artifacts for release as 3.0.18. > > sha1: edd52cef50a6242609a20d0d84c8eb74c580035e > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.18-tentative > Artifacts: >

Re: [VOTE] Release Apache Cassandra 2.2.14

2019-02-03 Thread Nate McCall
On Sat, Feb 2, 2019 at 4:32 PM Michael Shuler wrote: > > I propose the following artifacts for release as 2.2.14. > > sha1: af91658353ba601fc8cd08627e8d36bac62e936a > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.14-tentative > Artifacts: >

Re: [VOTE] Release Apache Cassandra 3.11.4

2019-02-03 Thread Nate McCall
On Sat, Feb 2, 2019 at 4:38 PM Michael Shuler wrote: > > I propose the following artifacts for release as 3.11.4. > > sha1: fd47391aae13bcf4ee995abcde1b0e180372d193 > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.4-tentative > Artifacts: >

Re: [VOTE] Release Apache Cassandra 2.1.21

2019-02-03 Thread Nate McCall
+1 on the release of 2.1.21 (let's focus on that in the spirit of these other votes we have up right now). I don't feel the need to be absolutist about something being EOL. On Sun, Feb 3, 2019 at 1:47 AM Stefan Podkowinski wrote: > > What are we voting on here? Releasing the 2.1.21 candidate,

Re: [VOTE] Release Apache Cassandra 2.1.21

2019-02-03 Thread Stefan Podkowinski
What are we voting on here? Releasing the 2.1.21 candidate, or that 2.1 would become EOL? Please let's have separate votes on that, if you want to propose putting 2.1 EOL (which I'm strongly -1). On 03.02.19 01:32, Michael Shuler wrote: *EOL* release for the 2.1 series. There will be no new