Hi Christian,
I think that the stuff you're looking for (reducing version churn) can also
be provided by having stable branches for selected parts of KF5.
IMHO this can be quite an elegant solution given the usual cat-herding
problem of FLOSS where people just do what they want to do. Those who value
the benefits of having bugfix-only releases and those willing to put their
time into this could well branch from a random KF5 release and keep
backporting bugfixes. I can give you CI coverage pretty easily for this.
Would this solve this problem for you, and would you volunteer to become a
maintainer for this? Has this been discussed before, or is there some
reason against doing this?
Cheers,
Jan
--
Trojitá, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/
_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
