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

2018-02-16 Thread Tommy Stendahl
+1 On 2018-02-14 21:40, Michael Shuler wrote: I propose the following artifacts for release as 3.0.16. sha1: 890f319142ddd3cf2692ff45ff28e71001365e96 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.16-tentative Artifacts:

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

2018-02-15 Thread Vinay Chella
Tests are green on our side. +1 Regards, Vinay Chell ​a​ On Thu, Feb 15, 2018 at 4:30 PM, Nate McCall wrote: > Thanks, Jason!! > > On Fri, Feb 16, 2018 at 1:18 PM, Jason Brown wrote: > > Nate, I can do this. > > > > On Thu, Feb 15, 2018 at 2:51 PM,

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

2018-02-15 Thread Nate McCall
Thanks, Jason!! On Fri, Feb 16, 2018 at 1:18 PM, Jason Brown wrote: > Nate, I can do this. > > On Thu, Feb 15, 2018 at 2:51 PM, Nate McCall wrote: > >> > >> > My circleci test runs fail on lack of resources and I understand now >> > that Jason used the

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

2018-02-15 Thread Jason Brown
Nate, I can do this. On Thu, Feb 15, 2018 at 2:51 PM, Nate McCall wrote: > > > > My circleci test runs fail on lack of resources and I understand now > > that Jason used the circleci configuration from the trunk branch to run > > the 3.0 and 3.11 branches. These branches

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

2018-02-15 Thread Nate McCall
> > My circleci test runs fail on lack of resources and I understand now > that Jason used the circleci configuration from the trunk branch to run > the 3.0 and 3.11 branches. These branches should get commits for a > working CI configuration in-tree. > Quick follow up - does someone have an

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

2018-02-15 Thread Michael Shuler
On 02/15/2018 11:49 AM, Josh McKenzie wrote: > What would it take for us to get green utest/dtests as a blocking part of > the release process? i.e. "for any given SHA, here's a link to the tests > that passed" in the release vote email? Jason graciously linked to his passing test-all runs for

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

2018-02-15 Thread Josh McKenzie
What would it take for us to get green utest/dtests as a blocking part of the release process? i.e. "for any given SHA, here's a link to the tests that passed" in the release vote email? That being said, +1. On Wed, Feb 14, 2018 at 4:33 PM, Nate McCall wrote: > +1 > > On

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

2018-02-14 Thread Nate McCall
+1 On Thu, Feb 15, 2018 at 9:40 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.16. > > sha1: 890f319142ddd3cf2692ff45ff28e71001365e96 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.16-tentative

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

2018-02-14 Thread Jason Brown
I ran the unit tests, and all are green: https://circleci.com/gh/jasobrown/workflows/cassandra/tree/3.0.16-candidate-2 +1. Thank you, Michael. On Wed, Feb 14, 2018 at 12:51 PM, Brandon Williams wrote: > +1 > > On Wed, Feb 14, 2018 at 2:40 PM, Michael Shuler

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

2018-02-14 Thread Brandon Williams
+1 On Wed, Feb 14, 2018 at 2:40 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.16. > > sha1: 890f319142ddd3cf2692ff45ff28e71001365e96 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= >