Establish a clear version number identification In order to standardize and unify the work, we need to clearly identify the version number of the job function email list product. At present, the industry usually adopts the following methods for naming software versions: Version number naming convention For example: 1.2.1, 2.0, 5.0.0 build-13124. Among job function email list them, the build version number is usually automatically generated by the compiler and is not provided externally. 1. Version number update rules Major version number update rules:

Brand-new optimization of product functions, including job function email list comprehensive update and optimization of pages, experience, and technology. The version numbers of the two products are upgraded as shown in the figure below. Subversion number update rules: 1. Important function modules have been added to the product; 2. Important updates have been made job function email list on the basis of the original functions; 3. Serious bug fixes. Revision number update rules: 1. Add or optimize general function modules; 2. Repair general bugs. 2. Version number suffix After the version number, suffixes such as Alpha, Beta,

Gamma, RC, Release can be added to indicate the current stage of the software. Alpha: closed beta. This version indicates that the software at this stage is job function email list mainly to implement software functions, usually only for internal communication among developers, or for testers to test. Generally speaking, this version of the software has many job function email list bugs and needs to be modified. Beta: Public beta version. Compared with the α version, this version has been greatly improved, and serious problems have been eliminated, but there are still some defects, which need to be further eliminated through multiple tests, and can be provided to certain target users for large-scale experience testing. RC Release: Release Candidate.