I would rather recommend 2.303.2. Docker images are so popular at the 
moment, I see no reason in separating their versioning from the Jenkins LTS 
releases.
On Monday, August 30, 2021 at 2:26:38 PM UTC+2 [email protected] wrote:

> Would be great if you could announce once it's done. So that people who 
> build images based on it have the chance of triggering a re-build.
> People who use it in Kubernetes might have a problem with the updated 
> images in case they use image pull policy IfNotPresent.
>
>
> Am Mo., 30. Aug. 2021 um 14:09 Uhr schrieb Mark Waite <
> [email protected]>:
>
>> No issue or objection from me to have the 2.303.1 Debian images updated.
>>
>> On Mon, Aug 30, 2021 at 2:34 AM Damien Duportal <[email protected]> 
>> wrote:
>>
>>>
>>> Hello dear developers and maintainers,
>>>
>>> We (the Jenkins Infra team) were recently bitten by a change in the 
>>> latest Docker image for Jenkins controller, in its LTS 2.303.1 (released 
>>> last week).
>>>
>>> The issue is related to a change of locale from "C.UTF-8" to "POSIX" 
>>> when using Debian image (as an upstream change from Debian bullseye).
>>>
>>> A fix has already been made by a user in 
>>> https://github.com/jenkinsci/docker/pull/1194 and is already merge in 
>>> GitHub.
>>>
>>> We (the Jenkins Infra team) would like to rebuild the Docker image for 
>>> the LTS 2.303.1 to avoid our users to be annoyed by this issue.
>>> - It should not imply any tagging version change (as the Docker image 
>>> tags are only about the Core version of Jenkins used, not about the other 
>>> dependencies on the image)
>>> - It should only impact the Debian images (amd64 and arm64)
>>> - It should not impact the weekly (next weekly will have the fix of 
>>> course)
>>> - It should make the image being advertised as updated a few days after 
>>> the official LTS release
>>>
>>> - Is there any issue or counter voice to this change?
>>> - Is there any question or element unclear?
>>>
>>> For the Jenkins infra team
>>>
>>> Damien DUPORTAL
>>>
>>>
>>> -- 
>>> 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/0e3ad65e-9bd7-4074-9fc6-e35328f837dcn%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/0e3ad65e-9bd7-4074-9fc6-e35328f837dcn%40googlegroups.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/CAO49JtFUzjbbxT5jbcFxGW3D52ViNJ3LOwNzeNKFhQOGbEEQnQ%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFUzjbbxT5jbcFxGW3D52ViNJ3LOwNzeNKFhQOGbEEQnQ%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/e46c0a8e-e075-4db9-9974-1c5cf5e07b4en%40googlegroups.com.

Reply via email to