Update wayland.xml to 1.21.92 #608
Conversation
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## master #608 +/- ##
==========================================
+ Coverage 74.01% 74.32% +0.31%
==========================================
Files 53 53
Lines 7607 7621 +14
==========================================
+ Hits 5630 5664 +34
+ Misses 1977 1957 -20
Flags with carried forward coverage won't be shown. Click here to find out more. see 10 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
|
1.21.92 is a beta release, shouldn't we wait for the proper 1.22 release? In any case, could you add changelog entries to wayland-client and wayland-server covering this update? |
That's something I was pondering myself, I'm not sure about your policy on this. To me it seems unlikely that there will be major changes to protocols after they've been officially released, but I'm not familiar with Wayland's track record here. But since new additions don't introduce breaking changes to existing protocols, I think it should be fine to expose unstable additions like this. Wayland protocol extensions are already heavily used in unstable revisions and I think since most compositor/client developers directly using this are likely looking at the protocols themselves, they can make their own decisions about relying on unstable/beta versions. |
|
Ok, so 1.22 has been released now, with no changes since 1.21.92. I'm good with merging this, maybe let's just adjust the changelogs accordingly? |
|
Thanks |
I think the most noteworthy change here is probably the addition of
preferred_scale, which I think makes some sense to integrate considering fractional scale is already supported and implementing preferred scale on top of that should be pretty simple for compositors.