Latest should only be used for stable releases, not for release candidates, in
my opinion. Users often just use the latest tag (or no tag at all which
implicitly uses latest then) and expect that they will simply get the latest
official release with that.
Our current configuration also uses that approach. The execution
"docker-image-tag-latest" has this configuration [1]:
<skip>${only.when.is.prerelease.version}</skip>
So, we only tag images as latest if the version is not a prerelease version.
The same applies to tags like 3.4 and 3.3. Prereleases will only be tagged with
their exact version, e.g., 3.4.1-rc1.
[1]:
https://github.com/apache/tinkerpop/blob/e81280836feed5df8d6adc8f3a03d09988282ea5/gremlin-server/pom.xml#L302
-----Ursprüngliche Nachricht-----
Von: Stephen Mallette <[email protected]>
Gesendet: Dienstag, 26. Februar 2019 21:01
An: [email protected]
Betreff: latest and rc version
Florian, I suppose this question is for you, but if anyone else knows that's
fine....For DockerHub, what will the "latest" tag and "intermediate"
tags (for lack of a better term - by intermediate i mean 3.4, 3.3, etc).
point to if we were to publish a release candidate? so if we published
3.4.1-rc1 will that put "latest" and "3.4" on that version or will it stay with
the official version at 3.4.0?
