1b8021494Sopenharmony_ciVersioning 2b8021494Sopenharmony_ci========== 3b8021494Sopenharmony_ci 4b8021494Sopenharmony_ciSince version 3.0.0, VIXL uses [Semantic Versioning 2.0.0][semver]. 5b8021494Sopenharmony_ci 6b8021494Sopenharmony_ciBriefly: 7b8021494Sopenharmony_ci 8b8021494Sopenharmony_ci- Backwards-incompatible changes update the _major_ version. 9b8021494Sopenharmony_ci- New features update the _minor_ version. 10b8021494Sopenharmony_ci- Bug fixes update the _patch_ version. 11b8021494Sopenharmony_ci 12b8021494Sopenharmony_ciWhy 3.0.0? 13b8021494Sopenharmony_ci---------- 14b8021494Sopenharmony_ci 15b8021494Sopenharmony_ciVIXL was originally released as 1.x using snapshot releases. When we moved VIXL 16b8021494Sopenharmony_ciinto Linaro, we started working directly on `master` and stopped tagging 17b8021494Sopenharmony_cinamed releases. However, we informally called this "VIXL 2", so we are skipping 18b8021494Sopenharmony_ci2.0.0 to avoid potential confusion. 19b8021494Sopenharmony_ci 20b8021494Sopenharmony_ciUsing `master` 21b8021494Sopenharmony_ci-------------- 22b8021494Sopenharmony_ci 23b8021494Sopenharmony_ciUsers who want to take the latest development version of VIXL can still take 24b8021494Sopenharmony_cicommits from `master`. Our day-to-day development process hasn't changed and 25b8021494Sopenharmony_cithese commits should still pass their own tests. However, note that commits not 26b8021494Sopenharmony_ciexplicitly tagged with a given version should be considered to be unversioned, 27b8021494Sopenharmony_ciwith no backwards-compatibility guarantees. 28b8021494Sopenharmony_ci 29b8021494Sopenharmony_ci[semver]: https://semver.org/spec/v2.0.0.html 30b8021494Sopenharmony_ci "Semantic Versioning 2.0.0 Specification" 31