Software Naming Convention (version number)

Software naming rules

1. Software Version Stage Description
   • Base version:This version indicates that the software is only a fake page Link, usually including all functions and page layout, but the functions in the page are not fully implemented, just as an overall website infrastructure.
   • Alpha version:This version indicates that the software is mainly used to implement software functions at this stage, and usually only communicates with software developers. Generally, the software has many bugs and needs to be modified.
   • BETA: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:(Release Candidate) This version is quite mature. Basically, there are no bugs that may lead to errors, which is almost the same as the official version to be released.
   • Release Version:This version indicates the "final version". After a series of Beta versions of the previous version, there will be a formal version, 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.

   
   

   Rules for changing the version number:

   • Major version (1 ):When there are major changes to functional modules, such as adding multiple modules or changing the overall architecture. The version number is determined by the project.
   • Sub-version (1 ):When functions are added or changed, for example, permission control and custom views are added. The version number is determined by the project.
   • Phase version (1 ):It is generally a bug fix or a small change. A revision should be released frequently with no fixed interval. You can release a revision after fixing a serious bug. The Project Manager determines whether to modify the version number.
   • Date version (051021 ):It is used to record the current date of the modified project, and the date version number needs to 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 this version number. The version number is determined by the project.
3. File naming rules

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

   Bytes

   When multiple people submit the same file at the same time, you can add names or abbreviations to the end of the stage logo, for example: Project outsourcing platform test report 1.1.1.051021_beta_ B _liuqi.xls. When this file is submitted again, you can add serial numbers after the person's name or abbreviation, for example, 1.1.1.051021_beta_ B _liuqi2.xls

4. Stage ID of the version number

   Each software version contains 11 stages. The detailed stages are described as follows:

   Stage name	Stage ID
   Requirement 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