Versioning scheme

6

In .NET,% generated% have four version numbers. I've heard a lot about the major version and minor version, and that these would be the first two numbers. I've heard that the third one would be a "maintenance" number and the fourth would be a "review", but I've also heard (and found on the internet) mentions to the third number as the build number.

What is the "right" way to interpret numbers? Or is there more than one pattern? And when should each number be incremented?

    
asked by anonymous 26.02.2014 / 19:33

2 answers

4

"Correct" form does not actually exist, but there are some indications from Microsoft.

The MSDN uses the following form :

<major version>.<minor version>.<build number>.<revision>

Following the template:

  • Major version: The number that represents the flow of your application, when your application drastically changes the flow or is redesigned, increments this version.
  • Minor version: Number that represents the incremental improvements and new features, increments when the application is updated with new functionality.
  • Build version: Build build number, usually automatically incremented by Visual Studio.
  • Revision version: Number of BugFix, fixes in general, increments when your application is updated by patches function.

Like Windows itself:

  • Windows XP = 5.1.2600.3
  • Windows Vista = 6.0.6001.1
  • Windows Seven = 6.1.7601.1
26.02.2014 / 20:11
1

According to SEMVER :

(in free translation)

Given a MAJOR.MINOR.PATCH version number, increment:

MAJOR , when you make changes to the API that break backwards compatibility,

MINOR (Minor version), when you add functionality in a backwards-compatible way, and finally

PATCH , when you make backward compatible (bugfixes) patches.

Additional Labels for prereleases and Builds metadata are available as extensions to the MAJOR.MINOR.PATCH format.

NOTE:

  

In .NET , versioning with 4 numbers is adopted by default, the third being Build , and fourth is Revision > Number.

I hope I have been clear. If you have any questions, you can comment below or take a look at the SemVer specification.

    
26.02.2014 / 19:58