No soname version bump for version 0.30.0

[dbermond]

There is no soname version bump for version 0.30.0, as the shared library remains with version 0.29 (libopenjph.so.0.29).

In previous versions, minor point releases like this (0.28.0 -> 0.29.0, 0.27.0 -> 0.28.0, and so on) carried a soname version bump.

Is 0.30.0 API and ABI compatible with 0.29.0? Or client applications linked against libopenjph.so.0.29 from version 0.29.0 would require a rebuild when upgrading to 0.30.0?

[daveshenal]

OpenJPH's build (ojph_version.cmake) doesn't take the version from the git tag... it parses OPENJPH_VERSION_MAJOR/MINOR/PATCH straight out of src/core/common/ojph_version.h, and that's what feeds the SOVERSION/soname. If libopenjph.so.0.29 is what gets built from the 0.30.0 release, the most likely explanation is that ojph_version.h itself still says OPENJPH_VERSION_MINOR 29 - i.e. the header just wasn't bumped before tagging, even though the version number everywhere else (tag, changelog, README) says 0.30.0.

This wouldn't be a first: the 0.27.1 release notes literally say "Forgot to bump version in my previous release". Same exact class of mistake happened before and needed a quick patch release to fix.

So to directly answer your question... there's no indication 0.30.0 was deliberately kept ABI compatible with 0.29.0 (nothing in the project's history suggests they track real ABI compatibility rather than just bumping the soname every minor release on principle) so this looks like the version header just got missed this time.

Worth doing: check src/core/common/ojph_version.h in the 0.30.0 tag directly... if OPENJPH_VERSION_MINOR still reads 29 there, that confirms it, and it's worth flagging to @aous72 for a quick 0.30.1 (as happened with 0.27.1). Until that's confirmed/fixed, I'd treat client binaries as not verified ABI-compatible and rebuild against 0.30.0 rather than relying on the unchanged soname.

[aous72]

I am sorry; it was late last night and I was tired working on the repository the whole day.
I will fix this next, by releasing version 0.30.1.