@rdmark That's not the Gitflow workflow anymore as far as I can tell. I don't think it's a good idea to reinvent the wheel and invent yet another way of versioning, when there are already best practices. IMHO the original text was correct, but when creating the releases the release numbers were wrong and not according to the Gitflow workflow.

As far as I can tell, Gitflow doesn't define what the version numbering should be. Its more how the changes flow between branches.

We have been starting with .1 at the end of the releases as a convention. The last release, I made a bad tag for .1, so I incremented it to .2.

@akuker I mentioned this because https://datasift.github.io/gitflow/IntroducingGitFlow.html uses 1.0 (not 1.0.0) as the first version, and that's exactly the approach used also for the Linux kernels.