Axel it is so true, thanks.
Please do it.
+1
Am Do., 24. Sept. 2020 um 18:54 Uhr schrieb Axel Dörfler <
axeld@xxxxxxxxxxxxxxxx>:
Am 24/09/2020 um 13:35 schrieb Adrien Destugues:
[...]
One example for this is the Services Kit rework from leorize, which
completely changes the API because the way it is currently doesn't
work. Should we merge this before R1? In which case our commitment to
"beta" doesn't really hold, we are breaking compatibility between
beta and final release, and it shouldn't be the case. Should we delay
it to R1.1, meaning that R1 would only be a stable/final platform
only for 6 months to a year, and then be replaced with another one?
What's the difference between R1 and a beta then? Should we delay any
such changes to R2, and living with a broken API for a few more
years?
As you mentioned, I think the current Services API should not have ended
up in a shared library. But the same is true for the new one -- it
should grow a little before doing so first.
I would move both APIs into two different static libraries. It does
break the ABI, but I think that's acceptable for a Beta (even if we try
to avoid it, better do it now, than live with a mess for a couple of
years :-)).
Bye,
Axel.
