mention WP-CLI
Merge pull request #47 from scribu/patch-1

mention WP-CLI in readme
added @scribu to the list of contributors
Merge pull request #50 from carldanley/master

Add @scribu to the list of contributors
README refresh

* Remove a couple of the obvious packages from the "look we install cool things" section. Nobody ever got excited about make being installed.
* Add links to other packages that are actually cool and were missing links.
* Update Vagrant and Virtualbox version information
Allow for custom provisioning to replace the default

It's possible that the framework and directory structure we are providing in Varying Vagrant Vagrants could be useful in the wild without the default provisioning. By allowing for a custom provisioning script, we can use the same project structure with little ramp up time on different provisioning setups.
Add pre/post provisioning hooks to Vagrantfile

If provision-pre.sh or provision-post.sh exist, they are used for additional provisioning with either provision.sh or provision-custom.sh
Introduce a flags system to disable select portions of default provisioning

Allows for simple files to be created in the `provision/flags/` directory that trigger the avoidance of other shell scripting when the provisioning is running.
Display PHP errors by default
Merge pull request #53 from danielbachhuber/display-php-errors

Display PHP errors by default
Updated contributors list
Merge pull request #51 from 10up/provision-hooks

Pre/Post Provision Hooks, Custom Provision Replacement, Provisioning Flags
Add unit tests.
Move tests to shared drive.

It makes sense for the unit test files to be accessible to the host machine. Since /srv/www is the main location for shared files, move the unit tests co to that folder. Update references to the folder as well.
Remove WP_TESTS_DIR variable.

This just not working, so remove it.
Add comments
Properly handle unit tests on reload.

Check for the correct folder to determine if unit tests are installed. If they are installed, perform svn up instead of displaying "already installed" message.
Setup unit tests from the "trunk" WordPress install.

It is best to do unit testing against trunk. Ideally, I wanted to be able to flexibly test against trunk or latest stable. This is going to take some tinkering to get right, so, for now, unit tests will be run against the trunk install.