add ruby 2.1.1 to travis-ci
this serverspec version does not work w/ rspec-3.0
Merge pull request #368 from tacahilo/add-ruby2.1.1-to-travisci

add ruby 2.1.1 to travis-ci
Merge pull request #370 from tagomoris/rspec-2.x

this serverspec version does not work w/ rspec-3.0
Bump up version
Do not merge stdout/stderr.

The reason of the merge was the fact that when SSH was requesting a PTY,
stdout/stderr were merged. However, the use of PTY was made
optional (only used for sudo password) in this commit:
 https://github.com/serverspec/specinfra/commit/b4153a7f4f79cfcf5b1d91ebf77da66bd3e76b78

Therefore, we now need to access the true stderr for tests to work as
expected.

The user has to know if he should use stdout or stderr for its
tests. The documentation may state that the use of sudo password will
merge stdout and stderr.
Merge pull request #375 from vincentbernat/fix/stdout-stderr

Do not merge stdout/stderr.
Bump up version
Add constraint ruby version because rake 10.2 does not support Ruby 1.8
anymore
Remove allow_failures
Add ipaddress method to host type
Add spec
Merge pull request #376 from serverspec/add-ipaddress-method-to-host-type

Add ipaddress method to host type
Bump up version
Fix how to run the command following serverspec/specinfra#71
fix indent and insert a line between methods for readability
Merge pull request #377 from serverspec/fix-process

Fix how to run the command following serverspec/specinfra#71
Merge pull request #380 from serverspec/fix-indent-and-insert-empty-a-line-betwoon-methods

fix indent and insert a line between methods for readability
Add constrain to octokit version because latest octokit requires Ruby >= 1.9.2
Don't conflate stdout and stderr; run commands once

It was previously that if one asserted something about a command's stdout, then
asserted something about the stderr, the 2nd assertion, the one about stderr,
would actually compare to stdout.

Also, each assertion (about the exit status, stdout, stderr), would run the
command each time. Very problematic for commands that are expensive to execute,
or have side effects.