This starts to become a dangerous path (Was: New Feature for kdelibs)
bcooksley at kde.org
Tue Nov 15 21:36:54 GMT 2011
Perhaps as a solution to this, kdelibs master could have features
added to it, but only by a couple of gatekeepers who would
simultaneously ensure that the feature also lands in frameworks at the
same time? Obviously frameworks is going to be the future, however it
seems there are some people who will not take "kdelibs 4.x is closed
for new features" as a valid answer.
As I see it, certain distributors seem dead set on including certain
features in kdelibs 4.8 regardless of the wishes of KDE developers,
and these forks will cause both binary incompatibility between
distributions - and make supporting different distributions harder as
those who have patched theirs to include these features will have a
differently behaving KDE compared to everyone else.
More information about the kde-core-devel