Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Domino 14 has Java 17, which is good, but the timing of things meant that that's no longer the current LTS. It makes sense that Domino wouldn't move to 21 for in R14, but it'll be important to avoid another situation like what happened with Java 6 and 8, where Domino lags far behind current Java versions up until the point where it's completely untenable.
The next Jakarta EE version targets 21 as a minimum, and I expect other projects to follow suit: it seems that it's becoming more culturally normal for frameworks and libraries to be fairly aggressive about bumping up JVM requirements. Domino should follow suit, and ideally have a known planned timeline.