Plasma 5.18 was a pretty buggy release, and I'd like to start a discussion about how we think it happened and what we can do better next time. Here are some of the top bugs that our users are reporting:

- https://bugs.kde.org/show_bug.cgi?id=417424 [Can't enter edit mode if widgets were previously locked] - https://bugs.kde.org/show_bug.cgi?id=416358 [Can't apply changes in Fonts KCM] - https://bugs.kde.org/show_bug.cgi?id=417351 [FormLayout positioning and width regressions] - https://bugs.kde.org/show_bug.cgi?id=415155 [Broken closing from Present Windows] - https://bugs.kde.org/show_bug.cgi?id=412331 [GTK2 apps suffer from visual glitches particularly when using dark color schemes]
- https://bugs.kde.org/show_bug.cgi?id=417454 [Emoji panel is really slow]
- Emoji panel doesn't work properly if you don't have the right fonts and ibus packages installed
- https://bugs.kde.org/show_bug.cgi?id=417127 [Can't turn off Baloo]
- https://bugs.kde.org/show_bug.cgi?id=417511 [Un-maximized dark panels have white corners] - https://bugs.kde.org/show_bug.cgi?id=416331 [Unnecessary horizontal scrollbar in plasma-pa KCM] - https://bugs.kde.org/show_bug.cgi?id=417437 [Scrollview overlap in Baloo KCM]

Looking through the list, I can't see any one common thread.

Some of these bugs were caused by un-reviewed commits, but others were caused by commits that were reviewed by multiple people. Some bugs were simply not found during the beta period, while others were discovered early but not prioritized. Some changes were rushed in at the last minute, but others went in months ago. Some bugs are in Plasma, but others are in Frameworks products, most notably Kirigami, qqc2-desktop-style, and plasma-framework.

Does anyone have any thoughts on how we can do better?

(also, focusing on issues in the list above would be much appreciated :) )

Nate

Reply via email to