Add missing contributors
v0.6.4
Fix buckets in S3-Classic/US-Standard that have dots

us-standard buckets that have dots ('.'), but are otherwise subdomain
compatible and could successfully run get_location(), which would
return '' (empty string), which is not seen in the region dictionary,
causing WAL-E to crash.

The fix is to re-write a successful get_location() of '' to
'us-standard'.

A regression test has been added.

This was not exercised by previous testing because all of them
combined other strangeness of bucket-name (like upper-case) that would
cause defaulting to us-standard.  Also, those that use an IAM set up
that does not permit get_location would not see this regression.

Reported by Christophe Pettus
v0.6.5
Fix __exit__ in contexts

The return value of __exit__ is used to determine if Python should
re-raise exceptions, False meaning 're-raise'.

The dangerous looking one is the one in StreamPadFileObj, where a
.close() that might somehow yield a non-False-ish return could cause
exceptions to be swallowed.

It doesn't seem likely that'd ever be the case, but the code as
written needlessly relies on that for correct behavior and obscures
the intent.

Backpatch this change to 0.5, too.
Set default WAL upload concurrency to 8

The slowest steps of dealing with segments one at a time is program
start-up and subsequently connection-start-up.  For this reason, a
relatively large default maximum allowable concurrency is used so
WAL-E can wait for connection-startup to complete for many segments in
parallel.
Use s3-external-1 endpoint for us-standard

This is the endpoint in us-east-1, where most instances are.  This is
not being applied to the v0.6 maintenance releases to avoid changing
behavior for those who are closer to Seattle.