Software version number writing specification and description

1. Software Release Stage description

Base version: This version indicates that the software is just a fake page link, usually including all the features and page layout, but the features on the page are not implemented completely, but as a whole site of an infrastructure.
Alpha Version: This version indicates that the software is mainly used for software functions in this phase, usually only within the software developers, in general, this version of the software has more bugs and needs to be modified.
Beta: This version has been greatly improved relative to the alpha version, eliminating serious errors, but there are still some flaws that need to be further eliminated by several tests, the main modification of this version is like the UI of the software.
RC Version: This version is already quite mature, there is basically no bug that caused the error, similar to the upcoming release of the official version.
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, the first 1 is the main version number, the second 1 is the sub-version number, the third 1 is the stage version number, the fourth part is the date version number plus the Greek version number, the Greek version number has 5 kinds, namely: base, alpha, Beta, RC, release. For example: 1.1.1.051021_beta.

3, the software version number specification

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.
Phase 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 every day changes to the item need to change the date version number. This version number is determined by the developer to modify.
Greek letter version Number (Beta): This version number is used to label the development phase 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 specification
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.

5, version number of the stage identification

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

Software version number writing specification and description