As it stands, all changes since 1.3.1 maintain ABI compatibility. So the next release can be 1.3.2 (and so 1.3.2a1 the first pre-release).
fyi. assessing ABI changes can be difficult. A first pass check is to look for changes to installed/public headers. In this case, only non-functional changes to URLs.
As an automated check, run ./abi-diff.sh 1.3.1 HEAD which wraps abi-dumper and abi-compliance-checker. Currently two separate reports are produced for the two installed libraries pvxs and pvxsIoc. This script currently assumes the a Linux host.
As it stands, all changes since
1.3.1
maintain ABI compatibility. So the next release can be1.3.2
(and so1.3.2a1
the first pre-release).fyi. assessing ABI changes can be difficult. A first pass check is to look for changes to installed/public headers. In this case, only non-functional changes to URLs.
As an automated check, run
./abi-diff.sh 1.3.1 HEAD
which wrapsabi-dumper
andabi-compliance-checker
. Currently two separate reports are produced for the two installed librariespvxs
andpvxsIoc
. This script currently assumes the a Linux host.Beyond this things get difficult, and become a question of judging whether the semantics of a function changes enough to be considered incompatible.