On Sat, Dec 13, 2025 at 6:04 AM Ullrich Hafner <[email protected]> wrote:
> > I think we should not wait another four months, we are already late in our > plan: > [image: Figure 4] > > We agreed in a long discussion to switch to Java 21 this year and that > already was a compromise (actually we planned to switch to Java 21 right > after the drop of Java 11). So I think we should stick to that plan (that > has been accepted by the Governance board) and drop Java 17 the next weekly > after the next LTS baseline switch. This is already later than planned. I > also did not hear any complaint from users that still want to use the Java > 17 runtime so why should we wait for that step again. Java 21 support ist > already available for two years now. > > When you say that we should "drop Java 17 in the next weekly after the next LTS baseline switch", I assume you mean 2.541 as the next LTS baseline switch. The 2.541.1 release is scheduled for Jan 21, 2026. If that assumption is correct, then I think that your idea matches mine. The 2.541.1 LTS will support Java 17 because 2.541 weekly supports Java 17. Weekly releases after 2.541 can drop support for Java 17 so that the LTS baseline selected on March 4, 2026 will not support Java 17. Someone (who?) can submit the pull requests necessary to drop Java 17 support from a Jenkins weekly release after 2.541. The new LTS baseline that releases on April 15, 2026 would be the first LTS to drop support for Java 17. Mark Waite -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFoqqx_8RBca0kurV_UJMHaJeZ%2B%3DZe0TsukDgcir8wj0g%40mail.gmail.com.
