Hello guys, I'm talking about the src:double-conversion package (popcon >= 70k), and a choice for the post-Buster stage.
The upstream doesn't follow semantic versioning convention at all. Recently they have changed the SOVERSION to 3: https://github.com/google/double-conversion/commit/4199ef3d456ed0549e5665cf4186f0ee6210db3b But that doesn't imply any ABI or API change. IIRC their last major version bump was merely due to directory layout change... Should I bump the SOVERSION and trigger a transition after the Buster release? (I think it's pointless, as it triggers pointless rebuild for many packages including Qt) Or ignore the upstream SOVERSION bump and track the changes by myself? Reviewing every line of upstream code change is relatively easy for src:double-conversion. I guess the later solution is the correct choice in my case? [1] https://github.com/google/double-conversion [2] https://tracker.debian.org/pkg/double-conversion
