Bumped to 2.0.0 due to the incompatible changes.

The items below are largely implemented. Test suite up to ~75% coverage and passing on py2.6-3.4

Some incompatible changes need to be introduced:

• replacing baker.py with a custom solution

  • This will add support for command aliases and be a little more amenable to dbsake's use case; I am already hacking baker.py too much to support needed features.

• replacing sarge.py
  dbsake isn't really using the sarge features so scaling back to some simpler subprocess wrappers makes sense and removes an uncommon dependency

• remove dbsake.thirdparty
  only tempita will remain. This can be included easily in the executable zipfile distribution, but for rpm/deb this can be pulled in via OS dependencies, as needed.

• rename mysql-sandbox -> sandbox
  This is to avoid confusion with the "real" mysql-sandbox project.

  • add 'sb' alias for sandbox for convenience

• Cleanup the naming conventions keeping old names as an alias for compatibility

  • frm-to-schema -> frmdump
  • filename-to-tablename / tablename-to-filename -> {encode,decode}-name

• Update Documentation links to point to other projects to make dbsake a better citizen

  • mysql-utilities for alternative frm tools that preceded dbsake
  • point to Guissepe's mysql-sandbox

• integrate a test suite

  • This is a big missing feature and pretty easy to provide for most commands, particularly now that we have an easy way to spin up mysql sandboxes internally; dbsake really needs a proper test suite

• integrate travis-ci integration

• Other documentation cleanups

  • Include changelog in online documentation to more easily see dbsake's history from a user perspective
  • Include other standard documentation niceties from cookiecutter's template

• Python3 support

  • dbsake is pretty close to supporting python3. There are a handful of bytestring <-> unicode headaches in frm and sandbox that need addressed.