cc.server: new config option stats-period (defaults to 30s)
added support for writing service infofiles (with detailed stats about running job)

First anonymous / default section contains general info about the process and environment.
Section "total" contains overall stat.counters.
Section "latest" contains stat.counters for last period (since previous infofile).
Next sections contain running averages for preconfigured time spans (1, 5, 15 minutes).
Lines in "avg" sections contain: counter name, counter value, avg per bucket, avg per second.
cc.handler.jobmgr: fixed "IOError: [Errno 35] Resource temporarily unavailable" issue

It seems Mac and BSD specific and transient, just one check (per job) fails (upon CC launch).
cc.server: new config option infofile-level controls detail of statistics

The following levels are available (default is 2):
0 - no infofile created
1 - basic info about the process and environment
2 - plus overall stat.counters and stat.counters for latest period
3 - plus running averages for preconfigured time spans (1, 5, 15 minutes)
cc.server: optimised .info file generation (level 3)

Optimisation gain increases with the following:
. the more timespans (running averages sections)
. the longer the timespans are
. the more precision is used (smaller buckets)
. the more counters are used by CC components
v0.8.4
cc.handler.database: fixed bug when db connection broke
cc.handler.database: improved recovery on connection failure

So far the first message to encounter connection error was always dropped.
Now it tries to reconnect in process_request() when getting cursor fails.
cc.handler.database: refactored connection handling
cc.server: amended timestamp printing in infofile
cc.server: fixed broken compat with python 2.5

note that infofile-level above 2 cannot be used with python older than 2.6
cc.server: added zmq versions to .info file
postponed log string formatting (all code checked)
v0.8.5
added filter handler feature

Filter class implements a filter that can be used to selectively drop messages (and forwards the rest to another handler for real processing).
fixed issue when using too old skytools (pre-3.1)
cc.handler.proxy: added explicit reconnection when link to remote cc goes down

This has disadvantages 1) that all queued messages are dropped and especially 2) that the connection ID gets changed and therefore no replies to messages from past can make it back!
cc.handler.proxy: removed previous commit as reconnection on zmq level is preferable

Our internal libzmq has necessary patch (libzmq/patches/getaddrinfo.diff) since version 2.1.11-3 and that is the proper way to overcome connection issues.
.gitignore updated
cc.daemon.infosender: lowered log level of maintenance message

We do not log on info level about sending, so neither we should do about forgetting.