> 1) Would it make sense to keep the last âstableâ of each main version around?
Yes. I plan to always have a version number tag, too. This won't go
away, once builds for that version aren't updated any more.
> 2) The scheme does not include the âlatestâ tag, which is the default tag. This should be equal to the âstableâ tag. Therefore, when no tag is specified, the âstableâ (âlatestâ) will be used.
I tried to avoid latest, as it's been the source of confusion the short
past we've already had. You'd expect it to be "stable", I'd expect it to
be "dev". Some would expect it to point to the latest image built, no
matter what LMS version is in there... See eg.
https://vsupalov.com/docker-latest-tag/ for more discussion around it.
--
Michael
Yes. I plan to always have a version number tag, too. This won't go
away, once builds for that version aren't updated any more.
> 2) The scheme does not include the âlatestâ tag, which is the default tag. This should be equal to the âstableâ tag. Therefore, when no tag is specified, the âstableâ (âlatestâ) will be used.
I tried to avoid latest, as it's been the source of confusion the short
past we've already had. You'd expect it to be "stable", I'd expect it to
be "dev". Some would expect it to point to the latest image built, no
matter what LMS version is in there... See eg.
https://vsupalov.com/docker-latest-tag/ for more discussion around it.
--
Michael