Version number naming specification

Recently written documents have been abused ... Ah, fall. The teacher is not satisfied, but also embarrassed to criticize me directly, make oneself very ashamed ... So I decided to strengthen my writing skills.

First of all, from the file management improvements, the first is the version number of the management specification,

Transferred from Baidu Library http://wenku.baidu.com/view/0f7d6b240722192e4536f66b.html

Version control is more common in 3 naming formats:

first, GNU style version number naming format:
The major version number. Child version number [. fix version number [. Build version number]]
major_version_number.minor_version_number[. revision_number[. Build_number]]
Example: 1.2.1, 2.0, 5.0.0 build-13124

Second, the Windows style version number naming format:
The major version number. Child version number [fix version number [. Compile version number]]
major_version_number.minor_version_number[revision_number[. Build_number]]
Example: 1.21, 2.0

iii.. Net Framework-style version number naming format:
Major version number. Child version number [. build version number [. Fix version number]]
major_version_number.minor_version_number[. build_number[. Revision_number]]
The version number consists of two to four parts: Major, minor, build, and revision. The major and minor version numbers are required, and the build number and revision number are optional, but if the revision number section is defined, the build number is required. All defined parts must be integers greater than or equal to 0.

These sections should be used according to the following conventions:

Major: Assemblies with the same name but different major version numbers are not interchangeable. This applies, for example, to a large number of overrides for products that do not allow for backward compatibility.

Minor: If the name of two assemblies is the same as the major version number, and the minor version number is different, this indicates a significant increase, but it takes care of backward compatibility. This applies, for example, to a revision of the product or to a new version that is completely backwards compatible.

Build: A different version of the build number represents a recompilation of the same source. This is appropriate for changing the processor, platform, or compiler situation.

Revision: Assemblies that have the same name, major version number, and minor version number but different revision numbers should be fully interchangeable. This applies to fixing security vulnerabilities in previously released assemblies.

Subsequent versions of an assembly that differ only by build or revision numbers are considered to be previous versions of the hotfix (Hotfix) update.

Version number Management policy

I. GNU-style version number management strategy:

1. At the beginning of a project, the version number can be either 0.1 or 0.1.0, or 1.0 or 1.0.0, if you are very low-key, I think you will choose the main version number 0 way;
2. When the project is in a local modification or bug fix, the major version number and the child version number are unchanged, the revision number plus 1;
3. When the project on the original basis to add some functions, the main version number is unchanged, the sub-version number plus 1, the fixed version number is reset to 0, so it can be ignored;
4. When the project has undergone significant changes or local corrections accumulate more, and cause the overall change of the project, the main version number plus 1;
5. In addition, the compiled version number is usually generated automatically by the compiler during the compilation process, we only define its format and do not have human control.

Second, the version number under Window Management policy:
1. When the project is first first, the version number is 1.0 or 1.00;
2. When the project is in a local modification or bug correction, the major version number and the child version number are unchanged, the revision number plus 1;
3. When the project on the original basis to add some functions, the main version number is unchanged, the sub-version number plus 1, the fixed version number is reset to 0, so it can be ignored;
4. When the project has undergone significant changes or local corrections accumulate more, and the overall change in the project, the main version number plus 1;
5. In addition, the compiled version number is usually generated automatically by the compiler during the compilation process, we only define its format, and do not have human control.

In addition, you can add Alpha, Beta, Gamma, Current, RC (Release Candidate), release, Stable and other suffixes after the version number, and you can add a 1-digit version number after these suffixes.

For the user, if the major version number of a software upgrade, users also want to continue the software, the release of the software companies typically charge users for upgrade fees, and if the sub-version number or revision number has been upgraded, is generally free of charge.

===== Appendix software version name =====

Alpha (Alphal) internal Beta
Alpha version, this version indicates that the software is only a preliminary product, usually only within the software developers to communicate, but also a small portion of the release to professional testers. Generally speaking, this version of the software bug more, ordinary users should not install.

