split kdepimlibs

John Layt jlayt at kde.org
Wed Aug 27 18:59:24 UTC 2014

My general 2c: I'm with Kevin that we should do functional and api
reviews, move code around, and generally refactor stuff *before* we
split anything. It's just plain easier that way. I don't think we're
anywhere near close to knowing what to do with everything to be
splitting things yet.  Will we also end up with deprecated code in a
kdepimlibs4-support, for example?

We started a page at
https://community.kde.org/Frameworks/Epics/kdepimlibs to document this
sort of stuff, it would be good to bring it up-to-date and work
through it progressively.

We also have Akademy and the sprint scheduled for November (?) at
which we could sit down and methodically work through the list of
everything and figure out what to do.


More information about the Kde-frameworks-devel mailing list