[
https://issues.apache.org/jira/browse/CASSANDRA-18831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17940662#comment-17940662
]
Josh McKenzie commented on CASSANDRA-18831:
-------------------------------------------
My guess is we're going to:
# Have accord merge
# Then I'll panic and rush to get this merged
# Then we'll freeze and qualify the release
So it's less about dates or a release train at this point and more about
features, at least for this iteration.
That's just how I read the tea leaves; we don't have consistent calendar-based
release dates as a project at this time.
The 5.x denotes "next major", so it'll either be 5.1 or 6.0. I think we
discussed bumping to 6.0 given the magnitude of impact of accord and JDK compat
breaking changes.
> JDK21 support
> -------------
>
> Key: CASSANDRA-18831
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18831
> Project: Apache Cassandra
> Issue Type: Task
> Components: Build
> Reporter: Achilles Benetopoulos
> Assignee: Josh McKenzie
> Priority: Normal
> Fix For: 5.x
>
> Attachments: jdk21-patch
>
>
> This patch builds on the work in CASSANDRA-16895 that added JDK17 to the list
> of supported Java versions, and extends that work to enable building and
> running Cassandra under JDK21.
> The following commits comprise the changes included in the attached patch:
> -
> [https://github.com/apache/cassandra/commit/b15d4d6980e787ab5f3405ca8cb17a9c92a4aa47]
> -
> [https://github.com/apache/cassandra/commit/0c5df38dafe58bfec8924e81507bb604e1543897]
> -
> [https://github.com/apache/cassandra/commit/6506b7279d98eed4b2b65b71e0c6f41eb78c6913]
> -
> [https://github.com/apache/cassandra/commit/564cbd534c5a975cda0c629c14c68c8745b41451]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
