Follow a common versioning scheme
Bug #1949004 reported by
Anton
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNU Arm Embedded Toolchain |
New
|
Undecided
|
Unassigned |
Bug Description
Hello,
I noticed each new release has its own non-standard scheme:
9-2020-q2-update
10-2020-q4-major
10.3-2021.07
10.3-2021.10
It might sound logical for a human eye, but it is hard to automate and monitor such random schemes.
That breaks software like https:/
Please choose one and follow it. See the following for your references: https:/
The semantic scheme would be:
4.2.1 (major.minor.patch)
Thank you
To post a comment you must log in.
This also makes life more difficult for the xPack GNU Arm Embedded GCC, but I already got used for each new release to have an unusual name.
My release numbering scheme looks like:
10.3.1: the original GNU version
10.3.1-2: the second Arm release of GNU 10.3.1
10.3.1-2.1: the first xPack release of the second Arm release of GNU 10.3.1
10.3.1-2.1.1: the first xpm release of the first xPack release of the second Arm release of GNU 10.3.1
Arm could use something like 10.3.1-2, instead of the random strings.