Beta (Beta) external beta version
This version has been greatly improved relative to the alpha version, eliminating serious errors, but there are still some flaws that need to be further eliminated by large-scale release testing. This version is usually released free of charge by the software company and can be downloaded from the relevant site. Through the testing of some professional enthusiasts, the results are fed back to the developers and the developers make targeted changes. This version is also not suitable for general user installation.

Gamma (gamma) version
This version is already quite mature, with the upcoming release of the official version of the same, if the user can not wait, try to install.

Trial (Trial version)
The beta software has been popular in recent years, mainly thanks to the rapid development of the Internet. This version of the software usually has a time limit, after the expiration of the user if you want to continue to use, generally have to pay a certain fee for registration or purchase. Some of the trial version of the software also has a certain limit on the functionality.

unregistered (unregistered version)
Unregistered version is very similar to the trial version, but the non-registered version usually has no time limit, in the functional relative to the official version of the restrictions, such as the majority of Internet telephony software registration and unregistered version, the quality of the call there is a big gap. There are some although in use with the official version of identical, but will pop up an annoying message box to remind you to register, such as looking at the picture software ACDSee, intelligent Chen Qiao Chinese character input software.

Demo version
In the informal version of the software, this version of the most known. The demo version only integrates several features in the official version, quite a bit like unregistered. The difference is that the demo version can not be upgraded or registered by the method to become the official version.

The above is the official version of the software before the release of several versions, α, beta, gamma can be called beta, generally mature software will always have a number of beta version, such as the beta version of Windows 98, and then nearly 10. With so many beta editions on the one hand, the final product is as satisfying as possible to the user's needs, while minimizing bugs in the software. And trial, unregistered, demo sometimes collectively referred to as the demo version, this kind of version of the advertising color is thicker, quite a bit before the taste of buying, for ordinary users naturally can be free early adopters.

The official version, the official versions of different types of software are usually also differentiated.

Release final released version
This version means "final release", after a series of beta versions, there will eventually be a formal version, for users, the purchase of this version of the software is absolutely not wrong. This version is sometimes referred to as the Standard Edition. In general, release does not appear as a word on the software cover, instead of a symbol (r), such as Windows NT (r) 4.0, MS-DOS (R) 6.22, and so on.

Registered registered version
Obviously, this version is a registered version of unregistered. The registered version, release and the Standard Edition described below, are the official version of the software, but a large part of the predecessor of the registered software is downloaded from the Internet.

Standard Edition
This is the most common Standard Edition, no matter what the software, the standard version must exist. The Standard Edition contains the basic components of the software and some common functions to meet the needs of the general user. The price is "approachable" for a relatively high-level version.

Deluxe Deluxe Edition
As the name implies, "Deluxe Edition". Deluxe Edition is usually relative to the standard version, the main difference is a few more features, the price of course will be higher than a large, not recommended for general users to buy. This version is often intended for professional users who pursue the "perfect".

Reference
This version of the model is common in the encyclopedia, the more famous is the Microsoft Encarta Series. Reference is the highest level, it contains themes, images, movie clips and so on the standard and the deluxe version has a significant increase in capacity from a CD to three discs, and added a strong interactive function, of course, the price is not cheap. It can be said that this version of the encyclopedia can be regarded as a true encyclopedia, but also the first choice of enthusiasts collection.

Professional (Professional Edition)
The Professional edition is for some specific development tool software. Many of the content in the Pro Edition is not available in the Standard Edition, which is extremely important for a professional software developer. Microsoft's Visual FoxPro Standard Edition does not have the ability to compile executable files, which is obviously intolerable for a complete development project if no FoxPro is available on the client. If you use the Pro version there is no problem.

Enterprise (Corporate Edition)
Enterprise Edition is the best in development software (equivalent to the reference version in the encyclopedia). Having a set of this version of the software can develop any level of application without any obstacles. The famous Visual C + + Enterprise Edition adds several additional features to the Professional edition, such as SQL debugging, extended stored procedure wizards, support for as/400 access to OLE DB, and more. And this version of the price is not acceptable to ordinary users. such as Microsoft's Visual Studios 6.0 Enterprise Chinese version of the price of 23000 yuan.

