Stable docker tag

[AlbanDurrheimer]

I have been caught several times by updating my Dolibarr instance too quickly with versions containing bugs (mainly with major version changes).

Therefore, it would be wise to create a stable tag that corresponds to the latest version considered free of major bugs. (Nowadays, I always wait for 2 or 3 corrective updates before updating my instance).

[creekorful]

Hello,

Why not simply use a fixed version? This way you ensure no improper update will be deployed to you without you knowing.

I am not against stable version but this will need some discussion as how to qualify a stable version.

Cheers

[AlbanDurrheimer]

Hello,

Why not simply use a fixed version? This way you ensure no improper update will be deployed to you without you knowing.

That's what I'm currently doing, but it's inconvenient on several levels. It forces us to regularly check if an update is available, and it prevents us from using automation systems like Watchtower.

Many projects have already implemented the stable tag (e.g., Nextcloud), and I find it very useful.

Best

[mathieupotier]

Hi @AlbanDurrheimer

Maybe we should think enforcing test for the docker part itself, but adding a "stable" version could lead to misunderstanding : not dolibarr stable, but docker's ...

Maybe something like docker tags : stable-20.0.3, stable-20 or rc-20.0.3 when dealing with the dockerfile itself, but it breaks semver in some points ... making upgrade a little bit more complicated on consumer end ...

We must find a way to add version of docker image in addition to the main dolibarr version embedded (which could also break on his own ...)

Really complicated subject in fact ... than just adding a stable tag ^_^

[creekorful]

Hello @AlbanDurrheimer @mathieupotier,

Why not use the "latest" tag directly?

This tag points to the latest release. See:

dolibarr-docker/versions.sh

Line 9 in f5c5f7b

DOLIBARR_LATEST_TAG="21.0.0"

Each time Dolibarr cut a new version, latest point to it.

[AlbanDurrheimer]

Hello @creekorful,

It is not always advisable to follow the latest versions directly, as they may contain bugs. After more than three years of using Dolibarr, I have learned the hard way that it is better to wait for at least the third patch update before upgrading to a new major version.

The advantage of having a "stable" tag is that it allows for automated updates (for example, using a tool like Watchtower) without requiring manual intervention, while reducing the risk of deploying a faulty version, as the major issues would have already been solved.

[creekorful]

According to ldestailleur every release is stable... o:)

Joke asides, I understand your point now. Well adding such stable tag would be fairly easy but we first need to have a consensus about what release is considered stable and what is not.

As per your definition is would be any release with patch version >= 3 but I feel other people may have a different opinion.

Any opinion on this @eldy? How can we decide whether a Dolibarr release is stable enough for production deployment?

Cheers,

[AlbanDurrheimer]

As mentioned before, I personally wait for the third patch release to consider Dolibarr stable. However, this is indeed quite relative.

I believe we can consider a version stable when the latest release is at least 2 months old (which provides enough time to confirm version stability) and no immediate patch release is planned.