> Technically it can be two commits which would be merged / pushed at once.
I'll prepare a new pull request containing both of the changes. My
previous experience says me that it's really hard to find a reviewer
who will be able to go through huge pull requests, that's why
initially I've split thi
> com.carrotsearch.randomizedtesting.randomizedtesting-runner 2.1.2 - test
> dependency
Can you talk more about why? There are several ways to do random testing
in-tree ATM, so wondering why we need another one
> On Dec 8, 2022, at 6:51 AM, Mike Adamson wrote:
>
> Hi,
>
> I wanted to discu
Thanks for the extra time to investigate. Unfortunately no progress on
finding the root cause for this issue, just successful bootstraps in our
attempts to reproduce. I think highlighting the ticket in the release notes
is sufficient and resolving this issue should not hold up the release.
I agree
I’m unsure that without more information it is very helpful to highlight in
the release notes. We don’t even have a strong hypothesis tying this issue to
4.1.0 specifically, and don’t have a general policy of highlighting undiagnosed
issues in release notes?
> On 13 Dec 2022, at 00:48, Jon Me
I agree Benedict - I don't think we can provide a clear advisory to our users,
so I would approve of not sharing anything in the release notes. But if someone
posts an issue (likely to the user ML) related to streaming / bootstrapping on
4.1.0, then we should engage with the knowledge that it mi
Proposing the (second) test build of Cassandra 4.1.0 for release.
>
> sha1: f9e033f519c14596da4dc954875756a69aea4e78
> Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.1.0-tentative
> Maven Artifacts:
> https://repository.apache.org/content/repositories/orgapachec
