Hi,

I am definitely in favor of switching to jdk11 by default, it's really time to 
move forward. We have been using it on the Jenkins infrastructure project for 
almost a year now without major issues but we also had to fine-tune the java 
configuration for java 11.

That remains a major change with potential breaking changes, so I would 
announce it enough in advance so people can already switch to jdk11, and keep 
the java8 for several stable releases with a deprecation warning.



On Wed, Apr 28, 2021, at 6:20 PM, Tim Jacomb wrote:
> Defaults and (people not seeing a need to change)
> 
> Shipping an ‘admin monitor’ encouraging people to update would probably make 
> a difference 
> 
> On Wed, 28 Apr 2021 at 17:18, Tim Jacomb <[email protected]> wrote:
>> It’s just down to defaults I think.
>> 
>> We’ve seen the numbers rise as we changed the website and helm chart to use 
>> Java 11 by default
>> 
>> On Wed, 28 Apr 2021 at 17:08, Daniel Beck <[email protected]> wrote:
>>> 
>>> 
>>> On Wed, Apr 28, 2021 at 1:42 AM Oleg Nenashev <[email protected]> 
>>> wrote:
>>>> I am in favor of making JDK11 the default in all our distributions, 
>>>> including controller and agent Docker images.
>>>> At the same time I am afraid that removal of Java 1.8 support is 
>>>> premature. The vast majority of Jenkins users still uses this version, and 
>>>> the migration to Java 11 won't be seamless in al l cases. For example, 
>>>> Maven Plugin will effectively switch project builds to Java 11 once the 
>>>> agent images are updated. It will cause unexpected issues in user builds 
>>>> here and there. Nothing should be critical, but we should not force users 
>>>> to migrate immediately.
>>>> 
>>>> IMHO there should be a grace period between Java 8 support deprecation and 
>>>> the actual removal. Maybe 6 months or so.
>>> 
>>> Agree; I'd even be more conservative than just six months. We can and 
>>> should update the default Docker images to run on JDK 11. But we shouldn't 
>>> ignore that just ~0.3% of instances use Java 11, let's do something about 
>>> that first. I wouldn't be surprised that there are still some problems to 
>>> work out but we just have no users yet who would be affected.
>>> 
>>> 

>>> -- 
>>> 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/CAMo7PtLW05CwT6JyDHHpq52V%2BZwcRy3hQxPW7O9U-D%3DR1adL7Q%40mail.gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtLW05CwT6JyDHHpq52V%2BZwcRy3hQxPW7O9U-D%3DR1adL7Q%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/CAH-3BicOSJ%2B%3DMhXxO2HRz4QL7O8tm5P56MJhJPsU13z3tTe0og%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicOSJ%2B%3DMhXxO2HRz4QL7O8tm5P56MJhJPsU13z3tTe0og%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/9e55183f-9d5f-4d46-8a0c-0fddf21ebfc0%40www.fastmail.com.

Reply via email to