You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that Cassandra 5.0 is GA, we should be able to stop Cassandra 3.11 builds. For the near term, we should leave the code alone, but remove 3.11 builds and testing in CI and remove 3.11 in the release process (jarfiles and images).
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: MAPI-70
The text was updated successfully, but these errors were encountered:
* [CHANGE] [#556](#556) Update Management API dependencies to address CVEs
* [CHANGE] [#547](#547) Deprecate Cassandra 3.11 support
* [FEATURE] [#551](#551) Add Cassandra 5.0.2 to the build matrix
* [FEATURE] [#549](#549) Add DSE 6.9.3 to the build matrix
* [ENHANCEMENT] [#552](#552) Improve "liveness" probe implementation
* [BUGFIX] [#553](#553) Fix CassandraTaskExports metric filtering to make it work with 5.0.x Major compactions
* [BUGFIX] [#560](#560) Fix LatencyMetrics bucketing on 4.1 and 5.0 as their reservoir stores the data in microseconds, not nano (unlike 3.11 and 4.0)
* [BUGFIX] [#562](#562) Fix version detection
Now that Cassandra 5.0 is GA, we should be able to stop Cassandra 3.11 builds. For the near term, we should leave the code alone, but remove 3.11 builds and testing in CI and remove 3.11 in the release process (jarfiles and images).
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: MAPI-70
The text was updated successfully, but these errors were encountered: