Based on the release lifecycle[1], we should cut another RC until we don’t find
any blocking issues.
Dinesh
[1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=132320437
>
> On Jun 14, 2021, at 9:05 PM, Scott Andreas wrote:
>
> A second RC is appropriate given the revert of
A second RC is appropriate given the revert of CASSANDRA-15899 necessitated by
the discovery of CASSANDRA-16735: Adding columns via ALTER TABLE can generate
corrupt sstables.
Ekaterina and Benedict's statement regarding the true positive rate of flaky
tests also shows the value of resolving the
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. In past releases we have ensured no flaky
tests, I think.
That said, I’ve not had the time to contribute to the fixing of flaky tests, so
I’ll leave the decision to those who have
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
