Naming rules and formats for Version Management in program development

Preface:

Naming rules for software released on the Internet. Although you can name your own released software, you still have a lot of conversations about the rules.

Article 1:

Version 1

1.1 Official version

Enhance: the enhanced version or enhanced version belongs to the official version.

Full Version: The full version belongs to the official version.

Release: release version with Time Limit

Upgrade: upgraded

Retail: Retail Edition

Plus: enhanced version. However, most of these enhancements are made on the program interface and multimedia functions.

1.2 test version

Alphal: beta version

BETA: External Beta

M version: milestone, meaning the milestone version at the end of each development phase

Trail: trial version (containing certain restrictions, such as time and functions, may also change to the official version after registration)

RC: Release
Candidate indicates the release countdown. This version has completed all functions and cleared most bugs. At this stage, only bugs will be removed, and no major changes will be made to the software.

RTM: release to Manufactur, meaning released to the manufacturer, which is basically the final version

GA: generally available, final version

1.3 product version

Shareware: shared version

Free: Free Edition

Cardware: a type of shared software. You only need to send an email or postcard to the author. (Some authors provide registration codes). Currently, this form is rare.

Demo: Demo Version

Preview: preview

Corporation & Enterprise: Enterprise Edition

Standard: Standard

Mini: mini edition (Lite version) with only the most basic functions

Premium: Premium Edition

Professional: Professional Edition

Express: Special Edition

Deluxe: Deluxe Edition

Regged: Registered version

1.4 language classification

CN: Simplified Chinese version

CHT: Traditional Chinese Version

En: English version

Multilanguage

1.5 Other categories

Rip: refers to the separation of useful content (core content) from the original file (generally a CD or CD image file) to remove useless documents, such as PDF instructions, video demos and other things can also be considered as lite... However, the main content function is indispensable at all! In addition, DVDRip separates the video and audio directly from the DVD disc as files.

OEM: original equipment manufacturer, which indicates the version provided to the computer manufacturer.

FPP: Full packaged product (FPP)-retail, which is a retail version (boxed software). The flags of these products are marked with "FPP ".

Vlo: volume licensing for organizations
, Group batch licenses (a large number of procurement authorization contracts), which is a preferential method for group purchases.

This version is subdivided into the following five versions based on the number of purchases:

Open license-open license

Select license-select license

Enterprise Agreement-enterprise agreement

Enterprise subscription agreement-enterprise Subscriber Agreement

Academic Education license-academic Volume Licensing

2 version number

2.1 No. Syntax x. y. Z

X: The main version number, which indicates the major enhancement of the product functions provided to the customer. In an extreme example, the rise of the main version number indicates that the product now has a brand new function class. From the market and license perspectives, the major version number upgrade is equivalent to purchasing a completely independent product. From the developer's point of view, the iteration of a major version number almost always reflects the life cycle of a new independent branch or its trunk.

Y: feature version number, which indicates that some features have been added to the product, or the features described in the original document have been significantly modified. A metric used to determine when the feature version number needs to be modified is the product feature manual. The feature version upgrade of a product is an important mechanism to maintain product competitiveness among the main versions.

Z: the bug fix version number, which indicates the level of defect maintenance behavior performed on the version. Version fixes are an important mechanism for stabilizing the market and minimizing the cost of customer technical support.

2.2 Support the serial number syntax x. y. Z [A | B] for alpha and beta release

A: alpha version.

B: beta version.

|: Indicates the logical operator "or"

[]: Indicates that internal elements are selectable.

Note: after the last Alpha or beta release, a carry is given to the official customer release version to make it 0 at the position of "Z. For example, 2.2.6 is officially released by the customer and replaced by version 2.3.0.

3. Software release rule example

3.1 brief description

Used for file directories and compressed packages.

ProjectName-x.y.bYYYYMMDD [. N] (daily build)

ProjectName-x.y.Mn (milestone)

ProjectName-x.y.Betan (test release)

ProjectName-x.y.RCn (stabilization release)

ProjectName-x.y.RTX [. Rn] (official release, or official release with update package)

3.2 Detailed Description

Used for the internal description of the software, such as "about the software ".

