<div dir="auto"><div>Hi,</div><div dir="auto"><br></div><div dir="auto">> with Plasma 6.7 being the last version with X11 support</div><div dir="auto">> 6.7.7 2027-02-02</div><div dir="auto"><br></div><div dir="auto"><div dir="auto">I think dropping support for an ACTUALLY WORKING, VERY STABLE, and BATTLE-TESTED environment like Xorg/XLibre in favor of a solution where even the underlying protocol design is still effectively in an alpha state, valid use cases are broken, and basic core features are still missing and still actively debated among developers, is pretty insane. Literally.</div><div dir="auto"><br></div><div dir="auto">I would like to hear a MERITORIOUS reply to these concerns:</div><div dir="auto"><br></div><div dir="auto"><div dir="auto"><a href="https://www.reddit.com/r/linux/comments/1pxectw/wayland_is_flawed_at_its_core_and_the_community/" rel="noreferrer noreferrer noreferrer" target="_blank">https://www.reddit.com/r/linux/comments/1pxectw/wayland_is_flawed_at_its_core_and_the_community/</a></div><div dir="auto"><br></div><div dir="auto"><a href="https://www.semicomplete.com/blog/xdotool-and-exploring-wayland-fragmentation/" rel="noreferrer noreferrer noreferrer" target="_blank">https://www.semicomplete.com/blog/xdotool-and-exploring-wayland-fragmentation/</a></div><div dir="auto"><br></div><div dir="auto"><a href="https://vas.neocities.org/wayland_shitware" rel="noreferrer noreferrer noreferrer" target="_blank">https://vas.neocities.org/wayland_shitware</a></div></div><div dir="auto"><br></div><div dir="auto"><a href="https://news.ycombinator.com/item?id=44301194" target="_blank" rel="noreferrer">https://news.ycombinator.com/item?id=44301194</a></div><div dir="auto"><br></div><div dir="auto">Namely:</div><div dir="auto"><div dir="auto">- no mouse-grabbing protocol; pointer-warp protocol is still broken (required by virtually every game)</div><div dir="auto">- screen sharing is still broken</div><div dir="auto">- color management is still broken</div><div dir="auto">- automation tools are broken (xdotool)</div><div dir="auto">- global hotkeys broken</div><div dir="auto">- accessibility features can’t be properly implemented</div><div dir="auto">- no sane capabilities system</div><div dir="auto">- no standard way to communicate with the window manager (like EWMH)</div><div dir="auto">- fragmentation hell: no DE is required to implement any protocol, no API can be considered reliable</div><div dir="auto">- every new feature requires a new protocol and multiple, DE-specific implementations, which will take years to become even remotely useful</div></div><div dir="auto">...and much more.</div><div dir="auto">READ the actual articles; it's 10 minutes of work spent on actually listening to the community.</div><div dir="auto"><br></div><div dir="auto">Wayland is unusable for the majority of Linux users, based on the use cases described and the numerous comments above.</div><div dir="auto">Are you willing to take our voices into consideration, or will you continue to ignore us?</div><div dir="auto"><br></div><div dir="auto">Power-users, in particular, will be hurt by you ignoring our needs. KDE has always been the desktop environment that supported us.</div><div dir="auto">Do you remember "Simple by Default, Powerful when Needed"? With Wayland, it feels more like "Broken by Default, Powerful Never".</div><div dir="auto"><br></div><div dir="auto">I am fully in favor of replacing old X11 with something modern and better, but Wayland is either not that solution, or at the very least, it is not ready yet.</div><div dir="auto"><br></div><div dir="auto">That said, there should obviously be NO END DATE SCHEDULED FOR X11 SUPPORT.</div><div dir="auto">Maybe we can have this discussion again in 5 years or so, when Wayland is (hopefully) ready and actually usable.</div><div dir="auto"><br></div><div dir="auto">Once again: stop ignoring valid concerns and provide meritorious responses instead of avoiding the topic. Otherwise, this will end badly for the entire Linux community.</div></div><div dir="auto"><br></div><div dir="auto">Best Regards,</div><div dir="auto">Piotr H. Dabrowski</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr"><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi everyone,<br>
<br>
with Plasma 6.7 being the last version with X11 support [1] and the idea <br>
that "6.7 would get support until 6.9 branches" (David Edmundson, [2] ), <br>
I re-visited my proposed schedule and also created a draft schedule for <br>
6.8 and 6.9.<br>
<br>
This will be a bit of a longer e-mail, sorry, I'll try to keep it as <br>
short as possible.<br>
<br>
+++++ [Plasma 6.7.] +++++<br>
6.6.80 2026-04-30<br>
6.6.90 2026-05-14 [Note1]<br>
6.6.91 2026-05-28<br>
TAR 2026-06-11<br>
6.7.0 2026-06-16<br>
6.7.1 2026-06-23<br>
6.7.2 2026-06-30<br>
6.7.3 2026-07-14<br>
6.7.4 2026-08-04<br>
6.7.5 2026-09-08<br>
6.7.6 2026-11-10 [Note2]<br>
6.7.7 2027-02-02 [Note3, Note4]<br>
<br>
Versions:<br>
Qt: Stay on 6.10 (as agreed upon in the last e-mail thread and on Matrix <br>
discussion)<br>
KDE FW: 6.26<br>
<br>
Notes:<br>
[General / CI]<br>
I'm not sure how the CI situation will work out for one extra release of <br>
Plasma 6.7. There were some concerns raised by Ben Cooksley [4], though <br>
that was with my then drafted 6.7.8 bugfix release, which has been <br>
dropped. The current proposal would end the 6.7 series with 6.7.7 .<br>
<br>
[Note1] This is the Thursday following the corresponding Frameworks <br>
release ("expected May 8th"). It's also 2 days after 6.6.5, but that <br>
should be OK?<br>
<br>
[Note2] Delayed by one week with regard to the Fibonacci sequence to <br>
avoid conflict with 6.8.2<br>
<br>
[Note3] As can be seen further down this e-mail, this is about 2 weeks <br>
after tagging of Plasma 6.9 (scheduled for 2027-01-21)<br>
<br>
[Note4] Even though this is one extra release compared to other Plasma <br>
versions, consesus so far seems to be to not call this an "LTS" release <br>
publicly.<br>
+++++ [/Plasma 6.7.] +++++<br>
<br>
<br>
<br>
+++++ [Plasma 6.8.] +++++<br>
6.7.80 2026-09-03<br>
6.7.90 2026-09-17 [Note5]<br>
6.7.91 2026-10-01<br>
TAR 2026-10-15<br>
6.8.0 2026-10-20<br>
6.8.1 2026-10-27<br>
6.8.2 2026-11-03<br>
6.8.3 2026-11-17<br>
6.8.4 2026-12-08<br>
6.8.5 2027-01-12<br>
6.8.6 2027-03-16 [Note6]<br>
<br>
Versions:<br>
Qt: TBD (Staying with Qt 6.10 or Qt 6.11 would be possible, released <br>
"March 2026"[3])<br>
KDE FW: 6.30<br>
<br>
Notes:<br>
[Note5] Thursday after corresponding Frameworks release ("expected Sept. <br>
11th")<br>
[Note6] Delayed by one week with regard to the Fibonacci sequence to <br>
avoid conflict with 6.9.1<br>
<br>
<br>
+++++ [/Plasma 6.8.] +++++<br>
<br>
<br>
+++++ [Plasma 6.9.] +++++<br>
6.8.80 2027-01-07 [Note7]<br>
6.8.90 2027-01-21<br>
6.8.91 2027-02-04<br>
TAR 2027-02-18<br>
6.9.0 2027-02-23<br>
6.9.1 2027-03-02<br>
6.9.2 2027-03-09<br>
6.9.3 2027-03-23<br>
6.9.4 2027-04-13<br>
6.9.5 2027-05-18<br>
6.9.6 2027-07-13<br>
<br>
<br>
Versions:<br>
Qt: TBD (Qt 6.11 and Qt 6.12 would probably both be available)<br>
KDE FW: 6.34(?) - Not scheduled yet.<br>
<br>
Notes:<br>
[Note7] I've delayed this by about 2 weeks from the "usual" schedule to <br>
avoid a soft freeze right around Christmas. All other dates are delayed, <br>
therefor, too (when comparing with earlier versions of Plasma).<br>
<br>
This might be a good time to re-think the 2-or-3-releases a year situation.<br>
<br>
+++++ [/Plasma 6.9.] +++++<br>
<br>
As always: this is just a quick proposal by me, trying to take into <br>
account previous discussions and previous schedules. I'm happy to change it.<br>
<br>
Best regards<br>
<br>
Martin<br>
<br>
[1] <a href="https://blogs.kde.org/2025/11/26/going-all-in-on-a-wayland-future/" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://blogs.kde.org/2025/11/26/going-all-in-on-a-wayland-future/</a><br>
[2] <a href="https://mail.kde.org/pipermail/plasma-devel/2025-December/123833.html" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://mail.kde.org/pipermail/plasma-devel/2025-December/123833.html</a><br>
[3] <a href="https://wiki.qt.io/QtReleasing" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://wiki.qt.io/QtReleasing</a><br>
[4] <a href="https://mail.kde.org/pipermail/plasma-devel/2025-December/123826.html" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://mail.kde.org/pipermail/plasma-devel/2025-December/123826.html</a><br>
</blockquote></div></div></div>