2.541 as 21 Jan 2026 LTS baseline

53 views
Skip to first unread message

Jenkins Developers

unread,
Dec 10, 2025, 4:13:09 PM (5 days ago) Dec 10
to Jenkins Developers
It is time to choose the next LTS baseline.  The first release of that LTS baseline is scheduled for 21 Jan 2026.

I recommend Jenkins 2.541, released today.  Includes security fixes.

Mark Waite

Ullrich Hafner

unread,
Dec 12, 2025, 3:57:39 AM (4 days ago) Dec 12
to Jenkins Developers
Isn’t it also time to switch the Java baseline to JDK 21 now?

--
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 jenkinsci-de...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/c8621edf-27e2-48fd-bba4-3dcd1456732cn%40googlegroups.com.

Kris Stern

unread,
Dec 12, 2025, 4:59:15 AM (3 days ago) Dec 12
to Jenkins Developers
I would second that, as the Java JDK baseline should definitely be shifted to 21...

Best,
Kris

From: jenkin...@googlegroups.com <jenkin...@googlegroups.com> on behalf of Ullrich Hafner <ullrich...@gmail.com>
Sent: 12 December 2025 16:57
To: Jenkins Developers <jenkin...@googlegroups.com>
Subject: Re: 2.541 as 21 Jan 2026 LTS baseline
 

Tim Jacomb

unread,
Dec 12, 2025, 6:19:31 AM (3 days ago) Dec 12
to jenkin...@googlegroups.com

Jenkins Developers

unread,
Dec 12, 2025, 6:20:36 AM (3 days ago) Dec 12
to Jenkins Developers
On Friday, December 12, 2025 at 1:57:39 AM UTC-7 Ullrich Hafner wrote:
Isn’t it also time to switch the Java baseline to JDK 21 now?


That's a very good question.  The Java 17 end of life administrative monitor that we display to Java 17 users  says that support for Java 17 will end March 31, 2026.  If we want the first LTS baseline that releases after March 31, 2026 to drop support for Java 17, then we need to start the work in Jenkins weekly now so that it can be available in a Jenkins weekly release before the next LTS baseline is selected.  The next LTS baseline is scheduled to be selected March 4, 2026.

Do we think that we can complete the work to drop support for Java 17 from Jenkins weekly before March 4, 2026?

Mark Waite

Tim Jacomb

unread,
Dec 12, 2025, 12:45:48 PM (3 days ago) Dec 12
to jenkin...@googlegroups.com
> Do we think that we can complete the work to drop support for Java 17 from Jenkins weekly before March 4, 2026?

Yes, that should be fine.

--
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 jenkinsci-de...@googlegroups.com.

Ullrich Hafner

unread,
Dec 13, 2025, 8:04:57 AM (2 days ago) Dec 13
to Jenkins Developers
Java 17 users  says that support for Java 17 will end March 31, 2026

This is the support for Java from Oracle, but not our support. 

I think we should not wait another four months, we are already late in our plan:
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. 

Ulli


Mark Waite

unread,
Dec 13, 2025, 9:04:26 AM (2 days ago) Dec 13
to jenkin...@googlegroups.com
On Sat, Dec 13, 2025 at 6:04 AM Ullrich Hafner <ullrich...@gmail.com> wrote:

I think we should not wait another four months, we are already late in our plan:
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

Ullrich Hafner

unread,
Dec 14, 2025, 6:42:18 AM (yesterday) Dec 14
to Jenkins Developers
Maybe we should not use dates and discuss weekly release numbers;-) I was irritated about your March deadline.

I am fine with using 2.541 as latest baseline for the LTS that supports Java 17. 
Weekly releases 2.54x where x is 2, 3 or another small number should switch to Java 21 as baseline (whenever a PR has been created, is there a similar PR available for the Java 11 -> Java 21 switch?). We should not wait for March to make the transition to have time to fix potential problems.

That means, plugins can start to switch to Java 21 soon when they use this new Java 21 Jenkins weekly baseline version. 

--
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 jenkinsci-de...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages