-   BREAKING:  While this change will correct the weird encoding
    behavior, this also changes the way `xxx_url` macros work.
-   Do not encode the url bases (`base_url`, `media_url`). Only
    the path component needs to be encoded.

-   Ensure that subfolders for `layout_root`, `content_root`,
        `media_root` and `deploy_root` works reliably
        on windows. Use `fully_expanded_path` for all path components.

- Also, fixed `raise_exceptions` commandline parameter handling.

*   Better exception handling. (Issue #204)
    -   Hyde now propagates exceptions
    -   Hyde does not raise exceptions by default. `-x` flag is required
        for raising exceptions on error.
    -   Traceback is available in the `verbose` mode
*   Upgraded to commando 0.3.4
*   Upgraded to Jinja 2.7

- Add LICENSE, AUTHORS.rst, CHANGELOG.rst and README.rst to MANIFEST.in.
- Add "Hyde contributors" to copyright.

- Fix expected files in uglify tests
- Use proper configuration for copyright retention

`

*   Bugfix: Use `clearfix` class in `listing.j2`. (Issue #156)
*   Bugfix: Use `relative_path` instead of url in `macros.j2`.
    (Issue #180)

Remove dependencies on forked version. This will cause dependencies
to be unaccounted.

CleverCSS [1] is a Python-based preprocessor for CSS. It is not quite
as powerful as LessCSS and doesn't seem to get much updates, but the
advantage is that it only requires Python (which you'd already have for
Hyde) and you don't need node.js or some client-side JS.

[1] http://sandbox.pocoo.org/clevercss/

Basically just about the same as the Git dates plugin, but using
hg instead of git.

Merge the huge plugin structural refactoring and retrofit changes
from the past.

Compile the regexs on plugin load instead of every time a resource
is processed.

* blockdown
 * markings
 * syntext
 * textlinks

Check resource.source_file.kind in _should_parse_resource instead of
every time the latter is called.

* less   -> css
* git    -> vcs
* uglify -> js

thumbnails and tagger pages

This plugin may seem redundant with jpegoptim one. jpegtran allows one
to produce progressive JPEG while jpegoptim does not. On the other
hand, jpegtran only does losless compression while jpegoptim allows
one to set a maximum quality setting.

Signed-off-by: Henning@Mac <Henning@monkey-works.de>