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

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: Release votes

I'd like to help as well. For me the issue is I have only my time to contribute. The resources to test Cassandra extensively are beyond that of most individuals including me, aren't they? If resources are made available and I can help, count me in. Also, perhaps having a standard reference

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

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

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: Release votes

It seems there has been a bit of a slip in testing as of recently, mostly due to the fact that there's no canonical testing environment that isn't flaky. We probably need to come up with some ideas and a plan on how we're going to do testing in the future, and how we're going to make testing

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

> > 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: Release votes

> > We’ve said in the past that we don’t release without green tests. The PMC > gets to vote and enforce it. If you don’t vote yes without seeing the test > results, that enforces it. I think this is noble and ideal in theory. In practice, the tests take long enough, hardware infra has proven

Release votes

Moving this to it’s own thread: We’ve declared this a requirement multiple times and then we occasionally get a critical issue and have to decide whether it’s worth the delay. I assume Jason’s earlier -1 on attempt 1 was an enforcement of that earlier stated goal. It’s up to the PMC. We’ve

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

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 3) Release Apache Cassandra 3.11.2

+1 On Wed, Feb 14, 2018 at 4:45 PM, Jason Brown wrote: > I ran the unit tests and they are green: > https://circleci.com/gh/jasobrown/workflows/cassandra/ > tree/3.11.2-candidate-2 > > +1. Thanks, Michael. > > On Wed, Feb 14, 2018 at 1:34 PM, Nate McCall

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

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: row tombstones as a separate sstable citizen

Worth a JIRA, yes On Wed, Feb 14, 2018 at 9:45 AM, Carl Mueller wrote: > So is this at least a decent candidate for a feature request ticket? > > > On Tue, Feb 13, 2018 at 8:09 PM, Carl Mueller < > carl.muel...@smartthings.com> > wrote: > > > I'm particularly

Re: [VOTE] Release Apache Cassandra 2.2.12

+1 On 2018-02-13 19:54, Josh McKenzie wrote: +1 On Feb 13, 2018 12:19 PM, "Jason Brown" wrote: +1 On Tue, Feb 13, 2018 at 7:55 AM, Jon Haddad wrote: +1 On Feb 13, 2018, at 7:21 AM, Marcus Eriksson wrote: +1 On Tue, Feb