https://bugs.kde.org/show_bug.cgi?id=433090
--- Comment #10 from Antonio Rojas <aro...@archlinux.org> --- > Though I'm not sure I understand the concern. If pim devs don't pay > attention to the ABI then in what scenario would a distro not rebuild > everything? Or I guess to preempt the answer a bit, if distros can tell if > ABI was broken, why can't we, KDE, and bump the version when that happens. My current workflow is to manually test every out-of-release-service user after each major release, and rebuild stuff when necessary. I suppose bigger distros have resources to check for ABI breakage properly. I was assuming your alternative (b) would mean bumping the soversion on every release, including minor ones (using only the major version number wouldn't make sense given the date-based versioning that release service uses). But, given that PIM packages have a different internal version number from the release service version, (5.16.x currently), having 5.16 as the soversion would be a reasonable implementation of (b), so it only gets bumped on major releases. -- You are receiving this mail because: You are watching all bug changes.
