+1 for moving Java 11 support out of experimental for 4.0 at minimum, and no concern with doing so for 3.0/3.11 if someone were to propose.
I and contributors I work with have deployed 4.0 + JDK11 in production, have found no issues, and would treat any issues that arise as ones we’re able to jump on and contribute development + review resources to resolve in the project. No JDK11-specific bugs to report, though users should of course test their ancillary tooling for compatibility. As an example, a change in the File API in Java 10 altered the precision of filesystem timestamps as returned by the API, so users upgrading from 8 to 11 who have a dependency on timestamp identity may want to examine it. That JDK change was: https://bugs.openjdk.java.net/browse/JDK-8177809 — Scott --- Mobile On Aug 26, 2021, at 7:35 AM, Ekaterina Dimitrova <e.dimitr...@gmail.com> wrote: Hi everyone, I had a few people asking me recently about the Java 11 support. I came across this thread we had last year - https://lists.apache.org/thread.html/r38f6beaa22e247cb38212f476f5f79efdc6587f83af0397406c06d7c%40%3Cdev.cassandra.apache.org%3E . I think we have all tests running in both Java 8 and Java 11 for trunk and cassandra-4.0 in both Jenkins and CircleCI. Does anyone know about any Java 11 specific bugs discovered? I personally haven't heard of any in the past year. What is the plan of the community for moving Java 11 support out of experimental? Also, Java 17 LTS GA is planned for Sepember 2021 and I can try to test it with trunk. Any thoughts? Last but not least, do we know anyone running Java 11 in production? This thread was really opened as a stage to share our thoughts and hopefully come up with a plan as a community. Looking forward to seeing what people think here. Thank you, Ekaterina
