https://bugs.kde.org/show_bug.cgi?id=434202
--- Comment #5 from andreas.sturmlech...@gmail.com --- (In reply to Nate Graham from comment #1) > Or we could revert the change and only re-add it to the version of > Frameworks that's aligned with Plasma 5.22's release date (5.83). This would > technically break the dependency though. Perhaps we could change Plasma's > Frameworks dependency version to 5.23. One thing to keep in mind: Not every distribution is going to drop Plasma 5.21 just because 5.22 is out. In Gentoo e.g., we have a habit of keeping the latest Plasma 5.xx.5 release in stable branch until the next Plasma .5 is ready. During that time, new Frameworks versions may be stabilised once or twice. Now we have stable: Plasma 5.20.5 / Frameworks 5.77 / Release Service 20.08.3. Frameworks 5.80 would normally be scheduled for stabilisation 30 days from now, then likely either 5.82/83, 5.85/86... so for a brief time maybe Plasma 5.21.5 will be paired with even Frameworks 5.85 in stable for our users, until 5.22.5 is ready. And during all that time stable users may decide to unmask any unstable Frameworks version in between, because that is something they can easily do (even if they lose stable support ofc). Long story short, this means we will likely need to backport the adaptive panel opacity support to Plasma 5.21.5 unless we want to break with our usual schedule or just risk some users may end up with this bug by their own choice (of mixing a stable Plasma with unstable Frameworks). -- You are receiving this mail because: You are watching all bug changes.
