Software Version Number Format

The version number is relatively free. There is no relationship between the Beta or official version and the version number. As long as the version number meets the requirements of the official version, even if the version number is 1.0 or 0.1, it may be the official version.
* Alpha version: This version indicates that the software is mainly used to implement software functions at this stage. It is usually only communicated within the software developer. Generally, this version has many bugs, you need to continue modification.
* Beta version: this version has been greatly improved compared with alpha version, eliminating serious errors, but there are still some defects that need to be further eliminated through multiple tests, this version mainly modifies the UI of software.
* RC version: This version is quite mature. Basically, there are no bugs that may lead to errors, which is similar to the official version to be released.
* Release version: This version indicates the "final version". After a series of Beta versions of the previous version, a formal version will eventually be available, which is a version that is finally delivered to users. This version is also known as the Standard Edition. In general, Release does not appear on the software cover in the form of words, instead of the symbol (R ).

2. Version naming rules

The software version number consists of four parts: The first 1 is the major version number, the second 1 is the Subversion number, the third 1 is the stage version number, and the fourth part is the date version number plus the Greek letter version number, there are five Greek letter versions: base, alpha, beta, RC, and release. Example: 1.1.1.051021 _ beta.

3. Fixed modification rules for version numbers

* Major version number (1): When the function module changes significantly, such as adding multiple modules or changing the overall architecture. The version number is determined by the project.
* Sub-version (1): When features are added or changed, for example, permission control and custom views are added. The version number is determined by the project.
* Phase version number (1): it is generally a Bug fix or a small change. A revision should be released frequently, with no fixed interval. A critical bug can be fixed to publish a revision. The Project Manager determines whether to modify the version number.
* Date version number (051021): used to record the current date of the project to be modified. The date version number must be changed every day for changes to the project. The developer determines whether to modify the version number.
* Greek letter version (beta): This version number is used to indicate the development stage of the current version of the software. When the software enters another stage, you need to modify the version number. The version number is determined by the project.

You can also define it as follows:
A. B. c. d
A: version number.

B: Release number. The number of release times in the same version.

C: Revision No. Fix the bug number. (Multiple bugs may be fixed to be released once ).

D: Build number. That is, the number of builds. This is learned from Microsoft. I wrote a tool that automatically increases every Build.