Hi Philipp and mailing list,
in today's meeting with Pau, Vadim (and Harald who had to go before the decision; would also have been nice to have Philipp there, would probably have been good if I said so explicitly before it), we decided to do the following:
* tag no libosmocore release * tag osmo-pcu from master, but revert the patch that requires a new libosmocore beforehand (new minor version) * tag osmo-bts with cherry picked PCUIF 12 patches (new patch version) * tag osmo-bsc with cherry picked PCUIF 12 patches (new patch version)
It isn't perfect regarding semver but this solution was the most reasonable in our opinion. The patches are here: https://gerrit.osmocom.org/q/topic:pcuif12-releases
On 11.12.23 15:11, Philipp Maier wrote:
Yes, I think this makes sense. Unfortunately, when the PCUIF version number is incremented, this will automatically affect OsmoPCU, OsmoBTS and OsmoBSC equally. (The PCUIF version number has to be incremented when protocol details change, in particular when new struct members are added.)
We also thought about how to make this more elegant in the future, and had the idea of using TLV instead. Created this issue for future reference: https://osmocom.org/issues/6303
Best regards, Oliver