Suggestion for semver tag and release convention to use `v1.1.1` about golang-action

[cedrickring]

So we keep the major.minor.patch versioning for Docker?

You also could do a 'just-in-time' release branch model where the tag is done on master and only when you need to specifically hotfix do you create the release branch:

Does GitHub support overwriting tags? So the Docker versioning could apply to GH aswell. You could specify only e.g. v2 in your main.workflow and get all the latest minors and patches too.

This maybe relates to this issue aswell: Can we add some script to automatically update the README.md when a new release happens? Something like: replace all vx.x.x with the latest version.

[dougnukem]

Yes you can overwrite the git tags to match that versioning scheme, but I think the best process is to treat tags as immutable, and just re-tag the same ones as vX.Y.Z

• v1.0.0
• v1.1.0
• v1.1.1

I think it'd could make sense to use the docker versioning scheme and force tags for minor/patch updates:

• v2
• v2.1

[dougnukem]

Also i think while it's in master the process should be that things are tagged/re-tagged as:
v1.2.0-develop - indicating the "next" version that will be released

We can add that to the Makefile process and update Readme and Dockerfile accordingly.