[
https://issues.apache.org/jira/browse/CASSANDRA-14931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721957#comment-16721957
]
Benedict commented on CASSANDRA-14931:
--------------------------------------
Well, no, this is independently of value. The fact we aren't patching 2.2
often is not necessarily because there are no bugs with 2.2, but that none of
the active committers or community members are any longer testing it. We are
presently embarking on a program of extensive testing, much of which will be
valid for 2.2 as much as for 3.0+. It seems absurd not to, at relatively low
cost, apply the same tests to 2.2 to establish if it has any critical faults.
But, yes, we also want to utilise this for CASSANDRA-14937.
> Backport In-JVM dtests to 2.2, 3.0 and 3.11
> -------------------------------------------
>
> Key: CASSANDRA-14931
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14931
> Project: Cassandra
> Issue Type: Improvement
> Components: Testing
> Reporter: Benedict
> Assignee: Benedict
> Priority: Major
> Fix For: 2.2.14, 3.0.18, 3.11.4
>
>
> The In-JVM dtests are of significant value, and much of the testing we are
> exploring with it can easily be utilised on all presently maintained
> versions. We should backport the functionality to at least 3.0.x and 3.11.x
> - and perhaps even consider 2.2.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
