Attention is currently required from: laforge, osmith.
1 comment:
Patchset:
We should not have "unavoidable" API breaks in libosmo-sigtran. Something is wrong here. […]
It's simple: I already fixed all users of libosmo-sigtran to avoid using structs.
Hence, structs can finally (it should have been like that since the start) be made private.
This means I can now modify structs inside the library, which will be needed to implement AS loadsharing.
This also means anyone, in the future, can add new features without breaking ABI/API again.
So, imho, here we can accept that broken user code accessing structs is not going to build with newer versions of the library without applying a small patchset (already available in master and/or gerrit), or keep breaking ABI again and again because we don't want to fix the root problem, also in the process making my time 10x times more difficult to implement the features.
I'm the first one willing to keep ABI stable, but if we want to do that then we need to reasonable and stop making tons of stuff public-first before there's even a known user of those APIs/structs. Otherwise all this is nonsense imho.
BTW, this is still happening with newer libraries like libosmo-pfcp, despite I think I'm raising the topic at review time here and there.
To view, visit change 38698. To unsubscribe, or for help writing mail filters, visit settings.