3 ms·
This is more thought out than it might appear. In various Fedora releases you can already test GNOME under Wayland. Due to Wayland, certain functionality is not
by bkor 12y ago
This is more thought out than it might appear. In various Fedora releases you can already test GNOME under Wayland. Due to Wayland, certain functionality is not available. The one case which is not resolved yet is the "color picker" from anywhere on the screen. This as security wise you don't want applications to determine the screen content of other applications.
So the switch is actually gradual:
1. Now: Optional GNOME Wayland session (with slightly less functionality)
2. Wayland login session in development distribution
3. QA testing (Fedora has a big QA team)
4. Go/no go decision
5. GNOME Wayland login session in stable distribution
6. Repeat 2-5 for Wayland as default session (for next distribution version)
The login session doesn't use the functionality that might be different between releases. That is why to proceed with testing Wayland, login session is a better test than knowingly reducing functionality.
I'm aiming to also have the Mageia development version switch to using Wayland for GDM. A lot of people use that and we (Mageia) often notice bugs quite quickly.
- reidrac 12y agoThe problem is that the process is good for the software but it won't be good for the users in the early iterations. I use Fedora at home and I love it, but sometimes it is a little bit too experimental and in this case I'm afraid it might not be usable (Fedora has shipped broken things in the past that I would qualify as "release blockers", but the release team have a different opinion). Things settle in the sweet spot (eventually), but with every upgrade is like "what will be broken this time", and that's not a pleasant end-user experience.
- mst 12y agoIf 3+4 are done sensibly, it's possibly not that terrible. But I think in that case there should be a boot option of some sort to get a non-wayland login session, just in case.