On the Wayland mailing list, Kristian laid out his Wayland 1.2 vision. Key points from his e-mail include:
- New major releases on a quarterly basis (every 4 months) while a six month cadence was talked about long ago in the past. Kristian explains, "The motivation for this is that we have a lot of new features and new protocol in the works and a time-based release schedule is a good way to flush out those features. Instead of dragging out a release while waiting for a feature to become ready, we release on a regular schedule to make sure the features that did land get released on time."
- With a quarterly release, Wayland/Weston 1.2 is expected for release around the end of June.
- While mentioned previously, with future Wayland releases they will never break the protocol or client-side API. For now the wayland-server API isn't for sure stable but that's less of an impact.
- Early features being planned for Wayland 1.2 is the sub-surface work and input method work.
- Other features being talked about for Wayland 1.2 is trimming down the libwayland-server to just IPC, weston-launcher with potential handling there for VT switching, a pop-up placement protocol, pointer locking, clearing up some gaps in the Wayland core protocol, locking issues, color management work, a back-end to support DisplayLink USB devices, mouse motion binding, remote display, and XWayland.
- On the XWayland front, there's work on making it support DRI2 swap buffers, MWM resize hints, double-buffer decoration drawing, drag and drop between Wayland and X applications, support for window icons, frame buttons, and other features.