On Wed, Mar 4, 2026 at 2:20 PM Ullrich Hafner <[email protected]> wrote:
> As a side note: when are we planning to switch the BOM builds from Java 17 > to Java 21? When I understand correctly, as soon as we have Java 21 > plugins, these will break the BOM because they cannot be built with Java 17 > anymore. > I think that BOM builds will switch from Java 17 to Java 21 in a series of steps, with the final step occurring around September 30, 2026. Jenkins plugins should not require Java 21 until they require Jenkins 2.545 or newer because Jenkins core does not require Java 21 until version 2.545. The next LTS baseline has been proposed as 2.553. Jenkins 2.553.1 is scheduled for release on April 15, 2026. When the plugin BOM adds the Jenkins 2.553.x line, that line of the plugin BOM will need to use Java 21. However, the preceding lines of the plugin BOM do not need to use Java 21 and should not use it, lest they fail to detect incompatibilities in a plugin. I think that we should allow the usual process to work in this case. We will release Jenkins 2.553.1 April 15, 2026 and it will require Java 21 for the 2.553.x line in the plugin BOM. We will drop the 2.516.x at that time, but the 2.528.x line and the 2.541.x line will continue to compile and test with Java 17. July 8, 2026 we will release ".1" of the next LTS baseline and will drop the 2.528.x line. Sep 30, 2026 we will release the ".1" of the "next-next" LTS baseline and will drop the 2.541.x line. At that point, the plugin BOM will build entirely with Java 21. 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/CAO49JtGecr%3Drzx1xh9uFMw8xKob2xcZdAD-F0eNY65pOyDNLiA%40mail.gmail.com.
