Version scheme

[stojad]

If you want a basic versioning strategy, this is the approach I use based on GitFlow branching and SemVer 2.0.0:

1. Merges to master build a release with version major.minor.build, where the major.minor tuple is the current stable release version (generally maintained as a branch-specific variable in your CI tool of choice), so build 3 of release 1.0 would be 1.0.3. This allows you to use merges of post-release bugfix branches back into master to auto-increment the patch number for bugfix releases.

2. Merges into dev follow a similar pattern as master, except the build version is major.minor.0-branch.build, so pre-release builds are tagged with the non-master branch they came from. Say dev is the active development branch for my next minor release, then I set major.minor to 1.1 for dev, then build 5 of my dev branch would be 1.1.0-dev.5.