I have very little experience this, despite having decades of programming under my belt. The +1 with each master branch merge proved to not be the best as we have seen many programs to switch to year and month type of versioning. Which makes sense as it clearly communicates WHEN the current version was the most up-to-date and it leaves no place for ambiguity.
On the other hand, unlike products, libraries still make sense to version semantically as it is technical information for the users of those libraries that clearly communicates breaking changes.
Comments
I have very little experience this, despite having decades of programming under my belt. The +1 with each master branch merge proved to not be the best as we have seen many programs to switch to year and month type of versioning. Which makes sense as it clearly communicates WHEN the current version was the most up-to-date and it leaves no place for ambiguity.
On the other hand, unlike products, libraries still make sense to version semantically as it is technical information for the users of those libraries that clearly communicates breaking changes.