Re: [VOTE] Release Apache Cassandra 3.0.18

2019-02-06 Thread Ariel Weisberg
Hi, +1 Upgrade test look OK. There are failures I also found against 2.2 plus some other test bugs. Nothing that looks like a product bug. https://circleci.com/gh/aweisberg/cassandra/2589 Ariel On Wed, Feb 6, 2019, at 5:02 AM, Marcus Eriksson wrote: > +1 > > Den ons 6 feb. 2019 kl 10:53

Re: [VOTE] Release Apache Cassandra 3.0.18

2019-02-06 Thread Marcus Eriksson
+1 Den ons 6 feb. 2019 kl 10:53 skrev Benedict Elliott Smith < bened...@apache.org>: > +1 > > > On 6 Feb 2019, at 08:01, Tommy Stendahl > wrote: > > > > +1 (non-binding) > > > > /Tommy > > > > On lör, 2019-02-02 at 18:32 -0600, Michael Shuler wrote: > > > > I propose the following artifacts for

Re: [VOTE] Release Apache Cassandra 3.0.18

2019-02-06 Thread Benedict Elliott Smith
+1 > On 6 Feb 2019, at 08:01, Tommy Stendahl wrote: > > +1 (non-binding) > > /Tommy > > On lör, 2019-02-02 at 18:32 -0600, Michael Shuler wrote: > > I propose the following artifacts for release as 3.0.18. > > sha1: edd52cef50a6242609a20d0d84c8eb74c580035e > Git: >

Re: [VOTE] Release Apache Cassandra 3.0.18

2019-02-06 Thread Tommy Stendahl
+1 (non-binding) /Tommy On lör, 2019-02-02 at 18:32 -0600, 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 3.0.18

2019-02-05 Thread Jeff Jirsa
+1 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 3.0.18

2019-02-04 Thread Aleksey Yeshchenko
+1 > On 4 Feb 2019, at 00:39, Joseph Lynch wrote: > > 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 ( >

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 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.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: [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 3.0.18

2019-02-02 Thread Jeff Jirsa
There’s SO MUCH that needs to go out, let’s just get out what we have -- Jeff Jirsa > On Feb 2, 2019, at 5:35 PM, Benedict Elliott Smith > wrote: > > CASSANDRA-14812 should probably land in this release, given that it is a > critical bug, has been patch available for a while, and is

Re: [VOTE] Release Apache Cassandra 3.0.18

2019-02-02 Thread Benedict Elliott Smith
CASSANDRA-14812 should probably land in this release, given that it is a critical bug, has been patch available for a while, and is relatively simple. That said, we are sorely due a release. But if we go ahead without it, we should follow up soon after. > On 3 Feb 2019, at 00:32, Michael