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

Software cycle version

Software release cycle

α, β and λ are often used to represent the three stages in the process of software testing. -An is the third stage, when the product is already quite mature and only needs further optimization in individual places.

Development period

-- Alpha (α): preview version, or internal beta version; generally not released to the external, there will be a lot of Bug; generally only used by testers. -- Beta (β): beta, or public beta; the version at this stage will always add new features; it will be released after the Alpha version. -- RC (Release Candidate): the final test version; may be a candidate for the final product, or if there is no problem, it can be released as the official version-- Release version: this version means "final version". After a series of beta versions of the previous version, there will eventually be a formal 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). Most open source software releases two versions of RC, and the final RC2 becomes the official version.

Completion period

-- Stable: stable version; released from the preview version for use and improvement. -- GA (General Availability): the officially released version; GA is used to describe the release version in foreign countries. -- RTM (Release to Manufacturing): the release version for the manufacturer; the RTM version does not necessarily mean that the creator has solved all the problems with the software; it is still possible to update the version before it is released to the public. Another RTM is called RTW (Release To Web), which means that the official version of the software is released to the Web website for free download. -- RTL (Retail): the retail version; it is the real official version, the official retail version. Alpha, beta, and gamma are used to identify the phase and scope of the test

Description

Alpha: internal beta, which is now called CB, refers to the internal test version of the development team or limited user experience test version; Beta: external test version, which refers to public testing, that is, the test version that is open to all users Gamma: is the beta version with some modifications to become the official release candidate version (Release Candidate) Build: internal label Corporation or Enterprise Enterprise Edition Delux: deluxe version (deluxe: luxurious, gorgeous) DEMO demo version There will generally be functional limitations Free: free version Full: full version Final: official version Pro (professional): professional version Plus: enhanced version Retail: retail version Release distribution, time limit Shareware shared version, although registration is not required, but generally there are functional limitations SR: modified version Trial: trial version (usually with time or functional restrictions)

RTM: (Release to Manufacture) is a version that presses a large number of films for the factory, and the content is the same as the official version, but the RTM version also has a limited and evaluation version. But it is the same as the main program code in the official version.

OEM: it is sold to computer manufacturers along with the computer, that is, the random version. Can only be shipped with the machine, not retail. It can only be installed fresh, not upgraded from the old operating system. Unlike the exquisite retail version, the package usually has only one side of the CD and the instruction book (authorization form).

EVAL: the EVAL version, which circulates on the Internet, is similar to the "evaluation version" and is no different from the retail version in function.

RTL:Retail (retail version) is the real official version, the official retail version. There is an eula.txt in the i386 folder of the installation disk, and at the end there is a line EULAID, which is your version. For example, the official version of simplified Chinese is EULAID:WX.4_PRO_RTL_CN, and the official version of traditional Chinese is WX.4_PRO_RTL_TW. Among them: if it is WX. It starts with the official version, WB. It starts with a beta version. _ PRE, which represents the home version, and _ PRO, which represents the professional version.

Demo version (demo version): DEMO is the abbreviation of the English word demonstration, demo version, trial version, mainly to demonstrate some functions of the formal software, from which users can know the basic operation of the software and expand the influence for the release of official products.

Enhance version (enhanced version or enhanced version): if it is general software, commonly known as "enhanced version", some practical new features will be added. If it is game, commonly known as "enhanced version", some new scenes and plots will be added. This is the official release.

-

KB:

KB is the way Microsoft names patches and is short for Knowledge Base (knowledge Base).

It refers to a patch corresponding to which article in the Microsoft knowledge base.

KB888111, for example, corresponds to article 888111 in the knowledge base.

Now it is generally used to represent patches, KB1,KB2,KB3.

-

SP:

Short for upgrade patch pack Service Pack

Such as Windows XP SP2, etc.

Each version of the software includes 11 phases, which are described in detail as follows:

Phase name phase identification requirements control a design phase b coding phase c unit test d unit test modification e integration test f integration test modification g system test h system test modification

I acceptance test j acceptance test modification k

The software version number consists of four parts, the first 1 is the major version number, the second 1 is the sub-version number, the third 1 is the stage version number, the fourth part is the date version number plus the Greek alphabet version number, there are five Greek alphabet version numbers, namely: base, alpha, beta, RC, release. For example: 1.1.1.051021_beta.

1.1.1.051021_beta .

1: major version number (total version number)

1: branch version number

1: minor version number

051021: milestone version date version number

Greek alphabet version number

Naming and modification rules for APP version numbers

1. Major version number (1)

When there are great changes in many major modules of APP, in general, for example, a TAB is added to APP, the entire product structure is changed, or new features or businesses are added, such as Wechat online Wallet, Douyin online LVB; the starting value of the major version is 0 or 1, and it is up to the product manager to decide whether to change the major version (PS: most may need to be approved by the boss).

two。 Sub-version number (1)

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 (1)

The initial value of the phase version number is 0; when the phase version number is modified, it is generally fixed by Bug and changed by fewer branch modules, such as vision, style, interaction, copywriting, etc.; in general, if only bug is repaired, 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, the direct child version number + 1 is recommended.

4. Date version number (051021):

Used to record the current date of the modified project, the date version number needs to be changed for daily changes to the project. It is up to the developer to decide whether to modify this version number.

5. Greek alphabet version number (beta):

This version number is used to indicate which development stage the current version of the software is in, and this version number needs to be modified when the software enters another stage. This version number is up to the project to decide whether to modify it.

Summary

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.

The naming version number is not rigorous and standardized, and the product manager needs to pursue perfection. I hope the naming convention of the above APP version can give you some reference.

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.