Version: 0.0.1 + 1Copy the code

Version number format: < major version number >.< Minor version number >.< Release number >+ < Build number >

The initial version number is 0.0.1+1

Management Rules:

Major Version number

  1. The main component of the product shall be significantly modified, and the main version number shall be increased by 1;

  2. The interface protocol between the main components of the product is significantly modified, and the main version number is increased by 1;

Minor Version

  1. When the major version number changes, the minor version number is set to 0.

  2. Data structure changes (except for new or modified comments), the minor version number is increased by 1;

  3. If the minor version number accumulates to more than 20, the major version number is carried, and the major version number is added by 1.

Reset the minor version number to 0.

Release number

  1. When the major version number or minor version number changes, the Release number is set to 0;

  2. If the released version has no data structure change, the Release number is increased by 1.

For example:

When a new version is released, the major, Minor, or Build (if any) version number should be updated, depending on the size of the change.

When there are major updates, the major number will be added. When there is a major update, but not a major update, the minor version is updated.

If the update is minor, such as bug fixing, the build version number will be updated. Here’s an example:

1.0 – – > 1.0.2 1.0.1-1.1-1.1.1-2.0-2.1-2.1.1-3.0 -… In the example above,

1.0 to 1.0.1 to 1.0.2, 1.1 to 1.1.1, 2.1 to 2.1.1 are minor updates, such as bug fixing, interface tweaks, etc.

1.0.2 to 1.1 and 2.0 to 2.1 are major updates, including many new features;

While 1.1.1 to 2.0 and 2.1.1 to 3.0 are major updates, for example, the interface or functions of the APP are completely changed;