@lukesneeringer @landrito FYI, the docs update produces a ton of changes. It might be easier to review commit-by-commit so you can just see the changelog/version update.

The main README needs to be updated to denote the drop of 2.6.

The main README needs to be updated to denote the drop of 2.6.

Done.

While we are busy dropping 2.6, would would be the effort level involved in adding 3.5 and 3.6 to Tox and Travis? It seems to be the effort level of Tox should be pretty low.

It looks like Travis does not have gold support for Python 3.6 yet. I assert that adding Python 3.5 would be worthwhile.

@lukesneeringer it's a good idea, but let's not tie it to this release? (I can likely configure it next week)

I'm going to go ahead and cut this release, adding testing for 3.5 shouldn't necessitate a new release (just some updated docs).