v0.7c1
Fix the search for the backup 'LATEST' in listing subroutines

Previously, the sort was on Python objects without a comparitor, so
the resultant sort order was arbitrary and then the last member of
this arbitrary sorting would be selected as the "latest".

Instead, use the BackupInfo.last_modified field to do the sort.

This regression was introduced by
e90973ae83b56197851caa1c5247fab255b25f40, which converted BackupInfo
from a tuple (which was in an order as to sort lexically, which given
Postgres naming conventions is roughly by date) to a more general
Python object.
Add Dan Milstein as a contributor
Fix comment style

The first line ought have content, not just a newline.
Zero-pad the partition number so lexical and numerical sorting match
v0.7c2
v0.7.0
Fix indentation
Disable yet another, new visual indent complaint from pep8

I would honor the continuation line complaints, but given that Python
mode in emacs is not cooperative in the slightest I'm considering it a
non-starter.
Re-spell set inclusion a more idiomatic way

Found by pyflakes.
Demarcate beginning of v0.8 development
Edit PyPI metadata title to be more accurate

No longer is this an S3 only tool.  The title has been made the same
as the mailing list's title.
Use a more idiomatic placement of the docstring
Fold the introduction below the title, use the standard subtitle

This makes the Table of Contents render a little nicer, and after the
couple of sentences of introductory test.
Use pip instead of default sdist

Before, OpenStack dependencies would cause obscure crashes when
setting up virtual environments because "python setup.py develop" is
not supported on account of its easy_install use.  The OpenStack
maintainers show negative interest in fixing that.
Remove some over-detailed information from the abstract
Add delete everything blackbox test

It doesn't check any invariants, but at least shows the system doesn't
crash trivially.

To make this more terse, some of the test fixtures were factored out
of the backup-push test.
Add start-up message
Print command at start-up with more attention paid to rendering

In particular, 'delete' has two levels of subcommands and knowing
which one was used is handy.
Make logging at debug levels more convenient

Previously, even though MINIMUM_LOG_LEVEL could be set, if set to a
severity like "DEBUG", log entries would be ignored anyway because of
the hard-coded setLevel calls with logging.INFO.

Instead, set the severity from MINIMUM_LOG_LEVEL so that the former
does the more obvious thing when changed to a value like DEBUG.

Reported by Greg Stark <stark@heroku.com>