2 kirigami fixes for a point release

David Faure faure at kde.org
Sun Feb 16 21:34:51 GMT 2020

On dimanche 16 février 2020 22:17:17 CET Albert Astals Cid wrote:
> This is their fault, they as a distribution have decided to support a random
> KDE Frameworks version for longer than we do support it, so they are the
> ones that should be the job of supporting it.
> It's like you are trying to say we should be doing the distributions jobs,
> what we should be doing is doing our job which is making the best software
> we can, not spending time accomodating decisions that somebody else took
> for us, and since distributions often only bring us pain in the shape of
> not updating versions, etc. IMHO what we should be doing is moving away
> from distributions model and more into the snap/flatpak model in which we
> control what we give our users.
> Sadly flatpak doesn't work for non applications and snap is
> Ubuntu-only-not-really-but-yes-really so for Plasma this doesn't really
> solver the problem so maybe we should just finally tell our users to start
> using the good distributions if they care about their user experience. By
> good meaning those with a rolling KDE software suite or those that actually
> do backport fixes to the version they have randomly decided to lock onto.

At the same time, we can only successfully convince distributions to upgrade 
to the monthly KF5 releases if they are stable and don't come with 
regressions. I believe this is true for most of the frameworks, but I'm not so 
sure about kirigami/qqc2-desktop-style, based on what I hear (not just the 
recent issue).

Before blaming distros, I believe we have our own backyard to take care of,
with for sure more systematic use of code reviews and possibly more automated 
testing, for those frameworks (for the latter I guess that QtQuick doesn't 
make it easy, but that's part of the problem...).

David Faure, faure at kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5

More information about the release-team mailing list