summaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorDanielle Madeley <danielle.madeley@collabora.co.uk>2010-02-24 15:56:25 +1100
committerDanielle Madeley <danielle.madeley@collabora.co.uk>2010-02-24 15:56:25 +1100
commit6751bafc218447314c4fd3e97f684ac8827745cd (patch)
treecbb80cad68001dc9c09ba96c3146d10efbe1acdd /NEWS
parent20719b71095d2e77d953ee53f10ce2c0cc0717f6 (diff)
downloadtelepathy-logger-6751bafc218447314c4fd3e97f684ac8827745cd.tar.gz
Release telepathy-logger 0.1.0telepathy-logger-0.1.0
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS29
1 files changed, 29 insertions, 0 deletions
diff --git a/NEWS b/NEWS
index e69de29..6268cc7 100644
--- a/NEWS
+++ b/NEWS
@@ -0,0 +1,29 @@
+telepathy-logger 0.1.0 (2010-02-24)
+===================================
+
+The ``Calamity Ensues'' release
+
+This is the first preview release of the telepathy-logger. You should be aware
+that this is a piece of software that is still very much in development,
+everything is subject to change.
+
+The idea behind tp-logger is that it will become a generic logging daemon usable
+anywhere in Telepathy, with any Telepathy client.
+
+Things that mostly work:
+
+ - logging of text channels into an Empathy style log format using a Telepathy
+ Observer client
+ - Telepathy-style D-Bus API to retrieve logs (will be extended soon with more
+ functionality)
+ - libtelepathy-logger API to allow clients to access logs en-masse
+ - GConf preferences to control what accounts to log
+
+Things that don't work:
+
+ - existing channels won't be logged when the logger starts
+ - preference changes aren't noticed asynchronously
+
+Note that tp-logger won't import your existing logs from Empathy, for the time
+being, if you're running it, you are going to end up with two sets of logs,
+one from Empathy and one from tp-logger.