> Infrastructure
> I have noticed that there is a need for infrastructure to run automated
> tests for Cassandra. We'd like to help so that the tests can be run
> regularly with a reasonable running time. We believe that 15 m4.2xlarge
> [3] EC2 instances could help accomplish this, and we'd
And I sent this without saying when. Let me save you a click on the
confluence link.
January 21, 1PM PST
On Mon, Jan 13, 2020 at 5:28 PM Patrick McFadin wrote:
> Hi everyone,
>
> In order to catch up on what's happening here, here's the establishing
> thread:
>
Hi everyone,
In order to catch up on what's happening here, here's the establishing
thread:
https://lists.apache.org/thread.html/aa54420a43671c00392978f2b0920bc6926ca9ba1e61a486ad39fb21%40%3Cdev.cassandra.apache.org%3E
Key points that Scott Andreas proposed in the initial email was
Motivation
Hi Almero,
Great to see your interest in contributing to the project. Currently, the
Apache Cassandra community is in a code freeze[0] to ensure that we stabilize
Cassandra 4.0 so the focus is going to be on testing. Here's a blog post[1] on
how we're validating Cassandra. Anything that your
Hi Cassandra devs,
My name is Almero Gouws, I am the head of engineering for Amazon Managed Apache
Cassandra Service (MCS). My team and I are eager to begin contributing to
Apache Cassandra, and I want to share some of the contribution ideas we have
planned. The goal of this thread is to get
> If I don't hear any objection, I'll commit this. Off this, as it
> aggregates test reports, it's now possible to start test posting emails
> with the test report summary, as well as bringing in the dtest builds
> into the pipeline.
Based on the pipeline approach I've gotten notifications