Other versions, in addition to some of the versions described above, have some proprietary version names.

Update (upgrade version)
The upgraded version of the software is not used independently, the version of the software during the installation process will search for the original version, if not present, then refused to perform the next step. such as Microsoft Office 2000 upgrade, Windows 9x upgrade, and so on.

OEM version
The OEM version is typically a version that is bundled in hardware and not sold separately. To the other companies to sell their products, to retain their copyright, mutual benefit, double benefit.

stand-alone (network) edition
Network version in the function, structure is far more complex than the standalone version, if you pay attention to the software quotes, you will find some software standalone version and network version of the price difference is very large, some network version even more a client port will add a lot of money.

Popular Edition
This version is sometimes called a shared version, which is characterized by low prices (some are even completely free), a single function, strong targeting (and of course, the occupation of the market, anti-piracy and other factors). Unlike the trial version, this version of the software generally does not have a time limit. Of course, if users want to upgrade, it is best to buy the official version.

Enhance enhanced or enhanced version belongs to the official version
Free version
Full version complete version belongs to the official version
Shareware Shared edition
Release releases have a time limit
Upgrade Upgrade Version
Retail retailing Edition
CardWare is a shared software, as long as the author replies to an email or postcard. (some authors and thus provide registration code, etc.), this form is now rare.
Plus is an enhanced version, but most of this is enhanced by the program interface and multimedia functions.
Preview version
Corporation & Enterprise Edition
Standard Edition
Mini Mini version is also called Lite version only the most basic functions
Premium--Your price version
Professional--Professional Edition
Express--Special edition
Deluxe--Deluxe Edition
Regged--registered version
CN-Simplified Chinese version
CHT--Traditional Chinese version
EN-English version
MultiLanguage--Multi-language version

Software version number summary:

V (Version): That is, versions, usually with a number representing the version number. (Example: EVEREST Ultimate v4.20.1188 Beta)
Build: A way of marking a version number with a number or date. (Example: VeryCD eMule v0.48a Build 071112)
Sp:service Pack, upgrade package. (Example: Windows XP sp2/vista SP1)

Authorization and functional Partitioning:
Trial: Trial version, usually have a time limit, some of the trial version of the software is also a certain limit on the functionality. can be registered or purchased as a full version
Unregistered: Unregistered version, usually no time limit, in the functional relative to the official version has made certain restrictions. can be registered or purchased as a full version.
Demo: Demo version, only the integration of several features in the official version, can not be upgraded to the official version.
Lite: Lite version.
Full version: Complete edition, belongs to the official version.

Language Division:
Sc:simplified Chinese Simplified Chinese version.
CN: Simplified Chinese version
GBK: Simplified Chinese Character code Extension Specification Edition.
Tc:traditional Chinese Traditional Chinese version.
CHT: Traditional Chinese version
BIG5: Traditional Chinese large five yards version.
EN: English version
MultiLanguage: Multi-language version
Utf8:unicode Transformation Format 8bit is not a good solution for existing Chinese systems.

Other version divisions:
Enhance: The enhanced version or the enhanced version belongs to the official version 1
Free: Freedom version
Release: The release has a time limit
Upgrade: Upgrade Version
Retail: Sales Edition
CardWare: A shared software, as long as the author replies to an email or postcard. (some authors and thus provide registration code, etc.), this form is now rare.
Plus: This is an enhanced version, but most of this is enhanced by the program interface and multimedia functions.
Preview: Previewing version
Corporation & Enterprise: Corporate Edition
Standards: Standard Edition
Mini: Mini version is also called Lite version only the most basic functions
Premium: Your price version
Professional: Professional Edition
Express: Special Edition
Deluxe: Deluxe Edition
Regged: Registered Version
Rip: Refers to the original file (generally referred to as a CD or CD image file) to separate the useful content (core content) directly, eliminate useless documents, such as PDF document AH, video presentation Ah such things, can also be counted as a lite version, but the main content function is not a little lacking. Another: DVDRip refers to the video and audio directly from the DVD disc to separate files.

