+1 nb
-Original Message-
From: Mick Semb Wever
Sent: den 10 oktober 2019 07:08
To: dev@cassandra.apache.org
Subject: Re: [VOTE-2] Apache Cassandra Release Lifecycle
> We have discussed in the email thread[1] about Apache Cassandra
> Release Lifecycle. We came up with a doc[2] for
Very powerful tool indeed, thanks for sharing!
I believe it is best to keep tools like this in different repos since different
tools will probably have different life cycles and tool chains. Yes, that could
be handled in a single repo, but with different repos we'd get natural
boundaries.
Thanks! Added you as reviewer on both tickets.
/pelle
-Original Message-
From: Vinay Chella
Sent: den 2 maj 2019 19:10
To: dev@cassandra.apache.org
Subject: Re: Unit test fixes
I can help reviewing these tickets. Thank for bringing up.
On Thu, May 2, 2019 at 9:48 AM Per Otterström
Hi.
The unit tests have been failing/glitching for a while. There are a couple of
patches available that should improve the situation. Would be great if we could
get a couple of reviewers/committers to have a look at them:
https://issues.apache.org/jira/browse/CASSANDRA-15088
https://issues.apac
This is a great initiative! If we can create a structured verification approach
on new and old features I think 4.0 will be up for a good start. Jon, you can
add my team to that signup sheet.
/pelle
-Original Message-
From: Varun Barala
Sent: den 6 september 2018 15:16
To: dev@cassand
say I’m wrong, I’ll believe it - must be imagining restrictions that
don’t exist.
--
Jeff Jirsa
> On Oct 12, 2017, at 10:55 PM, Per Otterström
> wrote:
>
> Hi!
>
> This was news to me. I had the impression that we are maintaining backwards
> compatibility for st
Hi!
This was news to me. I had the impression that we are maintaining backwards
compatibility for streaming non-upgraded sstables. Is that not the case?
However, I believe it is a good idea to run upgradesstables at some point
_before_ upgrading Cassandra next time to make sure there are no old
