Package: release-notes X-Debbugs-CC: debian-accessibil...@lists.debian.org Control: tags -1 patch pending
Hi all, I thinks we should document the switch of GNOME to Wayland as the default display server in the What's New section. Proposal attached. I've added d-a11y@l.d.o in X-D-CC, please keep them in the loop, because I think it is worth mentioning a recommendation to not use Wayland for people needing a11y technology. Did I phrase it right in the proposal? Does this subject (a11y on Wayland) warrant a note in "Issues to be aware of for buster" chapter? Paul
diff --git a/en/whats-new.dbk b/en/whats-new.dbk index 4865e7ae..b6b9ffaa 100644 --- a/en/whats-new.dbk +++ b/en/whats-new.dbk @@ -661,5 +661,26 @@ Among many others, this release also includes the following software updates: </para> </section> +<section id="wayland-by-default-on-gnome"> + <!-- stretch to buster --> + <title>GNOME defaults to Wayland</title> + <para> + Following the upstream code, GNOME in buster now uses the Wayland display + server by default instead of the Xorg display server. The Wayland display + server is more recent than Xorg, and therefor is designed to prevent some + security issues present in Xorg. + </para> + <para> + The Xorg display server is still installed by default and the default + display manager still allows you to choose it as the display server for the + next session, which may be needed if you want to use some applications (see + <xref linkend="apps-in-gnome-on-wayland"/>). + </para> + <para> + People requiring accessibility features of the display server, e.g. global + keyboard shortcuts, are recommended to use Xorg instead of Wayland. + </para> +</section> + </section> </chapter>
signature.asc
Description: OpenPGP digital signature