RTM version: This is basically the final version, English is release to Manufactur, meaning is released to the manufacturer.
OEM version (Original equipment manufacturer): OEM software is a version of the production plant for computers, needless to say.

FPP version (full Packaged product (FPP)/retail): Retail edition (boxed software), the CD-ROM of this product has the word "FPP", such as the FPP version of the English Windows XP Pro CD volume label is Wxpfpp_en, One of the WX representations is that Windows Xp,p is professional (H is home), FPP indicates that it is a retail version, EN is English. Access to some MSDN users is available in addition to store purchases.
Vol Edition (Volume Licensing for Organizations (VLO)): Group Volume License (bulk purchase license contract), which is a preferential method for group purchase. The CD-ROM of this product is labeled "VOL", taking "Volume" the first 3 letters to indicate that it is in bulk, such as the vol version of the English WXP Pro CD-ROM label is wxpvol_en, where WX is said to be Windows XP, P is Professional (vol no home version), vol indicates the Group Volume License version, EN is indicated to be English. Access is primarily purchased by the group, and some MSDN users can get it.

Software Development Phase Division:

1. Software Release Phase description

*α (Alpha) version: Beta version. This version indicates that the software in this phase mainly to achieve the main software functions, usually only in the software developers internal communication, or professional testers testing, in general, the version of the software has more bugs, need to continue to modify.
*β (Beta) version: public beta. This version has been greatly improved relative to the alpha version, eliminating serious errors, but there are still some shortcomings, need to undergo a number of tests to further eliminate, this version of the main changes to the software like the UI, for professional enthusiasts to large-scale test trial.

* RC version: is the release candidate abbreviation, meaning is the release countdown, the candidate version, this version is already quite mature, completes the entire function and clears most bugs, basically does not have the bug which causes the error, is similar to the forthcoming release official edition.

* Release version: This version means "final version", after a series of beta versions of the previous version, there will eventually be a formal version, a version that is used by the final delivery user. This version is sometimes referred to as the Standard Edition. In general, release does not appear as a word on the software cover, instead of the symbol (R).

2. Version naming specification

The software version number consists of four parts, the first 1 is the main 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 version number, the Greek version number has 5 kinds, namely: base, alpha, Beta, RC, release. For example: 1.1.1.051021_beta.

3. Revision rules for version number setting

* Major Version number (1): When the function module has a large change, such as the addition of multiple modules or the overall architecture changes. This version number is determined by the project to modify.
* Sub-version number (1): When the function has a certain increase or change, such as increased access to control, add custom views and other functions. This version number is determined by the project to modify.
* Stage version number (1): usually bug fixes or some small changes, to frequently publish revisions, time interval, fixed a serious Bug can be released a revision. This version number is determined by the project manager to modify.
* Date version number (051021): Used to record the current date of the modified item, and changes to the project every day need to change the date version number. This version number is determined by the developer to modify.
* Greek alphabet Version number (Beta): 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. File Naming conventions

The file name consists of four parts: the first part is the project name, the second part is the description of the document, the third part is the version number of the current software, the fourth part is the file phase identification plus file suffix, for example: Project outsourcing platform test report 1.1.1.051021_beta_ B.xls, this file is a test report document for the project outsourcing platform, with the version number: 1.1.1.051021_beta.

If the same version of the same phase of the file has been modified more than two times, then the stage identification is digitally identified, each modification of the number plus 1, the Project Outsourcing platform test report 1.1.1.051021_beta_b1.xls.

When more than one person submits the same document at the same time, it can be distinguished by the addition of the name or abbreviation after the stage identification, for example: Project outsourcing platform test report 1.1.1.051021_beta_b_liuqi.xls. When this file is submitted again, you can also add a serial number after the name or initials, for example: Project outsourcing platform test report 1.1.1.051021_beta_b_liuqi2.xls.

5. Phase identification of the version number

Each version of the software includes 11 stages, which are described in detail in the following steps:

Stage name Stage identification
Demand control A
Design Phase B
Encoding 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