https://phabricator.kde.org/T15127#269860 (build status): - limited progress, Kirigami is the main blocker now - should we ifdef out the blocking shader stuff to unblock dependent modules? -> yes
https://phabricator.kde.org/T15232 (unit test status): - good progress, only 9 regressions compared to KF5 remaining - kwayland lost its unit tests due to the removal of the server part, how do we solve that? - kwayland will be phased out in favor of Qt Wayland client API, so that's not really a concern Baloo - is this Plasma only and can be moved to Plasma or is it needed as a Framework still? - Elisa might be using it as a Framework https://phabricator.kde.org/T12135 - probably a Plasma-only thing for now - could also be done as part of plasma-integration? - seems mainly needed as a workaround for Linux/Nvidia issues https://phabricator.kde.org/T12232#268214 - what can we do in 5 for easing the transition for this? - seems mainly used in Konqueror and very few other places - "static bool test(const QEvent *event, const char *name);" should be deprecated now https://invent.kde.org/frameworks/kcoreaddons/-/merge_requests/176 - needs review https://phabricator.kde.org/T14294 - move to meta tasks, split out actionable tasks https://invent.kde.org/frameworks/kfilemetadata/-/merge_requests/48/ - needs a decision on the Q_DECLARE_PRIVATE removal - std::unique_ptr usage is undisputed and can go in https://phabricator.kde.org/T12137 - probably mainly a Plasma-specific thing, but also used by Latte Dock and KRunner - could be moved to a Plasma library - could be copied now to enable transition now https://phabricator.kde.org/T12138 - multiple engines are discouraged and mainly historic in Plasma - still in use for different styling in configuration dialogs when using QQC1 - goal for Plasma 6 is to migrate to a single engine, not possible for Plasma 5 due to compatibilty
signature.asc
Description: This is a digitally signed message part.