split kdepimlibs

Kevin Krammer krammer at kde.org
Thu Aug 28 09:46:02 UTC 2014

On Wednesday, 2014-08-27, 19:59:24, John Layt wrote:
> 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.

I agree, it makes little sense to rush this before Akademy.

Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 173 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20140828/1ad3013e/attachment-0001.sig>

More information about the Kde-frameworks-devel mailing list