Hi, from what I observer during many of these discussion a huge part of the reluctance to update stems from the fatc, that (historical) there is not enough distiction between the java version used to run jenkins and the version used to really build java projects. I think that could warrant a bit more epxlanation that you can build projects in any java version you like, even if jenkins is running in another version. Then mainly some proprietary or unmaintained plugins are left as a problem for upgrades (but will those users really upgrade core anyway?)
Björn [email protected] schrieb am Mittwoch, 17. November 2021 um 23:50:05 UTC+1: > Agreed that the benefit to developers is a critical point. For Java 8 bump > <https://groups.google.com/g/jenkinsci-dev/c/fo5nKLhZK5U/m/Zb9jHpBJBQAJ> > that was a big driver. We do want Jenkins to be appealing to the OSS Java > developers out there. > > I think we should plan & announce ahead like we've done for Java 8 [1] > <https://www.jenkins.io/blog/2015/11/03/what-jvm-versions-are-running-jenkins/> > > [2] > <https://www.jenkins.io/blog/2016/11/22/what-jvm-versions-are-running-jenkins-the-return/> > > [3] > <https://www.jenkins.io/blog/2017/01/17/Jenkins-is-upgrading-to-Java-8/> > [4] > <https://www.jenkins.io/blog/2017/04/10/jenkins-has-upgraded-to-java-8/>, > like saying we'll bump to Java 11 as min version some time in (late?) 2022, > blog about it etc. > > > > > Le mer. 17 nov. 2021 à 14:39, 'Jesse Glick' via Jenkins Developers < > [email protected]> a écrit : > >> On Wed, Nov 17, 2021 at 4:03 AM 'Daniel Beck' via Jenkins Developers < >> [email protected]> wrote: >> >>> […] do not show a rapid growth of Java 11 adoption >>> >>> >> Every time this topic comes up I need to remind people that while the >> proportion of installations currently running 8 vs. 11 is an interesting >> datum, it is not particularly useful for making a decision about when to >> drop support for 8. So long as you *can* run Jenkins on 8, and you were >> doing so before, and 8 is still receiving security fixes, and there is no >> particular functionality which is only available on 11 or even runs better >> in any way that I am aware of, why would you bother to even take five >> minutes to switch to a different Java version? >> >> What needs to be weighed is on the one hand the advantage to Jenkins >> *developers* in requiring 11 (as Tim describes); and on the other hand >> the proportion of Jenkins administrators who would *refuse* to upgrade >> Jenkins if it meant switching to 11 (for example because of some dumb >> enterprise policy, or because of lack of support for agents on exotic >> platforms). >> >> -- >> > 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 on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1%3D2tCML%2BOYBgXmrmX2SD4_oxGDgL%2B7Fv_28S5hod9bHg%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1%3D2tCML%2BOYBgXmrmX2SD4_oxGDgL%2B7Fv_28S5hod9bHg%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2454fe7f-8678-4dc9-9126-22df094fe654n%40googlegroups.com.
