Management Rules for software [version]

In order to maintain software projects, we have put forward the requirements for version management and control. For users, versions are directly reflected in the version number name. So how can we name the version number? I have checked a lot of information and hope to explain it more specifically. I also hope that you will be able to give your own opinions on the naming format of the version number while reading this article, this includes some version number naming examples. next, let's take a look at the three common naming formats.

GNU version naming format: Main version number. Subversion number [. Corrected version number [. compiled version number]
Comparison: major_version_number.minor_version_number [. revision_number [. build_number]
Example: 1.2.1, 2.0, 5.0.0 build-13124

Windows Version naming format: Major version number. Subversion number [corrected version number [. compiled version number]
Comparison: major_version_number.minor_version_number [revision_number [. build_number]
Example: 1.21, 2.0

. NET Framework-style version number naming format: Main version number. Sub-version number [. Build version number [. Modify version number]
Comparison: major_version_number.minor_version_number [. build_number [. revision_number]
Official Instructions:
Http://msdn.microsoft.com/library/default.asp? Url =/library/en-US/cpref/html/frlrfsystemversionclasstopic. asp
As there is an official explanation, this article does not explain it.

GNU Version Management Policy

The version number can be 0.1, 0.1.0, or 1.0 or 1.0.0 for the project's first version. If you are a low-profile user, I think you will choose the primary version number 0;
When the project is partially modified or the bug is corrected, the main version number and sub-version number remain the same, and the corrected version number is added to 1;
When some functions are added to the project on the basis of the original, the main version number remains unchanged, the sub-version number is added with 1, and the corrected version number is reset to 0, so it can be ignored;
When the project has been significantly modified or partially corrected, the overall project changes globally, and the main version number is increased by 1;
In addition, the compilation version is generally automatically generated by the compiler during the compilation process. We only define the format and do not manually control the version.
Version Number management policy in window

The project version is 1.0 or 1.00 at the beginning of the project;
When the project is partially modified or the bug is corrected, the main version number and sub-version number remain the same, and the corrected version number is added to 1;
When some functions are added to the project on the basis of the original, the main version number remains unchanged, the sub-version number is added with 1, and the corrected version number is reset to 0, so it can be ignored;
When the project has been significantly modified or partially corrected, the overall project changes globally, and the main version number is increased by 1;
In addition, the compilation version is generally automatically generated by the compiler during the compilation process. We only define the format and do not manually control the version.
In addition, you can add suffixes such as alpha, beta, gamma, current, RC (Release Candidate), release, and stable after the version number, you can add a version number of one digit after these suffixes.

If a user upgrades the main version of a software and wants to continue the software, the company that issues the Software generally charges the user for the upgrade; if the sub-version number or the corrected version number is upgraded, it is generally free of charge.
Reference: http://www.woodpecker.org.cn: 9081/doc/zscrapbook/data/20051010111809/