Tweak config for development.
Only reconnect to IRC if not shutting down.

As things stand right now, when the irc bot loses its connection, it
just tries to reconnect.  If it can't do that, then it waits 60 seconds
and tries again.. forever.  This is good, generally.  If our bot goes
offline due to a netsplit or something, it can get itself back on
freenode without human intervention.

However, if we're trying to stop the bot.. say, with
``service fedmsg-hub restart`` or a simple control-c, then it loses its
connection and, before it can finish terminating, tries to reconnect
again.  It never actually exits and you have to hit it with ``kill -9``.

This commit makes it so that when the core hub calls ``.stop()`` on the
``FMNConsumer``, then that consumer will tell its subordinates to give
up the :ghost:.
Merge pull request #19 from fedora-infra/feature/careful-with-the-irc-reconnects

Only reconnect to IRC if not shutting down.
Avoid logging so much unnecessarily.
Use the new caching mechanism from fmn.lib.
Merge pull request #20 from fedora-infra/feature/cream

Cache rules everything around me.
Add a relative arrow date to the irc message
Merge pull request #21 from fedora-infra/feature/relative-date

Add a relative arrow date to the irc message
Link to dev instructions from the README.
Add a way to disable a backend alltogether.

Fixes fedora-infra/fmn.consumer#3.
Reorganize backend to not keep session as a state attribute.
Employ new presentation bools.

- Fixes #17
- Fixes #18
Handle colorizing IRC messages.

Fixes fedora-infra/fmn.consumer#16.
0.2.4
Merge branch 'release/0.2.4'

Conflicts:
	fmn/consumer/backends/irc.py
Merge branch 'release/0.2.4' into develop
Fix missed session in the email backend.
Intelligent pkgdb2 cache invalidation.
Merge pull request #22 from fedora-infra/feature/pkgdb2-cache-invalidation

Intelligent pkgdb2 cache invalidation.
0.2.5