Dataflake.docbuilder

-----------------
- Be more resilient when simple ReST text compilation or
Sphinx building fails. Now the whole documentation build
process won't just fail at that point.
- provide more meaningful log messages when running with
the ``-v`` option.

-----------------
- Now you can use ``Git`` alongside ``Mercurial`` and
``Subversion`` to use as version control system.

-----------------
- Taking more control of logging by defining our own logger and
suppressing standard Sphinx log output. The new script flag
``-v`` or ``--verbose`` enables the user to determine what to
show. Without it, only serious warnings are shown. With ``-v``
specified once you will see script progress output and notes
about Sphinx build warnings. With ``-vv`` all Sphinx output
is shown as well.

----------------
- Now using pkg_resources.parse_version to parse the tag names and
produce correct release ordering for each package
- Instead of using a flag to set the revision control system
across all packages you now specify the revision control system
per package with a simple prefix::

[hg]http://myserver/hg/mypackage
[svn]https://myservr/svnmypackage

For backwards compatibility, all URLs without prefix are assumed
to point to a Subversion repository.

----------------
- Feature: You can now use either ``Subversion`` or ``Mercurial``
to check out documented packages.

----------------
- Feature: If no standard package documentation can be found,
the setuptools ``long_description`` settings is used as a
last fallback to at least generate a single page for a package.

- Feature: To style the ``long_description`` fallback ReST
documentation, a new parameter ``fallback-css`` can be used to
provide a path to a CSS file.