Recently, the company released the beta version, which involves the version number management of the software, and found that different companies have different version number management methods, each has its own strengths. Here is my version number management method that I think is good.

Version naming conventions

The software version number consists of four parts:

The first part is the major version number,

The second part is the second version number,

The third part is the revised version number,

The fourth part is the date version number plus the Greek letter version number. There are five Greek letter version numbers, including Base, alpha, beta, RC and release.

Description of software version phases

Base:

This version indicates that the software is just a fake page link, usually including all the functions and page layout, but the functions in the page are not fully implemented, just as an infrastructure of the overall site.

Alpha:

This version indicates that the software at this stage is mainly to achieve software functions, usually only in the software developers internal communication, generally speaking, this version of the software Bug more, need to continue to modify.

Beta:

This version is a big improvement over version alpha, eliminating serious bugs, but there are still some defects that need to be further eliminated through multiple tests. The main changes in this version are to the UI of the software.

RC:

This version is quite mature, with virtually no bugs causing errors, and is not much different from the upcoming official release.

Release:

This version means “final release”, after a series of beta versions of the previous version, there is a final release, which is the final release for users to use. This version is sometimes called the Standard edition. In general, Release does not appear as a word on the software cover, but instead as a symbol (R).

Version number Change rule

Major Version Number:

When there are major changes in functional modules, such as adding modules or changing the overall architecture. This version number is modified at the project’s discretion.

Second version:

An upgrade to a minor version number, relative to a major version number, corresponds to a partial change that causes the program to become incompatible with a previous version, or to break the program’s previous collaboration, or to make a major improvement or enhancement in functionality. This version number is modified at the project’s discretion.

Revised Version No. :

Usually it is Bug fixes or some minor changes or some function expansions. Revision should be released frequently, fixing a serious Bug can release a revision. This version number is at the discretion of the project manager.

Date version number (051021):

It is used to record the current date of the modified item. Every modification to the item requires a change in the date version number. This version number is at the discretion of the developer.

Greek version Number (Beta):

This version number is used to mark the development phase of the current version of the software and needs to be changed when the software moves to another phase. This version number is modified at the project’s discretion.

Release cycle

Non-emergency:

Bugs are first tested and submitted by testers, then the developers try to fix bugs that day and release the alpha version the next day, and then the beta version is released on the third day after bugs are closed by testers.

Emergency:

If the Bug is urgent, the general process can be skipped, and the developer can fix the Bug as soon as possible. After the test is confirmed, the beta version of the version can be released directly.

For example

In this case, the version number is 1.0.0.0321_alpha, which is in the internal test phase

After the developer fixes the bug submitted by the tester and closes the bug after verification by the tester, when it is released to the Internet, the next stage of the software will be entered. The version number can be changed to 1.0.0.0321_beta. If the current date is different from that of the previous version, the version number can be changed to: 1.0.0.0322 _beta.

A revision, such as 1.0.1.0322_beta, can be released on the current date of the release if some significant Bug fixes are followed and released to the Internet.

If some functional improvements or enhancements are made to the software, the second version number should be changed when some local changes are made, for example: 1.1.0.0322_beta (the lower level should be returned to zero when the upper level is changed).

When there are major changes in functional modules, modules are added or the overall architecture is changed, the main version number should be modified. For example, if the refund function is added, the version number should be changed to 2.0.0.0322_beta.