KTp developers please read this thread: http://www.mail-archive.com/[email protected]/msg06053.html
Summary: - there is a big incompatible change coming to the Telepathy spec. ~6 months - TpQt _needs_ porting and an API breaking release (TpQt 1.0?) - KTp will need a release on top of this. This doesn't affect 0.7 I expect 0.8 to have a very short release cycle, in ~2-3 months, fixing libkpeople. So this is probably 0.9 stuff. This is sort of very good news. We can remove a load of obsolete channels in TpQt \o/ and there's lots of upstream activity. However, it does put our release schedule under pressure. I'm not sure how much of the TpQt changes will mean we need to change KTp code. Using the high level interfaces should be fine, where we use the low level interfaces we may not be. I will need some help with TpQt porting. Plan is to create a branch, port the spec and see what breaks. We can then slowly fix it. It's also a good time to do Dario's farstream split. Further TpQt discussions should happen on the main Tp ML. David _______________________________________________ KDE-Telepathy mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-telepathy
