You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you add functionality, without breaking the API, you usually issue a minor release, and this means that the version (major version) remains the same.
Semantic versioning is not compatible with Unix versioning because Unix requires that the compiled (possibly shared) library be interchangeable between versions.
What is the feature you are proposing to solve the problem?
Consider adding an soversion that gets incremented with each minor release (using the semantic convention).
Currently, the release script does not update the soversion. The soversion should get incremented with minor release. Currently, it does not get incremented at all unless there is a major release:
That is, currently the soversion is just the major semantic version, but that's not correct. All librairies with the same soversion must have the same exported functions with the same function signatures.
What alternatives have you considered?
I don't think that there is a sane alternative short of dropping the semantic versioning and adopting Unix versioning where each. That would mean making a major release the minute a new function is added.
The text was updated successfully, but these errors were encountered:
lemire
changed the title
add soversion
update soversion with each minor release
Jan 6, 2025
What is the problem this feature will solve?
Currently the ada library uses semantic versioning.
https://semver.org/
If you add functionality, without breaking the API, you usually issue a minor release, and this means that the version (major version) remains the same.
Semantic versioning is not compatible with Unix versioning because Unix requires that the compiled (possibly shared) library be interchangeable between versions.
What is the feature you are proposing to solve the problem?
Consider adding an soversion that gets incremented with each minor release (using the semantic convention).
Currently, the release script does not update the soversion. The soversion should get incremented with minor release. Currently, it does not get incremented at all unless there is a major release:
ada/tools/release/lib/versions.py
Line 7 in a383f41
That is, currently the soversion is just the major semantic version, but that's not correct. All librairies with the same soversion must have the same exported functions with the same function signatures.
What alternatives have you considered?
I don't think that there is a sane alternative short of dropping the semantic versioning and adopting Unix versioning where each. That would mean making a major release the minute a new function is added.
The text was updated successfully, but these errors were encountered: