ChrisHegarty opened a new issue, #14229: URL: https://github.com/apache/lucene/issues/14229
This issue has been filed to help facilitate and track a discussion relating to bumping the minimum compile Java version. Currently the minimum compile version is Java 21, for both active development branches: `main` and `branch_10x`. Since Lucene 10 has already shipped artifacts compiled with class file version 65.0 (Java 21), then there is no suggestion to change this in any of the 10.x releases. Users of Lucene 10.x will continue to be able to run on a version of Java that is as low as Java 21. A few consideration points: 1. At time of writing, Java 21 is the most recent LTS (Long Term Support) release. 2. Java 25 is intended to be the next LTS release (scheduled for Sep 2025). 3. Lucene infrastructure has the ability to support newer than the minimum compile version, in the form of an api jar and MRJar. 4. While not strictly necessary, Lucene releases will always minimally target a class file version associated with an LTS Java release - likely the most recent LTS. It's extremely problematic for users to do otherwise. 5. Build and infrastructure dependencies will need to "keep up", or prevent us adopting the absolute most recent Java version. Assuming that a future Lucene 11 will not ship before Java 25 is released, then it seems safe to bump the minimum compile version of the `main` branch to the latest Java version, e.g. Java 23. With the intention of continually bumping it when appropriate, until it hits Java 25. This allows Lucene developers to take advantage of newer Java features, but means that we cannot release Lucene 11 before September 2025 (which seems fine). As a general guideline, bumping the minimum Java compile version in the `main` branch might be acceptable (or not), but in this particular case, given the times/dates outlined above, it does seems ok to do now - with the intention of eventually tying Lucene 11 to a class file version 69.0 (Java 25). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
