It’s really disappointing that the only reason for blocking Plasma 5.27.5 and Frameworks 5.104 is that there’s “too many packages”.
KDE upstream has stopped feature development for Plasma 5.x and Frameworks 5.x with the releases of Plasma 5.27.0 and Frameworks 5.100, because the focus has completely switched to developing Plasma 6.0 and Frameworks 6.0 [1] [this link also explains the Fibonacci release cycle that you asked about]. That means Plasma 5.27.x and Frameworks 5.1xx are strictly only bug fix releases, they contain absolutely no new features and no major regressions have been reported in the newer versions. Just check the changelogs for every Plasma release since 5.27.2 and every Frameworks release since 5.103 (the versions Testing is stuck on), there have been *hundreds* of bugs fixed since. Cherry-picking fixes for the most prominent crashes just isn’t practical considering especially how many bugs were fixed in Plasma 5.27.3 alone. I’d like to remind you that GNOME 43.4 was allowed to migrate recently; why does GNOME get special treatment and KDE has to stay stuck on an older, buggier version? Debian KDE users would strongly appreciate you changing your stance and allowing the best versions to be included on release. If you still are not convinced on allowing these to be unblocked, would you at least consider allowing them to migrate for the Debian 12.1 point release? Again, I’d like to remind you that these are long-term support releases, they strictly fix bugs and contain no new features. There are absolutely no downsides to allowing them to migrate so they can be in Debian 12. Thank you for your consideration and your hard work maintaining Debian. [1] https://community.kde.org/Schedules/Plasma_5 - “This is the last Plasma 5 release and will receive bugfixes only, no new features. The bugfixes are intended to continue being integrated into 5.27 until a first version of Plasma 6 can be released (and might continue longer).”
