Software version number specification and naming principle

1. Software Release Phase description

* Alpha Version: This version indicates that the software is mainly used for software functions in this phase, usually only within the software developers, generally speaking, this version of the software has more bugs and needs to be modified.
* Beta version: This version of the Alpha version has been a great improvement, eliminating serious errors, but there are still some shortcomings, need to undergo a number of tests to further eliminate, this version of the main changes to the software like the UI.
* RC Version: This version is quite mature, there is basically no error caused by the bug, and the upcoming release of the official version of the same.
* Release version: This version means "final version", after a series of beta versions of the previous version, there will eventually be a formal version, a version that is used by the final delivery user. This version is sometimes referred to as the Standard Edition. In general, release does not appear as a word on the software cover, instead of the symbol (R).

2. Version naming specification

The software version number consists of four parts:

First 1 Main version number

The second 1 is a sub-version number

The third 1 is a stage version number

The fourth part is the date version number plus the Greek version number

There are 5 versions of the Greek alphabet: base, alpha, Beta, RC, release. Example: 1.1.1.051021_beta

General: Full version number definition, divided into three items::< major version number >.< minor version number >.< revision number, such as 1.0.0

3. Revision rules for version number setting

* Major Version number (1): When the function module has a large change, such as the addition of multiple modules or the overall architecture changes. This version number is determined by the project to modify.
* Sub-version number (1): When the function has a certain increase or change, such as increased access to control, add custom views and other functions. This version number is determined by the project to modify.
* Stage version number (1): usually bug fixes or some small changes, to frequently publish revisions, time interval, fixed a serious Bug can be released a revision. This version number is determined by the project manager to modify.
* Date version number (051021): Used to record the current date of the modified item, and changes to the project every day need to change the date version number. This version number is determined by the developer to modify.
* Greek alphabet Version number (Beta): This version number is used to mark the development stage of the current version of the software, and this version number needs to be modified when the software enters another phase. This version number is determined by the project to modify.

4. File Naming conventions

The file name consists of four parts: the first part is the project name, the second part is the description of the document, the third part is the version number of the current software, the fourth part is the file phase identification plus file suffix, for example: Project outsourcing platform test report 1.1.1.051021_beta_ B.xls, this file is a test report document for the project outsourcing platform, with the version number: 1.1.1.051021_beta.

If the same version of the same phase of the file has been modified more than two times, then the stage identification is digitally identified, each modification of the number plus 1, the Project Outsourcing platform test report 1.1.1.051021_beta_b1.xls.

When more than one person submits the same document at the same time, it can be distinguished by the addition of the name or abbreviation after the stage identification, for example: Project outsourcing platform test report 1.1.1.051021_beta_b_liuqi.xls. When this file is submitted again, you can also add a serial number after the name or initials, for example: Project outsourcing platform test report 1.1.1.051021_beta_b_liuqi2.xls.

5. Phase identification of the version number

Each version of the software includes 11 stages, which are described in detail in the following steps:

Stage name Stage identification
Demand control A
Design Phase B
Encoding phase C
Unit Test D
Unit Test Modification E
Integration Test F
Integration Test Modification G
System Test H
System Test Modification I
Acceptance Test J
Acceptance Test Modification K

Software version number specification and naming principle