Android development, version number management summary android:versionCode
In Android development, during the iterative process of the project,
android:versionCode="19720030708"
android:versionName="3.7.8"
For android:versionCode="19720030708" arrangement rules, refer to the official Android documentation
19: stands for android sdk API Level
720: Represents the maximum screen dp that this APP supports and adapts to
03: Two-digit major version number
07: Minor version number
08: revision number
And android:versionName="3.7.8" is the version name released to the outside world, which is divided into three paragraphs
Major version number. Minor version number. Revision number
Corresponding to the application in project management
.version number naming convention
The version number is composed of major version number, minor version number and revision number. For major changes in the version, the major version number is incremented by 1, and the minor version number and revision number are reset to zero. For relatively minor changes to the version, the major version number remains unchanged, the minor version number is incremented by 1, and the revision number is reset to zero. When a bug appears and needs to be revised after a version is released, at this time, the major and minor version numbers remain unchanged, and the revision number increases by 1.
Note: For proactive program functionality changes, the major or minor version number should be incremented and should not be reflected by the revision number. The revision number is only used to revise the bugs of the released version, and the size of the revision number of a version can reflect the stability of a version after it is released to some extent.
Reference documentation:
http://www.cnblogs.com/zhuawang/p/4015458.html