Projectname [V/version] x. y. BN. un. [Mn/betan/rcN/RTx [. Rn]. byyyymmdd [. N]

Document version release rules:

DocumentName-Vx.y [. Rn] (release, or release with Revision)

Brief Description Example:

Release of xowidgets:

XoWidgets-1.0.b20080101

XoWidgets-1.0.b20080101.2 (second release on the Day)

...

XoWidgets-1.0.M1 (milestone version 1)

XoWidgets-1.0.b20080601

XoWidgets-1.0.b20080601.2 (second release on the Day)

...

XoWidgets-1.0.M2 (milestone 2)

...

XoWidgets-1.0.Beta1 (test version 1)

XoWidgets-1.0.Beta2 (Beta 2)

...

XoWidgets-1.0.RC1 (prerelease version 1)

XoWidgets-1.0.RC2 (prerelease version 2)

...

XoWidgets-1.0.RTX (official version of interaction)

XoWidgets-1.0.RTX.R1 (Official interactive version with R1 update)

XoWidgets-1.0.RTX.R2 (Official interactive version with R2 update)

...

Example:

Xowidgets v1.0.2480.512.rtx. r2.b20081201

Note:

(1) x-major, major version number

(2) Y-minor, minor version number (even numbers are stable versions, and odd numbers are development versions)

(3) bn-build number, build number

(4) UN-update number, update number

(5) yyyymmdd-yyyymmdd

(6) N-incrementing integer

 

Article 2:

Naming Conventions for excellent projects-Archives
In the GNU naming convention, the file name is added with the main version number, the minor version number, and the patch number.

Keeping the file name in line with the GNU naming rules is a matter of courtesy. The naming rule of GNU is to prefix the file name with all letters in lower case, followed by a break, followed by a version number, extension description and other suffixes.

Here is an example: assume that you have a project named "foobar", and her current progress is the first version, the second release, and the third patch. If she only has one archive (maybe all the source code ),
Her name should be:
Foobar-1.2.3.tar.gz
Source code Archive
Foobar. LSM

LSM file (this LSM file is required if you need to submit this project to metalab ).
Do not set the name to the following:

Foobar123.tar.gz
(This can be misunderstood as a project named "foobar123)
Foobar1.2.3.tar.gz

(This can be misunderstood as Version 2.3 of a project named "foobar1)
Foobar-v1.2.3.tar.gz

(Many handlers will understand her as a project named "foobar-v1)
Foo_bar-1.2.3.tar.gz

(When reading an underscore, it is not easy for others to input and remember)
FooBar-1.2.3.tar.gz

Do not write this statement unless you are willing to be seen as a man in the city. This writing method is also hard to read, input, and remember.

If you want to distinguish the source code package from the Binary Package, or want to distinguish different types of Binary packages and Binary packages compiled by different compilation options, in the "extension description" section of the file name, the extension description follows the version number. That is to say, you can name it like this:

Foobar-1.2.3.src.tar.gz
(Source code package)
Foobar-1.2.3.bin.tar.gz

(Binary Package, but not specific)
Foobar-1.2.3.bin.ELF.tar.gz
(Binary Package in ELF format)

Foobar-1.2.3.bin.ELF.static.tar.gz
(Binary Package in ELF format of the static Link Library)

Foobar-1.2.3.bin.SPARC.tar.gz
(Binary Package in space format)

The handler does not need to use the name in the format of "foobar-elf-1.2.3.tar.gz", because it is hard to explain the fix such as "-elf.

A good name will contain the following items in order:
Project name prefix
Break number
Version Number
Point
"Src" or "bin" mark (optional)

Point or broken number (recommended)
Binary format and options (optional)
Archive and compression suffixes

Obfuscation occurs when two different projects use the same master name. They are metalab index files (http://www.ibiblio.org/pub/Linux
) And Freshmeat Appendix (http://www.freshmeat.net
). Another good place is SourceForge.
Http://www.sourceforge.net
), Where you can perform a name check.

2. select a good license and copyright Description: Theoretical
Open source and copyright
Almost all non-public objects are copyrighted, and some even have more than one copyright.

The Open Source Software field is another scene; here copyright is used to protect licenses. The only right of the copyright holder is to ensure the implementation of the license.
Use a license that complies with the open-source definition

The definition of open-source software (OSD) is a public license standard. OSD itself is not a license; rather it provides a minimum set of licenses that must be included to become an open-source license.
OSD and other auxiliary resources can be obtained from the open source dynamic site.
If there is no special need, it is best not to create a self-built license
4. Good Development habits

Use Autoconf/automake/autoheader

If you write a program in C, remember to use the Autoconf/automake/autoheader tool to handle various portability issues. Use these tools to collect system configuration information and create makefile files. Currently, many people only want to use "Configure;
Make "is a simple command that can be compiled cleanly. In fact, this is what everyone does.
Check the code carefully before publishing.
Carefully check documents and readme files before release

You are advised to use the spelling check tool to check the document before it is published.
5. Good experience in creating project release packages
Make sure that an independent new directory is created when the tar package is decompressed.
Overview of the entire project

The URL of the project's WWW site (if any)
Points out the system environment where the developer compiles the entire project, and points out the potential portability Problems of the project.

Structure information of important files and subdirectories
Compile/install steps, or specify the file name of the information (usually the install file)

List of project owners and participants, or the files where the information is stored (usually credits files)

Recent progress and news about this project, or documents containing this information (usually news files)
Follow standard file naming rules

To read readme files, the "brave explorer" must first browse and decompress the file name under the root directory of the project file. These file names are themselves conveying a lot of information to the reader. If you follow standard naming rules, you can give those explorers valuable evidence so that they can better understand your intentions.

Some standard file names and their meanings are listed here. Of course, not all projects must contain all these files during release.
Readme or read. Me

The structure information of the entire project is described in the first document to be read.
Install
Configure, compile, and install this project
Credits

List of all contributors in this project
News
Recent news and progress of this project
History
History and evolution of the project

Copying
Indicate the license terms used in this project (generally using gnu gpl)
License
License Terms and Conditions for this project

Manifest
List of all files for this project
FAQ
FAQs about the plain text format of this project
Tags

Tag files prepared for Emacs or VI
We can see that all capital file names generally indicate that the file is a document for people to read, rather than a component of the project.

Compiling a faq file can help you a lot. If a problem is frequently asked by others, add it to the FAQ document. Then, instruct the user to read the FAQ document before sending a document or submitting an error report. A good FAQ document can reduce the burden on Project maintainers by several orders of magnitude.

In addition, a history file and news file are retained at each release. It is very advantageous to coordinate the time information. Among all other documents, these two documents can help you prepare for some patent infringement laws (although this has not happened so far, it is better to be prepared ).

Prepare for project upgrade

As long as you plan to release a new version for your project, the project will be constantly changing. Some changes are backward compatible. Therefore, you must carefully consider the installation program design issues, that is, to allow different versions of the code of the same project to exist in a system after installation. This issue is especially important for the release of library projects, because you cannot expect that all database-based applications will follow the background of your API specifications.

6. Good document compiling practices
7. Good communication methods
Create a project-related website

If you want to build an online community for users and developers around the project, you 'd better build a website. A standard project website generally includes the following content:

Project features (who will be interested in this project if you want to have it ).
Download the source code of the project.
Specifies how to add a project-related email list.

A list of FAQs.
Project documents in HTML format.
Links to other projects or websites related to or competing with projects.

Some project sites even have anonymous access links pointing to the source code tree (to facilitate tracking of project progress ).
8. good project management experience

For the discussion on the basic development mode and the discussion on the market development mode of "early release", please refer to the article "Cathedral and market.

For more information about psychological motives, Community customs, and conflict resolution, see the article "open up a smart domain.
For a discussion on the basis of open source software economics and various business operation modes, please read the article magic boiler.

It should be pointed out that these articles are not the final arguments of free software development, but they are the crystallization of ideas after careful consideration, there are no other articles beyond their depth (the author of the article hopes that someone else will surpass them one day ).

 

Article 3

1. Version:
V (version): indicates the version number. (For example, Everest ultimate v4.20.1188 beta)
Build: indicates a version number by number or date. (For example, verycd eMule v0.48a build 071112)
SP: Service Pack, upgrade package. (For example, Windows xp sp 2/Vista SP 1)

2. Authorization and function division:
Trial: The trial version usually has time restrictions, and some trial software still has certain functional limitations. Can be registered or purchased as the official version
Unregistered. You can register or purchase the official version.
Demo: demo version. It only integrates several functions of the official version and cannot be upgraded to the official version.
Lite: Lite version.
Full Version: Full version, which belongs to the official version.

3. Language Division:
SC: Simplified Chinese.
CN: Simplified Chinese version
GBK: simplified Chinese characters internal code extension specification edition.
TC: Traditional Chinese version.
CHT: Traditional Chinese Version
Big5: five-digit Traditional Chinese version.
En: English version
Multilanguage
Utf8: Unicode Transformation Format 8 bit, which is not a good solution for the existing Chinese system.

4. Development Phase Division:
ALPHA: beta version for internal communication or testing by professional testers. There are many bugs. It is recommended that you do not install them.
Beta (Beta): A Public Beta version that is used for large-scale testing by professional enthusiasts. This version is not suitable for general users.
Gamma (gamma): a fairly mature beta version, which is almost the same as the official version to be released.
RC: Release Candidate.
RC version. It is the abbreviation of release candidate, which indicates the release countdown. The candidate version, in the Gamma stage, has completed all functions and cleared most of the bugs. At this stage, only bugs will be removed, and no major changes will be made to the software. From alpha to Beta to Gamma is an improved relationship, but RC1 and RC2 are usually a trade-off relationship.
Final: official version.

5. Other Versions
Enhance: the enhanced version or enhanced version belongs to the official version 1.
Free: Free Edition
Release: release has a time limit
Upgrade: upgraded
Retail: Retail Edition
Cardware: a type of shared software. You only need to send an email or postcard to the author. (Some authors provide registration codes). Currently, this form is rare. /S
Plus: it is an enhanced version, but most of it is enhanced on the program interface and multimedia functions.
Preview: preview
Corporation & Enterprise: Enterprise Edition
Standard: Standard
Mini: The mini version is also called Lite version with only the most basic functions
Premium: Premium Edition
Professional: Professional Edition
Express: Special Edition
Deluxe: Deluxe Edition
Regged: Registered version
Rip: refers to the separation of useful content (core content) from the original file (generally a CD or CD image file) to remove useless documents, such as PDF instructions, video demos and other things can also be considered as lite... However, the main content function is indispensable at all! In addition, DVDRip separates the video and audio directly from the DVD disc as files.
RTM: this is the final version. The English version is release to Manufactur, which means release to the manufacturer.
Original equipment manufacturer (OEM)
You may license products through an original equipment manufacturer (OEM). These products, such as Windows operating systems, come installed when you purchase a new computer.
OEM software is a version for computer production plants.

Full packaged product (FPP)/retail
Physical, shrink-wrapped boxes of licensed product that can be purchased in a local retail store or any local software retailer.
FPP is a retail version (boxed software). The flags of these products all carry the words "FPP". For example, the flags of the FPP version of the English wxp pro are wxpfpp_en, wx indicates Windows XP, P is professional (H is home), FPP indicates retail version, and EN indicates English. In addition to purchasing in the store, some msdn users can also get the access.
Volume Licensing for organizations (vlo)
You may enjoy potentially significant savings by acquiring multiple product licenses. Depending on the size and type of your organization.
Group batch licenses (a large number of procurement authorization contracts) are a preferential method for group purchases. The volumes of these products are marked with the words "vol". Take the first three letters of "volume" to indicate that they are in batch. For example, the vol version of the English wxp pro is wxpvol_en, wx indicates Windows XP, P indicates Professional (Vol does not have the home version), Vol indicates group batch license version, and EN indicates English. The main way to obtain this information is through group purchases, which can be obtained by some msdn users.

 

Article 4

Currently, there are three mainstream software version number management solutions:

I. Naming rules and formats

1. GNU solution:
Naming rules: Major version number. Subversion number [. Corrected version number [compiled version number]
Comparison: major_version_number.minor_version_number [. revision_number [. build_number]
Examples: 1.1.5, 2.0, 2.1.0 build-1781

2. Windows solution:
Naming rules: Major version number. Subversion number [corrected version number [compiled version number]
Comparison: major_version_number.minor_version_number [revision_number [. build_number]
Example: 1.15, 2.0

3.. NET Framework solution:
Naming rules: Major version number. Subversion number [. Build version number [. Modify version number]
Comparison: major_version_number.minor_version_number [. build_number [. revision_number]
Note: the version number consists of two to four parts: Main version number, minor version number, internal version number, and revision number. The main version number and minor version number are required. The internal version number and revision number are optional. However, if the revision number is defined, the internal version number is required. All defined parts must be integers greater than or equal to 0.

Ii. Some conventions

1. Major: an assembly with the same name but different major version numbers cannot be exchanged. For example, this applies to a large number of product rewriting, which makes backward compatibility impossible.
2. Minor: if the names of the two sets are the same as those of the primary version, but the minor version number is different, this indicates a significant enhancement, but takes care of backward compatibility. For example, this applies to the product's revised version or a new version that is fully backward compatible.
3. Build: different internal version numbers indicate re-Compilation of the same source. This is suitable for changing the processor, platform, or compiler.
4. Revision: The names, major version numbers, and minor version numbers are the same, but the different revision numbers of the Assembly should be completely interchangeable. This applies to fixing security vulnerabilities in previously released assemblies.
5. Only later versions with different internal version numbers or revision numbers are considered as hotfix updates of previous versions.

Iii. Version Number Management Policy

1. GNU solution:
In the initial version of the project, the version number can be 0.1 or 0.1.0 or 1.0 or 1.0.0. If you are a low-profile user, I think you will choose the primary version number 0;
When the project is partially modified or the bug is corrected, the main version number and sub-version number remain the same, and the corrected version number is added to 1;
When some functions are added to the project on the basis of the original, the main version number remains unchanged, the sub-version number is added with 1, and the corrected version number is reset to 0, so it can be ignored;
When the project has been significantly modified or partially corrected, the overall project changes globally, and the main version number is increased by 1;
In addition, the compilation version number is generally automatically generated by the compiler during the compilation process. Only the format is defined and is not subject to human control.

2. Windows solution:
The first project version is 1.0 or 1.00;
When the project is partially modified or the bug is corrected, the main version number and sub-version number remain the same, and the corrected version number is added to 1;
When some functions are added to the project on the basis of the original, the main version number remains unchanged, the sub-version number is added with 1, and the corrected version number is reset to 0, so it can be ignored;
When the project has been significantly modified or partially corrected, the overall project changes globally, and the main version number is increased by 1;
In addition, the compilation version number is generally automatically generated by the compiler during the compilation process. We only define the format and do not manually control it.

Iv. suffix

In addition, you can add suffixes such as alpha, beta, gamma, current, RC (Release Candidate), release, and stable to the end of the version number. You can also add a version number of one digit to the end of the suffix. If a user upgrades the main version of a software and wants to continue the software, the company that issues the Software generally charges the user for the upgrade; if the sub-version number or the corrected version number is upgraded, it is generally free of charge.

Appendix: Common suffixes and descriptions

Alpha internal Beta
Beta external test
Demo Version
The enhance enhanced version or enhanced version belongs to the official version.
Free Edition
Full Version: The full version belongs to the official version.
Shareware shared version
Release of release has a time limit
Upgrade upgrade
Retail Edition
Cardware is a type of shared software. You only need to reply an email or postcard to the author. (Some authors provide registration codes). Currently, this form is rare.
Plus is an enhanced version, but most of this type is enhanced on the program interface and multimedia functions.
Preview
Corporation & Enterprise Edition
Standard
The Mini version is also called Lite version with only the most basic functions
Premium-Premium Edition
Professional-Professional Edition
Express-Special Edition
Deluxe-deluxe edition
Regged-registered version
CN-Simplified Chinese version
CHT-Traditional Chinese Version
En-English Version
Multilanguage

V. Others

Alpha version
This version indicates that the software is only a preliminary finished product. It is usually only communicated within the software developer, and a few of them are released to professional testers. In general, this version of software has many bugs, and it is recommended that you do not install it.

Beta
This version has been greatly improved compared with alpha version, eliminating serious errors, but there are still some defects that need to be further eliminated through large-scale release tests. This version is usually released free of charge by software companies and can be downloaded from related sites. Through tests by professional enthusiasts, the results are fed back to developers and developers can make targeted changes. This version is not suitable for general users.

Gamma
This version is quite mature and is almost the same as the official version to be released. If you can't wait, try it out.

Trial (trial version)
Trial software has been quite popular in recent years, mainly thanks to the rapid development of the Internet. This version of the software usually has a time limit. If you want to continue using it after expiration, you generally have to pay a certain fee for registration or purchase. Some Trial software also imposes certain functional limitations.

Unregistered (unregistered Version)
The Unregistered version is very similar to the trial version, but the unregistered version usually has no time limit. In terms of functions, it imposes certain restrictions on the formal version, such as the registration version and unregistered version of the vast majority of VoIP Software, there is a big gap between the two in terms of call quality. Some of them are similar to the official version, but an annoying message box will pop up to remind you to register, such as ACDSee and smart Chen Qiao Chinese Character Input Software.

Demo Version
It is also known as the demo version, which is the most popular among non-official software. The demo version only integrates several functions in the official version, which is a bit like unregistered. The difference is that the demo version cannot be changed to the official version by upgrading or registering it.
The above are the previous versions of the software official version. Alpha, beta, and gamma can be called test versions. There will always be multiple test versions of mature software, such as Windows 98 beta version, there are nearly 10. So many beta versions, on the one hand, try to satisfy the user's needs for the final product, and on the other hand, minimize bugs in the software. Trial, unregistered, and demo are sometimes collectively referred to as the demo version. These versions have a strong color of advertisement and are a bit preemptible. For ordinary users, they can naturally enjoy them for free.

Official version
The official versions of different types of software are also different.

Release
This version means "the final release version". After a series of Beta versions, there will eventually be an official version. for users, the software purchased for this version will never be wrong. This version is also known as the Standard Edition. In general, release does not appear on the software cover in the form of words, instead of symbols (R), such as Windows NT (r) 4.0, MS-DoS (r) 6.22.

Registered
Obviously, this version is the registration version relative to unregistered. The registration and release versions are the same as the standard versions mentioned below. They are all official versions of the software, but a large part of the predecessor of the registration software is downloaded from the Internet.

Standard
This is the most common Standard Edition, No matter what software, the Standard Edition must exist. The standard edition includes the basic components of the software and some common functions to meet the needs of general users. Its price is relatively higher than that of the first-level version.

Deluxe
As its name implies, it is the "deluxe edition ". The deluxe edition is generally compared with the Standard Edition. The main difference is that there are several more features, and the price will certainly be higher than a large one. It is not recommended for general users. This version is usually prepared for professional users who are pursuing "perfection.

Reference
This version is common in encyclopedias and is famous for Microsoft's Encarta series. Reference is the highest level. Its subject, image, and video editing have greatly increased compared with standard and deluxe versions, and the capacity has increased from one disc to three, and added strong interaction functions, of course, expensive. That can be said, this version of encyclopedia can be regarded as a real encyclopedia, and it is also the first choice for enthusiasts to collect.

Professional (Professional Edition)
The Professional Edition is for some specific development tools and software. Many of the content in the Professional Edition is not available in the Standard Edition, which is extremely important for a professional software developer. For example, Microsoft's Visual FoxPro Standard Edition does not have the ability to compile into executable files, which is obviously intolerable for a complete development project. It cannot be used without FoxPro on the client. If you use the Professional Edition, there will be no such problem.

Enterprise Edition)
The Enterprise Edition is the best in development software (equivalent to the reference edition in the encyclopedia ). With a set of such software, you can develop any level of application software without any obstacles. For example, the famous visual c ++ Enterprise Edition has added several additional features compared with the Professional Edition, such as SQL debugging, extended stored procedure wizard, and support for AS/400 access to OLE DB. The price of this version is unacceptable to common users. For example, Microsoft's visual studios 6.0 enterprise Chinese version costs 23000 yuan.

Other Versions

In addition to the versions described above, there are also some proprietary version names.

Update (upgraded version)
The upgraded software cannot be used independently. During installation, the software of this version searches for the original official version. If it does not exist, the next step is rejected. Such as Microsoft Office 2000 and Windows 9X.

OEM version
The OEM version is usually bundled in hardware and not sold separately. You can sell your products to other companies to retain their copyright. The two parties will enjoy mutual benefit and win two birds in one fell swoop.

Standalone (network) version
The online version is far more complex in terms of functions and structure than the standalone version. if you pay attention to the software quotation, you will find that the prices of some software standalone versions differ greatly from those of the online version, some online versions require a lot of money to add even more client ports.

Popular edition
This version is sometimes referred to as a shared version. It features low price (or even free of charge), single functionality, and strong pertinence (of course, it also takes over the market, combating piracy and other factors ). Different from the trial version, the software of this version generally has no time limit. Of course, if you want to upgrade, you 'd better purchase the official version.

The above are some mainstream software version number management situations. As the software market behavior changes, there are also some new version naming methods, for example, XP in Windows XP is obtained from the second and third letters in experience.

Based on commercial considerations, many software do not strictly follow this rule. Microsoft is the most famous. For example, his nt series version. We are familiar with NT 4.0. Windows 2000,200 was launched in 2003, and Windows XP was withdrawn in 1 year. Windows was launched in. At first glance, the differences between the versions are quite large, but they will find that their internal versions are different, in fact, the changes are not big, but the interface changes a lot. This is what software companies often do. Windows 2000 is NT 5.0, Windows XP is NT 5.1, Windows 2003 is NT 5.2, and now longhorn is the real nt 6.0 ......
++ ++ ++
Common versions

* Alpha (alpha) Internal Beta
* Beta (Beta) External Beta
* This version of Gamma is quite mature and is almost the same as the official version to be released. If you can't wait, try it out.
* Demo version
* The enhance enhanced version or enhanced version belongs to the official version.
* Free Edition
* Lite version, also known as mini version.
* Final official version, released after alpha and beta versions, fixes bugs in the software.
* Pro: Professional edition, which can be used only after the user obtains the registration code.
* Full Version: The full version belongs to the official version.
* Ware Ware shared version
* Release of release has a time limit
* Upgrade
* Retail Retail Edition
* Enterprise Edition

Other Versions

* Cardware is a type of shared software. You only need to reply an email or postcard to the author.
(Some authors provide registration codes). Currently, this form is rare.
* Plus is an enhanced version. However, most of the enhancements are made on the program interface and multimedia functions.
* Preview is a preview version.
* Corporation & Enterprise Edition
* Standard Standard Edition
* The mini version is also called Lite version and has only the most basic functions.
* Premium
* Professional Edition
* Express special edition
* Deluxe edition
* Regged registered version
* CN Simplified Chinese version
* CHT Traditional Chinese Version
* En English version
* Multilanguage multi-language edition
* Build is an internal label, that is, the same version can have multiple labels, such as V1.0 build 203. Generally, the larger the number after the build, the newer the version.

Special version

* Rip refers to directly separating useful content (core content) from the original file (generally a CD or CD image file) to remove useless documents, such as PDF instructions, video demos and other things can also be considered as lite... However, the main content function is indispensable at all! In addition, DVDRip separates the video and audio directly from the DVD disc as files.
* Trial version of TRAIL (which contains certain restrictions, such as time and functions, and may change to the official version after registration)
* RC version. It is the abbreviation of release candidate, which indicates the release countdown. This version has completed all functions and cleared most bugs. At this stage, only bugs will be removed, and no major changes will be made to the software.
* RTM version. This is basically the final version. The English version is release to Manufactur, which means release to the manufacturer.
Original equipment manufacturer (OEM)
You may license products through an original equipment manufacturer (OEM). These products, such as Windows operating systems, come installed when you purchase a new computer.
OEM software is a version for computer production plants.
* Full packaged product (FPP)-Retail
Physical, shrink-wrapped boxes of licensed product that can be purchased in a local retail store or any local software retailer.
FPP is a retail version (boxed software). The flags of these products all carry the words "FPP". For example, the flags of the FPP version of the English wxp pro are wxpfpp_en, wx indicates Windows XP, P is professional (H is home), FPP indicates retail version, and EN indicates English. In addition to purchasing in the store, some msdn users can also get the access.
* Volume licensing for organizations (vlo)
You may enjoy potentially significant savings by acquiring multiple product licenses. Depending on the size and type of your organization.
Group batch licenses (a large number of procurement authorization contracts) are a preferential method for group purchases. The discs of such products all carry the word "vol ".

 

The above materials are from the network for reference only, as shown below:

Http://www.cnblogs.com/gis_gps/archive/2009/05/15/1458053.html

Http://hi.baidu.com/35316/blog/item/4a40a818fa11e30f35fa41c2.html

Http://hi.baidu.com/cpucn/blog/item/6d116b7b1f1b45ff0ad187c7.html