There's a few "buts", though.
Firstly, it should be noted that support for QWidget-Based applications (and other desktop-based usecases) may be far from ideal, and quality may not be great. This is a consequence of most development on QtWayland having been driven from mobile/embedded viewpoints to date, and is not, in general, an inherent limitation on the windowing system. It's also something of a reflection on Wayland itself, which is only now starting to mature for desktop use (through xdg-shell etc etc.)
tl;dr: Think of this as a technical preview, keep your expectations realistic, and if you want to use it, expect to roll up your sleeves a bit and get dirty from time to time.
Secondly, the QtCompositor API in the QtWayland module (allowing you to write your own Wayland compositor) will not be seeing a release at this time. The API is not frozen, and has not seen the usual polish/quality that you might expect from Qt APIs. As this API is only of use to a limited number of people (those looking to implement an embedded/mobile device, typically, or write their own DE) this should not impact too many people.
tl;dr: If you want to write a compositor, you get to keep both pieces if it breaks. If you want to use applications under an existing Wayland compositor, you're fine.
Future work to QtWayland is largely an open story, but some obvious candidates come to mind:
- Continued work on xdg-shell support
Plugin based window decorations (to enable environment-specific look and feel)this has now landed in the 5.4 branch :)
- Integration with the rest of Qt's autotests (I spent a while getting tests fixed or at least runnable under window-compositor, but it would be nice to automate this)
- "Official" subsurface protocol support
I'd also like to take a moment to thank everyone for their contributions to QtWayland. In particular, I'd like to say thanks to the following, in no particular order (and I'm extremely sorry if I've missed someone, please let me know and I'll happily add you to the list):
- Kristian Høgsberg & Jesse Barnes, for their initial work on the port, sponsored by Intel,
- Jørgen Lind, Samuel Rødal, Andy Nichols, Laszlo Agocs, and Paul Olav Tvete for continuing work on it excellently and admirably,
- Nokia for sponsoring a good deal of the development up until their abrupt departure from the Qt world,
- Digia for continuing to help out after Nokia left,
- Andrew Knight, for ably shepherding problems encountered by Jolla for quite a long time,
- Jolla for sponsoring a large chunk of work on QtWayland (past and present),
- Gunnar Sletta for rewriting integration with rendering (especially QtQuick), removing a large number of bugs & improving performance,
- Giulio Camuffo for numerous fixes, improvements and interaction with the wider Wayland community.