Provide aliases for failure_message_when_negated so rspec < 3 still work
Whitespace and such
Allow for validator hosts that have a port number
Run transpec on specs to get rid of rspec 2.99 dep warnings
Detect presence of Rspec 3 skip exception and use that

Fallback to the older one so that rspec < 3 will still work (and rspec 2.99 won't complain about dep warnings).
Use rspec 3 for development

Pick off final bit of old-style rspec that transpec didn't pick up when we were using rspec 2.99
Rspec 3: disable monkey patching
Allow for protocol-less host config again

Provide specs this time.
Bump version (and copyright year)
Add latest set of contributors to authors list
Extract simple changelog from commit history
Specify development dependencies in Gemfile.

Turns out that rubygems >= 2.2.0 doesn't allow duplicate dependencies in the gemspec.  I'm not sure if this is intentional behaviour when the "duplicates" are runtime vs. development dependencies (raised as https://github.com/rubygems/rubygems/issues/1032), but even if it is wrong, we can't release the gem until a fix comes out.

We can just remove the development dependencies from the specification and define them in the project gemfile instead.  It's not as clear a signal, but it'll do for now.