App version number definition and Description basics

Three more popular naming formats for version control

1. GNU-style version number naming format

   The major version number. Minor version number [. fix version number [. Build version number]]

   Example: 1.2.1, 2.0, 5.0.0 build-13124

2. Windows-style version number naming format:

   The major version number. Minor version number [fix version number [. Compile version number]]

   Example: 1.21, 2.0

3. Net Framework-style version number naming format:

   The major version number. minor version number [. build version number [. Fix version 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.

GNU Release Notes

    版本格式：主版本号.次版本号.修订号，版本号递增规则如下：    主版本号：当你做了不兼容的 API 修改    次版本号：当你做了向下兼容的功能性新增    修订号：当你做了向下兼容的问题修正

Major Version number:

The main version represents a new version of the incompatible API, which represents a large update in the app.
Early in the development of the project in the case of an unstable API, generally starting at 0, indicating that the project public API is unstable, may change at any time.
The official stable version, the first version of the app starts at 1, and when the project changes greatly, the major version number + +, the minor version number and the revision number are zeroed.

Minor version number:

Minor version number marked to do a compatible with the old API processing, in the app said on the original basis added some function time + +, revision number zero

Revision number:

Bug fixes and small-scale changes to the project, the same app

Version Number Rule description

In the ordinary development, we will refer to some third-party jar package or compile some open-source library, through the above instructions, we can according to the reference jar package, class library version number, appropriate to upgrade. For example, referencing a third-party library xxx-2.1, Then we can rest assured in the late use of >=2.1, <3.0 all version updates, because the main version number is unchanged, only modified minor version number (backward compatibility modification and new), revision number (bug fix), no compatibility issues, major version added incompatible with the old version of the modification

App version number definition and Description basics