[wildfly-dev] Re: Better synergies for WildFly Container images
On Fri, Nov 4, 2022 at 7:14 AM Jean-Frederic Mesnil <jmesnil(a)redhat.com>
wrote:
On 3 Nov 2022, at 12:59, Jean-Frederic Mesnil <jmesnil(a)redhat.com> wrote:
I’m not planning to publish the latest tag anymore if we provide multiple
jdk versions.
Actually I changed my mind on this and I think we should continue to
provide a latest tag.
The caveat with that floating tag is that it would point to the baseline
JDK version that we provide. For example for upcoming images that will be
built with JDK 11 and JDK 17, “latest” will point to “latest-jdk11”.
That seems odd to me. If we're going to continue to have 'latest' it seems
intuitive it would mean 'latest JDK' as well.
I get keeping 'latest' as 'JDK 11' for compatibility, and maybe that's
fine
right now as these changes haven't been socialized widely. But if we do
that I think we should also announce that at point XXX (some time soon) the
meaning of 'latest' will change to 'latest supported JDK'.
We might continue producing SE 11 images for a long time, but really people
should be using SE 17.
So the “latest” tag can be used to pull the image as usual.
But if/when we decide to stop producing JDK 11 images, the latest tag
would then point to latest-jdk17 (without notice).
I’d recommend to use the new latest-jdk11 and latest-jdk17 to avoid such
surprises if you want to stick to a given JDK version.
I’ve updated my PR to reflect this change at
https://github.com/jboss-dockerfiles/wildfly/pull/164
<https://github.com/jboss-dockerfiles/wildfly/pull/164/commits>
Best regards,
Jeff
--
Jeff Mesnil
Principal Software Engineer
Red Hat
http://jmesnil.net/
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
He/Him/His
Attachments:
- attachment.html (text/html — 5.0 KB)