Show Compositor Version in Compositor Compatibility

[Ferdi265]

Wayland Application developers might want to know since which version of some compositors a specific Wayland protocol is supported before adding it to their application or before bumping the version.

The current compositor data in /src/data/compositors currently only has compositor versions or release numbers in commit messages.

One simple way to improve this a bit would be to just show the release of the last recorded compositor version next to or below the date of last update, which would improve the current state by a lot since "supported in Sway 1.8" communicates a lot more information in one glance than "supported in Sway since 07/01/2023". This could be easily added just by adding something like a "compositorVersion": "1.8" member to the compositor info json files.

Ideally the "supported since" information should be kept per-global or per-protocol, so developers of apps that want to continue to support older releases like Sway 1.7 or KWin 5.24 (for Ubuntu LTS) can easily judge what protocols and versions they can afford to require to be present. This would require more changes to the compositor info format, but also wouldn't be much more than adding compositor version and/or timestamp members into the per-global dictionaries.

[ferdnyc]

Inspiration could be taken from MDN's Browser compatibility tables (which are themselves influenced by caniuse.com).

For example, a section of the compatibility table for the <img> tag, showing what version(s) of what browsers support certain attributes or features, including which features are deprecated (trashcan icon next to onerror), and when support was removed for some features in Firefox 91: