https://bugs.kde.org/show_bug.cgi?id=396713
--- Comment #8 from Alexander Semke <alexander.se...@web.de> --- (In reply to Antonio Rojas from comment #7) > (In reply to Alexander Semke from comment #6) > > (In reply to Antonio Rojas from comment #5) > > > A major release in KDE Applications is every 4 months, not every year. So, > > > unless you guarantee that you only plan to make ABI breaking changes in > > > the > > > xx.04 cycles and not in the xx.08 or the xx.12 ones, this system doesn't > > > make much sense > > Yes, but the leading/major number stays constant for all releases within one > > year - 18.04, 18.08 and 18.12. So, as long as you link against > > libcantorlibs.so.18, or even libcantorlibs.so, everything should be fine, > > shouldn't it? > > No, it isn't. If you commit an ABI-breaking change in June to master, it > will end up in the 18.08 release. This release will have a different ABI > than 18.04 even though it has the same soversion, packagers won't notice > that they need to rebuild stuff that links to it, leading to breakage. > The only way the current schema makes sense is if you only allow breaking > ABI between December and April, which seems to me a rather peculiar workflow Ok. I got your point. Let us check how this is done in other KDE frameworks and adjust accordingly. As the author of LabPlot I'd rather like to combine both projects to get more tigher integration and to also avoid this kind of problems with the stability of the ABI... -- You are receiving this mail because: You are watching all bug changes.
