Telepathy-1.0 release

[Kaffeine]

We need to decide if it will be better to add features and polish them (in spec 0.28 and TelepathyQt-0.10) before 1.0 release, or easy the development by dropping all the deprecated stuff and moving to 1.0.

Pros:

• it would be easier to merge 1.0 branch(es) now, than later.

Cons:

• We can not just bring TelepathyQt with 1.0 specification: we need telepathy-glib counterparts and we will have to support it. Namely, we need mission-control at the very least. Personally (@Kaffeine) I'm not familiar with glib and would prefer to rewrite everything in Qt, rather than develop glib-based code. About the other components: we also need telepathy-logger and I would like to rewrite it too to support multimedia content of messages. Maybe we can refactor Message class to let a client to operate with messages in a bit more abstract manner (logged/sent/received) with a possibility to subclass? This worth a yet another discussion thread (issue).

Links: https://github.com/davidedmundson/telepathy-qt/tree/next (190 commits ahead)

[Thaodan]

Have you looked in to that again? From what I've looked into the glib was based parts of telepathy bringing them up to date (dropping dbus-glib and such) requires rewriting some of the parts against GDBus which is already done in the next branch.