Operator versioning strategy about pravega-operator HOT 1 CLOSED

I would also suggest that we switch to using Git Tags to track and record versions. If we tag with a SemVer such as 0.0.1 the following will give us a simple version number to use.

$ git describe --always --tags --dirty --long
0.0.1-0-g067f261

# Now commit
$ git commit ........
$ git describe --always --tags --dirty --long
0.0.1-1-gfce7ed9

# Now retag
$ git tag 0.1.1
$ git describe --always --tags --dirty --long
0.1.1-0-gfce7ed9

This provides the version number from the tag, plus the number of commits since that tag and finally the actual latest commit meaning we don't need a +git to be appended. What's more we have the version number external to the code AND we mark the source code at the same time.

An example of this approach is Skaffold: https://github.com/GoogleContainerTools/skaffold/blob/master/Makefile#L37

from pravega-operator.