https://bugs.kde.org/show_bug.cgi?id=521682
--- Comment #68 from Anthony Lee <[email protected]> --- (In reply to Anthony Lee from comment #55) Feed back to the bugzilla team. I expect this to be 'spammed' as it doesn't advance the issue but I have nowhere else to leave this. >... > ## I concur that the priority of this issue should be bumped. ## > The work arounds range from obscure CLI, to the uninstallation of entire > software platforms (snap). Where the former can not be assumed to be > available to the kinds of users who place great value on a GUI, and the > latter is a high cost remedy. > ... I am still getting accustomed to managing some considerations that with Microsoft Windows are looked after for you. ** I am now decided that my above is mostly or even near entirely wrong.** I think it would have been valid, and valuable, to have (diplomatically) highlighted that this issue needs to be progressed in this way, and is often sometimes necessary, to enable development to keep moving forward. Else everything gets bogged down by needing to treat EVERY 'stable' releases as LTS, which is two different things, with different levels of burden and expectation. I think it would have been valid and fair to respond to my post above by highlighting https://community.kde.org/Schedules/Plasma_6#Long-term_support_releases . That said I would expect the next KDE plasma release designated 'stable' to have a version of Discover that does not suffer this issue. In fact I would regard it a 'blocker' to the 'Release type: stable' on the entire KDE plasma project, until met. You can validly release a 'bug' fix that does 'not' yet fix 'this' bug, but one should not surely approve such as broad 'stable' (?) . -- You are receiving this mail because: You are watching all bug changes.
