@mms It's a tricky one.
I don't necessarily blame the #wlroots developers here, but each release has breaking changes which they could do better to document/manage.
Take the release notes:
https://gitlab.freedesktop.org/wlroots/wlroots/-/releases
Some of this information is excellent, but doesn't go far enough. When you have a API in flux, having tooling to help might be worthwhile.
#hare #harelang did this with their hare-update(1) tool recently:
https://harelang.org/blog/2025-06-11-hare-update/
I'd rather see something like #coccinelle scripts in #wlroots to help with the transition, akin to what #harelang are doing.
I know #hikari is coming from 0.15 as its starting point, but the fact remains there's going to be further breaking changes, and I feel this should be addressed.
I might have to see what I can do to help as I do feel this is important.
I know that if the delta between releases is small, the changes might be small, but that's not guaranteed to cause big, sweeping changes. Case in point is the whole wlr_output_damage deprecated for wlr_damage_ring -- we're not just talking changes to the API, but rather, changes in *functionality* which I still don't see documented anywhere.
Hmm. The future.... great....