For new feature work on trunk, targeting the highest supported language level featureset (jdk17 right now, jdk21 within the next couple of weeks) makes sense to me. For bugfixing, targeting the oldest supported GA branch and the highest language level that works there would allow maximum flexibility with minimal re-implementation.
If anyone has any misgivings with certain features (i.e. the debate around usage of "var") they can bring it up on the dev ML and we can adjust, but otherwise I'd prefer to see us have more modern evolving options on how contributors engage rather than less. On Fri, May 9, 2025, at 1:56 AM, Vivekanand Koya wrote: > Hello, > > I want to understand the community's thoughts on using newer features (post > JDK11) in upcoming releases in Cassandra. An example is flow scoping instead > of explicitly casting types with instanceOf: https://openjdk.org/jeps/395. I > want your thoughts on JDK requirements for the main Cassandra repository, > Accord, and Sidecar. > > Much appreciated. > Thanks, > Vivekanand K.
