: Re: Are we ready for 4.0.0 (GA) ?
>
> We do have to cut another RC given the seriousness of CASSANDRA-16735
> though, right?
I do not disagree with that. I just would like to see us more precise with
our expectations for releasing 4.0 GA, considering that we have already
deeply tested
a new logo 😊
>
> Still, not disputing the need to ship GA soon. We do have to cut another
> RC given the seriousness of CASSANDRA-16735 though, right?
>
>
> From: Benjamin Lerer
> Date: Tuesday, 15 June 2021 at 11:14
> To: dev@cassandra.apache.org
> Subject: Re: Are we r
2021 at 11:14
To: dev@cassandra.apache.org
Subject: Re: Are we ready for 4.0.0 (GA) ?
As the list of flaky tests was filtered out I wanted to add some
information about the test that revealed real issues. First there was a
mistake: only 3 of the issues were revealed by flaky tests. The other one
was
es they're deploying, as heavy
> contributors doing so provides us the best opportunity to catch these
> issues before our users do.
> >
> > We're getting close.
> >
> >
> > From: bened...@apache.org
> > Sent: Monday, June 14, 2021 3:03 PM
&
ides us the best opportunity to catch these issues before our
> users do.
>
> We're getting close.
>
> ________
> From: bened...@apache.org
> Sent: Monday, June 14, 2021 3:03 PM
> To: dev@cassandra.apache.org
> Subject: Re: Are we ready for 4.0.0 (GA) ?
>
>
users do.
We're getting close.
From: bened...@apache.org
Sent: Monday, June 14, 2021 3:03 PM
To: dev@cassandra.apache.org
Subject: Re: Are we ready for 4.0.0 (GA) ?
A rate of 4/30 is a rate of 13% true bugs, which worries me with respect to our
promise of shipping a bug-free GA
have, or otherwise have a strong opinion.
From: Ekaterina Dimitrova
Date: Monday, 14 June 2021 at 20:51
To: dev@cassandra.apache.org
Subject: Re: Are we ready for 4.0.0 (GA) ?
To give some context around the flaky tests, I pulled a quick report for the
fixed ones during the past two months. It is
To give some context around the flaky tests, I pulled a quick report for
the fixed ones during the past two months. It is attached for your
reference.
To summarize, in two months 30 tickets for flaky tests were closed and only
4 of them were Cassandra bugs(marked in red in the report), the rest of
To the point of "long-term observability over flakies":
I will mention here that we intend to deploy a tool called Butler that we
have developed and used internally for a while. It compliments Jenkins to
present different views of test results, allowing developers to better
ascertain those tests t
Are we ready to cut 4.0.0 (GA) once the following tickets land?
CASSANDRA-16733 – Allow operators to disable 'ALTER ... DROP COMPACT
STORAGE' statements"
CASSANDRA-16669 – Password obfuscation for DCL audit log statements
CASSANDRA-16735 – Adding columns via ALTER TABLE can generate corrupt
sst
10 matches
Mail list logo
