[Ftp-release] ANNOUNCE: telepathy-qt4 0.5.2

[Andre Moreira Magalhaes]

The "I'm not subscribed now, right? WRONG" release.

telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time 
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.

Tarball:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.5.2.tar.gz 

Signature:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.5.2.tar.gz.asc 

The latest reviewed code is always available from:
git://git.collabora.co.uk/git/telepathy-qt4.git
http://git.collabora.co.uk/?p=telepathy-qt4.git (gitweb)

Enhancements:
 * Added Or/NotFilter classes making it more flexible to use the Filter 
   API.
 * Channel invalidation reasons now more accurately describe what 
   happened, including a new error TP_QT4_ERROR_ORPHANED for the 
   corresponding Connection getting invalidated from whichever reason.
 * Added support for ContactList and ContactGroups interfaces improving
   performance of Connection::FeatureRoster/Groups when the CM 
   supports the new interfaces.
 * ContactManager PendingOperations finish at consistent times wrt 
   actual state changes when used with a CM sporting the new
   ContactList/ContactGroups interfaces
 * Deprecated Contact/ContactManager signals carrying a
   Channel::GroupMemberChangeDetails param for 
   publish/subscription/block state changes and added new signals that
   should be used in new code.
 * fd.o #31464 - Added Channel::requestLeave() for leaving channels more
   gracefully than closing them; StreamedMediaChannel::hangupCall now 
   uses that

Fixes:
 * Properly install TelepathyQt4/ConnectionManagerLowLevel.
 * A race condition causing proxies to be needlessly dropped from the
   factory cache and hence new proxies built for a future request, and
   eventually hitting an assert in onProxyInvalidated as a result
 * Memory leaks when using Connection::FeatureRoster/RosterGroups where
   the connection and roster channels were leaking.
 * fd.o#29728 - ContactManager::addGroup and removeGroup are
   confusing/broken.
 * fd.o#29735 - Roster API semantics are error / race condition prone.

Regards,
Andre