Shulou(Shulou.com)06/02 Report--

This article will explain in detail how to name the APP version number correctly and elegantly. The content of the article is of high quality, so the editor shares it for you as a reference. I hope you will have a certain understanding of the relevant knowledge after reading this article.

As a mobile product manager, APP version iteration planning is often done, so it is inevitable to determine the version number of the APP version, which may be determined on the head in most cases.

Some companies may have special project managers responsible for version management and version number naming, but most small companies may have product managers to do the job.

After collecting some information on the Internet, I found that there are many norms and principles for the naming of APP version numbers. below, I will share these norms and principles with you.

First, why standardize the naming of APP version numbers?

The first thing to say is who needs to use the APP version number, the first is the product manager, the second is the developer, the third is the project manager, and the fourth is the user.

For the product manager, the APP version iteration is basically initiated by the product manager, so in many cases, the product manager roughly divides the version number when carrying out requirements management and version planning, and the version number for the product manager can better and more clearly filter and determine the requirements of each version.

For developers, the version number is directly related to the code, and often different versions are cross-developed, and different versions may be developed at the same time. In order to ensure the standardization and clarity of the code and avoid cross-confusion between different versions, the version number is an extremely important link.

For the project manager, the version number is the unique identifier in the requirements management, which needs to manage and assign the distribution work according to the version number, but also for better communication and marking in the software product life cycle.

For users, although the version number is only a series of numbers for users, the perception of the version number to the user is a constantly updated number, and you can judge whether your APP is up-to-date by the version number.

II. The composition and specification of the app version number

At present, in many cases, the version number may only follow two principles and norms, that is, the version number is unique and is a string of numbers.

Before introducing the naming conventions and principles of APP version numbers, we first need to understand some of the composition of APP version numbers.

The software version number consists of four parts:.

There are five Greek alphabet version numbers: base, alpha, beta, RC, Release. For example: 2.1.0.181209_Release.

The following is a brief description of the Greek alphabet number:

Alpha version: also known as alpha version (development environment), this version is mainly to achieve software functions, usually only within the software developers to communicate

Beta version: compared with alpha version, this version has been greatly improved and serious errors have been eliminated, but there are still some defects that need to be further eliminated after many tests. The main target of this version is the UI of the software.

RC version: this version is so mature that there is basically no BUG that causes errors, just like the upcoming official version, which is basically passed by testers.

Release version: this version means "final version" and "live version". After a series of beta versions of the previous version, there will eventually be an official version, which is the final version delivered to users. This version is sometimes called the standard version. In general, Release does not appear in the form of words on the cover of the software, instead of the symbol (R).

For the vast majority of APP, the general use of GNU-style version number management strategy, APP complete version number consists of three sets of numbers ".", that is, X.Y.Z, in which X, Y, Z are positive integers.

III. Rules for naming and modifying the app version number

1. Major version number

When there are great changes in several major modules of APP, in general, for example, a TAB is added to APP, the entire product structure is changed, or new functions or services are added, such as Wechat Wallet or Douyin Live.

The starting value of the major version number is 0 or 1, and it is up to the product manager to decide whether the major version number needs to be changed (PS: most may need to be approved by the boss).

two。 Child version number

The initial value of the child version number is 0

When fewer major modules of APP change greatly or new modules (involving main logic changes) or more branch modules are changed or added, it is only a local change relative to the major version number, such as UI reconfiguration on a certain function, optimization of a page, etc., in which fewer modules and more modules need to be defined. Generally speaking, we think that there are fewer than 3 modules and more than 3 modules.

The maximum value of the sub-version number needs to be determined. Different companies may have the maximum value, for example, the maximum value is 9. If it exceeds 9, the major version number needs to enter 1, and some companies may not have a maximum value. The sub-version number will only be returned to 0 when the major version number is + 1; there are no definite principles and specifications, and the product manager can make the rules by himself.

3. Phase version number

The initial value of the phase version number is 0

When to modify the phase version number, it is generally Bug repair, fewer branch module changes, such as visual, style, interaction, copywriting and other changes.

In general, if you only repair bug, the stage version number is + 1; if both bug repair and fewer branch module modifications are involved, the phase version number is + 2; if more than 3 branch modules are modified, it is recommended to directly subversion number + 1.

Although the version number is just a string of numbers, it is a meaningful string of numbers for product managers, developers, and users. It can not only standardize the life cycle of the version, but also facilitate the communication and work of internal personnel.

On how to correctly and elegantly name the APP version number to share here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.