Hi all, I've created a task to mark JDK 17 as production-ready for Cassandra 5.0 in our documentation - CASSANDRA-20681 <https://issues.apache.org/jira/browse/CASSANDRA-20681>
Reasons: - Cassandra 5.0.x has had four bugfix releases and is stable (5.0.0 was released in September 2024, so it's been out for eight months). - I'm not aware of any open Cassandra issues specific to JDK 17. - Our CI has been running tests with JDK 17 on every commit for over a year. - JDK 17 is a mature LTS version. We already have a newer LTS (JDK 21), and JDK 24 has already been released. - There might be a vicious cycle here: we’re waiting for more user feedback, while users are waiting for the feature to be marked as non-experimental before adopting it more widely. Any objections to marking JDK 17 as production-ready for 5.0? Related threads where the topic about JDK17 status has been raised: - https://the-asf.slack.com/archives/CK23JSY2K/p1744313849439569 - https://the-asf.slack.com/archives/CJZLTM05A/p1746787244618429 - https://lists.apache.org/thread/np70b8ck21k0ojsjnotg3j9p2rrj29dp - https://stackoverflow.com/questions/79563058/java-17-support-for-cassandra-5 -- Dmitry Konstantinov
