Software Naming conventions

A formal software product must have a canonical name, a good software product must have a canonical version number, and in the name of the version number of the rules have been established, let me briefly introduce below.

1. Version naming specification

The software version number is composed of four parts, the first part is the main version number, the second part is the minor version number, the third part is the revision version

This number, the fourth part of the date version number plus the Greek version number, the Greek version of the total number of five kinds, respectively, base, alpha, Beta, RC?、? release

2. Software Release Phase description

Base: This version indicates that the software is just a fake page link, usually including all the features and page layout, but the function on the page does not do a complete implementation, but as a whole site of an infrastructure.

Alpha: The primary version of the software, indicating that the software at this stage to achieve the main software functions, usually only in the software developer communication, generally speaking, the version of the software bug more, need to continue to modify, is the beta version. The tester submits the bug after the developer has modified the confirmation, publishes to the test URL lets the tester test, at this time can mark the software version as the Alpha Edition.

Beta: This version has made a lot of progress with respect to the alpha version, eliminating serious errors, but requires several??? Test to further eliminate this version of the main modification object is the UI of the software. Modified bug? Tested by??? Can be posted to the extranet when the test is confirmed, the software version can be labeled as a beta version.

RC?: This version is quite mature, there is basically no error caused by the bug, and the upcoming release of the official version of the difference?? Multitude

Release: This version means "final version", after a series of beta versions of the previous version, there will eventually be a formal version that is used by the final delivery user. This version is sometimes called the Standard Edition.

3. Version number modification rules

(1) Major version number: When the function module has a large change, such as adding the module or the overall structure changes. This version???? The project decides whether to modify it.

(2) Minor version number: Relative to the major version number, the minor version number of the upgrade corresponds to only the local changes, but the local???? Does the change cause the program to be incompatible with the previous version, or does it have a previous collaborative relationship with the program???? The destruction, or there is a large improvement or enhancement in functionality. This version number is determined by the project.??? Change.

(3) Revision number: Is it usually a bug? Fix or some minor change or expansion of some functions to be published frequently?? Bug? You can publish a revision. This version number is determined by the project manager.

(4) Date version number: 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.

(5) Greek alphabet version number: 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. Version release cycle

(1) Non-emergency: First Test and submit the bug by the tester, and then the developer will try to fix the bug on the same day and release the Alpha version of the version the next day, then the tester will release the version of the beta version on the third day after testing to verify that the bug was closed.

Emergency: If the bug is more urgent can skip the general process, the developer as soon as possible to fix the bug, test confirmation after the release of the version of the beta version.

5. Version number Modification Example description

At this time, the version number is: 1.0.0.0321_alpha?, this is the internal test phase

(1) When the developer fixes the bug submitted by the tester and the tester verifies that the bug has been closed, when it is published to the extranet, it enters the next stage of the software and the version number can be changed to: 1.0.0.0321_beta?, if the current date is different from the date of the previous version number, The version number can be changed to: 1.0.0.0322_beta.

(2) What if some major bugs are fixed? And as the process is published to the Extranet, a revision, such as 1.0.1.0322_beta, is published and the date is the current date of the publication.

(3) If the software has some functional improvements or enhancements, some local changes to the time to modify the minor version number, such as: 1.1.0.0322_beta (the upper level of change, subordinate to zero).

(4) When the function module has a large change, increase the module or the overall structure changes when you want to modify the major version number, such as the new refund function, the version number should be changed to: 2.0.0.0322_beta?

Software Naming conventions