how do I pick the latest version that is stable? And what does exp.0 mean? I am not a developer so maybe I misunderstand the “stable” name here under a “latest” label.
I normally just use the latest one and be done with it. Or is it my responsibility to research before any update? I read in another thread that 2.20.6 should be used as that is “stable”. So not 2.20.7 and not 2.20.7-exp.0 which is what I would have chosen.
@mailfraud good day
I wouldn’t pick only by the highest version number. For production, I’d follow the release channel.
exp.0 should be treated as experimental, so I’d avoid it unless you are testing a specific fix. My rule would be stable for production, newer versions in staging first, and experimental builds only in non-critical environments.
Thanks for trying to help everybody. I read the thread shown by @kjooleng . In there Jan says:
No that is correct. 1.22.4 is the latest stable version to be used in production (latest is the tag that gets used by Docker images for that - the latest stable version).
That very latest version we released, which is currently not stable yet, is right now 1.23.0 and tagged in Docker as next.
Besides the older version numbers it implies that “latest” in Docker is something different than “latest” in github.
@tamy.santos You say to follow the release channel. I do. github then shows this:
As you say exp.0 is experimental the name “stable” and the tag “latest” is to ignore then?
I downloaded now the “latest” version via Docker compose as I was following Jans post saying the tag “latest” in Docker is the latest stable one. But I did get the 2.20.7-exp.0 one.
I am confused now. Is that the release channel you mean? Is the version “latest” on github the one I get when pulling via Docker compose - so there is no difference actually? What mistake do I make? Did the Docker source label the exp.0 wrongly as stable?