2.2.0

• sandbox now handles MySQL 5.7 instance bootstrapping (PR #128)
• sieve will now use pigz if available when --format=directory is specified (issue #130)
• python2.6 is no longer tested

2.1.2

2.1.2 (2017-02-15)

This release fixes a regression in the dbsake sandbox command introduced in v2.1.1.

Bugs fixed

• dbsake 2.1.1 sandbox command was broken due to incorrectly quoting the –ledir argument when generating sandbox.sh (issue #120)

2.1.1

2.1.1 (2017-02-07)

This is bugfix release with only one minor feature to support recursively applying frmdump to a directory.

New features

• Add frmdump --recursive option to dump all *.frm files found in the target directory
  (issue #60)

Bugs fixed:

• frmdump now handles tokudb row_format from .frm files created by Percona Server
  (issue #80)
• sandbox generated sandbox.sh script would previously wait for the
  mysqld socket to appear as part of the "start" action, which was
  problematic for Galera based binaries. sandbox.sh start now waits
  for the pid-file to appear via the "sandbox.sh status" action.
  (issue #88)
• unpack command had a bug that failed on uncompressed input; similarly
  affected the sandbox command when unpacking uncompressed archives via
  the --data-source / -s option (issue #90)
• upgrade-mycnf now handles paths with spaces (issue #94)
• python-setuptools is now required for install (issue #95)
• Remove unicode_literals usage in cli to avoid noisy warnings from click
  (Issue #96)
• contrib/ is now included in the source package (PR#98 from azlev)
• frmdump failed to decode tables specified with utf8mb4, binary or other
  less common encodings. (issues #97, #102)
• starting a sandbox failed on recent versions of MySQL due to the mysqld_safe
  ledir option now being prohibited in config files. (issue #103)