Re: [VOTE] Release Apache Cassandra 3.0.13

2017-04-13 Thread Sam Tunnicliffe
> > One dtest failed on the standard and "novnode" jobs, which we > have an existing JIRA for, CASSANDRA-13113 The initial dtest failure that 13113 was opened for is not worth blocking the release for IMO. In the comments of that ticket, Alex has identified a more pressing, user facing regression

Re: [VOTE] Release Apache Cassandra 3.0.13

2017-04-13 Thread Jason Brown
Alex and Sam T think CASSANDRA-13113 is not a deal breaker in terms of regression (from reading their comments on the JIRA), and Sam mentioned to me that it only affects trunk, so I'm going to +1 and will poke on CASSAADNRA-13113 to get it done as soon as it can be :) -Jason On Thu, Apr 13, 2017

Re: [VOTE] Release Apache Cassandra 3.0.13

2017-04-13 Thread Tommy Stendahl
non-binding +1 On 2017-04-11 20:59, Michael Shuler wrote: I propose the following artifacts for release as 3.0.13. sha1: 91661ec296c6d089e3238e1a72f3861c449326aa Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.13-tentative Artifacts: https://repository.ap