The most important thing to keep in mind for this is that the build numbers should be increasing so that subsequent versions can be installed over previous versions. This can be expressed in written form as A.B.C (X) or A.B.C.X (where A is the major version, B is the minor version, C is the patch version and X is the build number). Usually this is referred to this as the Build Number. There is then usually need to have a more precise version numbers for each individual build so developers, clients and QA team members can identify the exact code that the build contains between releases to end users. In iOS, the semantic version is the same as the version number that is used. The semantic version is the versionName and the version number is the versionCode. ensuring all major & minor versions are the same on related iOS & Android at any point in time).įor Android, the semantic version is different to the version number that is used when determining whether a particular version of the app can be installed over another version. should 2.10.0 roll over to 3.0.0 - not according to the semantic versioning rules!) is usually up to the individual project and may be adjusted to keep app platforms or other systems in line (e.g. What the version number used and what the sequence should be (e.g. This is normally for small bug-fixes or the like Patch numbers change when a new build of the software is released to customers.
0 kommentar(er)
