You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some people tend to think this is a bad practice, because you can easily shoot yourself in the foot by upgrading without realising it. Using explicit version tags is usually preferred.
In addition, when we do releases on stable branches (like 6.1.2 today), we also update the "latest" tag. It means that as we release new and stable versions, the "latest" tag might point to 6.1.2, then 6.2.0, then 6.1.3... This can be confusing.
We currently publish a "latest" tag on the docker hub: https://hub.docker.com/r/ihatemoney/ihatemoney
Some people tend to think this is a bad practice, because you can easily shoot yourself in the foot by upgrading without realising it. Using explicit version tags is usually preferred.
In addition, when we do releases on stable branches (like 6.1.2 today), we also update the "latest" tag. It means that as we release new and stable versions, the "latest" tag might point to 6.1.2, then 6.2.0, then 6.1.3... This can be confusing.
@youegraillot do you have an opinion about this?
Also, how can we deprecate this tag without breaking the workflow of people using it?
The text was updated successfully, but these errors were encountered: