Re:OpenSSL versioning and license changes
by KwanEsq on Wednesday November 28, 2018 @02:01PM
(#18554513)
Yes, so far as I can tell. While I wouldn't personally call that text ambiguous, it is poorly worded; the "only" from "will only be guaranteed" would be better moved to make the third sentence in your quote start "Previously we only guaranteed[...]".
Re:OpenSSL versioning and license changes
by dimman on Wednesday November 28, 2018 @02:23PM
(#18554740)
>Does this mean 3.0.0, 3.0.1, 3.1.0 and 3.1.1 will all be ABI/API compatible?
Just to clarify (given my assumption that semver apply): 3.1.0 might contain new features compared to 3.0.z, those won’t be backported, but code written/compiled against 3.0.0 will continue to work fine on 3.y.z
Re:OpenSSL versioning and license changes
by wolfgang42 on Wednesday November 28, 2018 @04:05PM
(#18555690)
> given my assumption that semver apply
Per the post, "we are not at this stage directly adopting semantic versioning," though from the sounds of it they're going to try to make the version numbers at least closer to what's expected of semver.
"In practical terms our “letter” patch releases become patch numbers and “fix” is dropped from the concept. In future, API/ABI compatibility will only be guaranteed for the same MAJOR version number. Previously we guaranteed API/ABI compatibility across the same MAJOR.MINOR combination."
Does this mean 3.0.0, 3.0.1, 3.1.0 and 3.1.1 will all be ABI/API compatible?
This reads a bit ambiguously at face value in the announcement.