DB#data_set_size makes more sense in db/state.rb than db/import_export.rb
Do not fatal on Host#hostname if host is offline/unavailable, since this breaks masterless promotion
Display NULL slave lag more intelligently in Pool#summary(true)
command suite: Auto-detect shard to target with shard_split_child_writes and shard_split_cleanup tasks
Make most command suite methods describe the node being targeted
Remove commands show_slave, show_master, and node_info, replace with new summary command.
Add new command suite tasks for displaying global topology state: pools and pools_compact
No need to describe demoted node, since we call Pool#summary shortly later
Update documentation regarding new informational commands replacing the old ones
Fix bugs in SimpleTracker example plugin:
* jetpants destroy_slave now tracks the change properly
* jetpants promotion with an offline master -- now correctly fills in the slave
  list automatically
* DB#probe now handles offline/unavailable machines correctly
Clarify this FAQ example
Release Jetpants 0.7.4:
* Clean up which objects have associated credentials.
* Clean up connection methods in DB class, especially regarding user-
  switching and credential usage.
* Add a Topology#refresh method, for use in long-running scripts that need
  to pick up state changes made by another copy of Jetpants.
* Allow DB#mysql_root_cmd to optionally use or not use the schema name
  on the command line. (This has implications for users of filtered
  replication.)
* The commands "jetpants shard_split_child_writes" and "jetpants
  shard_split_cleanup" are now smart enough to auto-detect which shard
  to operate on, if only one shard is in the middle of a split
  operation.
* "jetpants shard_cutover" now performs validations regarding count of
  remaining spare nodes.
* Add new commands "jetpants summary", "jetpants pools", "jetpants
  pools_compact"
* Remove commands "jetpants show_slaves", "jetpants show_master",
  "jetpants node_info", and remove dependency on terminal-table
* Bug fixes for the simple_tracker example plugin relating to "jetpants
  destroy_slave", as well as "jetpants promotion" with offline master
* Bug fix for "jetpants promotion" when master is offline and using
  options --demote or --promote on command line instead of prompts
Prevent jetpants clone_slave on existing slave targets:
Prevent clone_slave from failing in a confusing way in the following edge
case scenario --
1. A MySQL slave instance has crashed. MySQL is not running, and the node's
   data has been cleared out. The node needs to be re-cloned but will remain
   in the same pool.
2. An asset tracker plugin is in use, and the plugin automatically imputes
   the master/slaves of a non-running MySQL instance by checking the asset
   tracker pool data at probe time.
3. The asset tracker still lists the crashed node as being in its appropriate
   pool, despite the node having crashed.

In this case, attempting to use clone_slave will fail on the call to
DB#resume_replication on the target. The subtle reason is that #2 causes
DB#change_master_to to be a no-op, since the node's @master will already have
been set to the right value already.

This small fix prevents the situation by disallowing existing slaves from
being targets of a clone_slave operation.
Support newer versions of pry
Specify gem versions in gemspec
Adjust gem versions in gemspec
Doc updates
Release Jetpants 0.7.6:
* Compatibility with newer versions of the pry gem -- fixes issues with the
  jetpants console prompt being completely broken.
* Specify required gem versions in the gemspec.
* Fix an edge case in jetpants clone_slave, involving re-cloning a slave
  into the same pool when an asset tracker is in use and jetpants
  destroy_slave was not run prior to the reclone.
Add support for Ubuntu-style service script, and update docs accordingly. Huge thanks to Tim Ellis for testing here.
Fully support Jetpants.standby_slaves_per_pool == 1, and partially support Jetpants.standby_slaves_per_pool == 0