2 ms·
But you dont get the most important part: Will installing the 2022.05.03-37492af update break my build or not? Semantic versioning is about compatibility and a
by lionkor 4y ago
But you dont get the most important part: Will installing the 2022.05.03-37492af update break my build or not?
Semantic versioning is about compatibility and amount of changes, sort of. I know that going from 3.0.1 to 3.1.0 wont break the API.
Not once have I been asked when 3.0.1 was released - and if Im asked, I can look at the release posts, or anything else.
Cute idea, but appending a git commit hash to the end of a semantic version may be more useful than any of this.
- lionkor 4y agoPlus, if your main issue with semantic versioning is that you cant find your changelog, make it part of your git repo. At BeamMP (a multiplayer game project) we have a changelog.md file right in the server repo. Go to any release tag and youll automatically also have the relevant changelogs.
- nathanaldensr 4y agoI agree. Additionally, some binaries like .NET assemblies have "informational" versions that can be set to arbitrary strings. I like to version my assemblies something like 1.2.3.4-rc.1+githash to communicate not only the semantic version but also the commit hash used during the build.