Why the SOVERSION bump? ...Why the release at all?
ferdnyc opened this issue · 1 comments
This is really more a question than an issue, and probably not even a good place to bring it up, but it's the best option I have and I'm really just trying to understand why libopenshot-audio was not only released as 0.1.6, but the SO version was bumped from 5 to 6 as part of that release.
Not only were there no API changes between v0.1.5 and v0.1.6, but the entire set of changes between v0.1.4 and v0.1.6 (19 commits total) consists of:
- One header include being moved to a slightly different place in the same file (7343b07)
- One slight modification of the
CMakeLists.txtfile (f489d3c) - Two commits to bump the version, once to 0.1.5, then again to 0.1.6 (0c5e0dc, c5596c8)
- Sixteen commits that made modifications to
.gitlab-ci.yml
...Yeah, libopenshot and openshot-qt were releasing, and pushing out a new libopenshot-audio with them probably seemed expected. And, there was that one header-include change. But why in the world would 0.1.6 be bumped to libopenshot-audio.so.6, when there was not only no API change, but no new code in it at all?
This issue is old enough to no longer be relevant.