Should I increase versions after a release or with every commit
semantic-versioning, version, version-control
Solution
Version does not depend on how many functions you have written in that particular release. If your current version is 1.0.0 ,then it should be 1.0.1 or 1.1 depend upon your naming rule that you have put for your product and dependencies.
Problem
We want to implement semantic versioning in our process, we are in version 1.0.0, and we have added two new functions. We will deliver these functions soon. The question is: should we name our next version 1.1 or should we name it 1.2 because we have created two new functions. In general, if we add n new functions, should we increment by n the minor component of the version, or we only increment by one in each delivery?