Collective-recipe-backup

=================

- Call repozo with ``--quick`` when making an incremental backup.
This is a lot faster. Theoretically it lead to inconsistency if
someone is messing in your backup directory. You can return to the
previous behavior by specifying ``quick = false`` in the backup
recipe part in your buildout config.
[maurits]

- check and create folders now happens after pre_commands is run
[djay]

=================

- Add ``rsync_options`` option. These are added to the default
``rsync -a`` command. Default is no extra parameters. This can be
useful for example when you want to restore a backup from a
symlinked directory, in which case ``rsync_options = --no-l -k``
does the trick.
[fiterbek]

=================

- Add ``alternative_restore_sources`` option. This creates a
``bin/altrestore`` script that restores from an alternative backup
location, specified by that option. You can use this to restore a
backup of the production data to your testing or staging server.
[maurits]

- When checking if the backup script will be able to create a path,
remove all created directories. Until now, only the final directory
was removed, and not any created parent directories.
[maurits]

- Testing: split the single big doctest file into multiple files, to
make the automated tests less dependent on one another, making it
easier to change them and add new ones.
[maurits]

- No longer test with Python 2.4, because Travis does not support it
out of the box. Should still work fine.
[maurits]

=================

- Do not create blob backup dirs when not backing up blobs.
Do not create filestorage backup dirs when not backing up filestorage.
Fixes https://github.com/collective/collective.recipe.backup/issues/17
[maurits]

=================

- Restore compatibility with Python 2.4 (Plone 3).
[maurits]

=================

- Archive blob backups with buildout option ``gzip_blob``.
[matejc]