0

http://gitversion.readthedocs.io/en/latest/why/ and https://github.com/GitTools/GitVersion explain the advantage of GitVersion over "Version.txt/Version in build script" and "Build Server versioning"

Before being able to understand the differences between the three approaches, what kind of problem do the three try to solve in common? In other words, what is versioning used for in the context of the three approaches?

Isn't a new version number created, by simply incrementing the version numbers? Why do we need complicated ways to calcuate version numbers?

If I am correct, the version here is different from the version of software release to users.

Thanks.

ps: If you could go on to explain the the differences between the three methods, that would be great. Otherwise, I will ask for that in a new post.

  • Are you familiar with semantic versioning? – Robert Harvey Sep 26 '17 at 19:11
  • I looked at semver.org but am not sure what it is used for. – Tim Sep 26 '17 at 19:12
  • Incredibly oversimplified tl;dr: breaking changes are only introduced in major version increments. Which means that you can generally upgrade libraries in minor version increments without worrying about breaking your program. – Robert Harvey Sep 26 '17 at 19:14
  • is "version" here version for source code during development? – Tim Sep 26 '17 at 19:15
  • Semantic versioning deals with production releases. – Robert Harvey Sep 26 '17 at 19:15
2

Isn't a new version number created, by simply incrementing the version numbers? Why do we need complicated ways to calcuate version numbers?

Because we are programmers, and we don't like to perform repetitive steps manually.

Why would I manually edit a version.txt file when I can let the VCS compute it for me?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.