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