Branch: refs/heads/stable-2.426
Home: https://github.com/jenkinsci/jenkins
Commit: f0846d9797b85fa3369a267cd8045211314640b7
https://github.com/jenkinsci/jenkins/commit/f0846d9797b85fa3369a267cd8045211314640b7
Author: Basil Crow <m...@basilcrow.com>
Date: 2023-11-26 (Sun, 26 Nov 2023)
Changed paths:
M pom.xml
M war/pom.xml
Log Message:
-----------
[JENKINS-72266] Upgrade Winstone from 6.14 to 6.16 (upgrade Jetty from
10.0.17 to 10.0.18 (#8666)
[JENKINS-72266] Upgrade Winstone from 6.14 to 6.16 (upgrade Jetty from 10.0.17
to 10.0.18)
(cherry picked from commit d3295776738cb4675161e71c992777b4605991e8)
Commit: a190edf08212d87fc1ed238e96ed64f529abdefa
https://github.com/jenkinsci/jenkins/commit/a190edf08212d87fc1ed238e96ed64f529abdefa
Author: Mark Waite <mark.earl.wa...@gmail.com>
Date: 2023-11-26 (Sun, 26 Nov 2023)
Changed paths:
M
core/src/main/java/jenkins/monitor/JavaVersionRecommendationAdminMonitor.java
Log Message:
-----------
[JENKINS-72252] Warn 12 months and 3 months before end of Java support (#8661)
Show Java version admin monitor at 12 months and 3 months
Daniel Beck described his recommendation to alert users at 12 months
and at 3 months prior to the end of support of a Java version.
He wrote:
> The second warning in particular needs to strike a balance between
> being shown late enough so it's actually relevant for whoever hasn't
> acted yet, while being shown early enough that slightly more elaborate
> environments (difficult to schedule maintenance windows) are informed
> in time. 3 months aligns rather nicely with the LTS schedule where
> we kinda expect folks to do that anyway.
>
> 18/9, or even 12/6 errs too far on the side of those for whom this is
> extreme effort (and who dismissed the first message more appropriate for
> their environment!), while showing everyone else completely irrelevant
> notices they won't care about for many months to come.
https://github.com/jenkinsci/jep/pull/400#discussion_r1371510566 provides
more details.
The Java 8 to Java 11 transition saw a significant change in adoption of
Java 11 once the admin monitor was visible to users. That was shown
slightly over 12 months before the release that required Java 11.
This change continues that pattern of 12 months warning before end
of support.
https://github.com/jenkinsci/jep/pull/400#discussion_r1375623888 has a
graph that shows the adoption curves for Java 8, Java 11, and Java 17.
(cherry picked from commit aeb64c0c3d097131b3f59d7fe9d1cce1f41de336)
Commit: abe7181b63a705033b48e09823bfaf6ce18cd4ae
https://github.com/jenkinsci/jenkins/commit/abe7181b63a705033b48e09823bfaf6ce18cd4ae
Author: Alexander Brandes <mc.ca...@web.de>
Date: 2023-11-27 (Mon, 27 Nov 2023)
Changed paths:
M
core/src/main/java/jenkins/monitor/JavaVersionRecommendationAdminMonitor.java
M pom.xml
M war/pom.xml
Log Message:
-----------
Merge pull request #8721 from
krisstern/feat/stable-2.426/backporting-2.426.2-1
Backporting for 2.426.2
Compare:
https://github.com/jenkinsci/jenkins/compare/5e97678698d6...abe7181b63a7
--
You received this message because you are subscribed to the Google Groups
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-commits+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-commits/jenkinsci/jenkins/push/refs/heads/stable-2.426/5e9767-abe718%40github.com.
