Software Version naming rules

1. Software Version Stage Description

• Base: This version indicates that the software is only a fake page link, which usually includes all functions and page layout, but the functions in the page are not fully implemented, it is just an infrastructure for the overall website.
• ALPHA: 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, 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:
  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:
  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 ).

The version naming convention software version number consists of four parts, for example, 1.2.3.4567890 _ Beta

• The first 1 is the major version number.
• The second 1 is the sub-version number.
• The third one is the stage version number.
• The fourth part is the date version and the Greek letter version.

Rules for changing the version number:

1. Major version (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 number (1): When features are added or changed, such as permission control and custom views are added. The version number is determined by the project. Phase version (1): generally a bug
   Fix the issue or make minor changes. You need to release a revision frequently with no fixed interval. To fix a serious bug, you can release a revision. The Project Manager determines whether to modify the version number.
   
   Date version (051021): used to record the current date of the modified project. The date version number needs to be changed every day for modifications to the project. The developer determines whether to modify the version number. Greek letter version number (Beta): This version number is used to indicate the development stage of the current version of the software. When the software enters another stage, the version number needs to be modified. The version number is determined by the project.