Adopt semver

[breathe]

Horse-js is really starting to pick up steam. I think it will really help ease the pain of using horse-js if we adopt semver standards. That said this is still definitely pre 1.0 so I can understand the desire to avoid over-haying about hay stability. But we work towards better hay with the next api release by bumping version to 0.:horse:.1 and continue along that branch until we need to make a backwards incompatible hay in release version 0.:horse::horse:.1. This naming convention should give good compatibility with both node and io.js and I think will work well with upcoming planned changes to node-semver

[breathe]

Also, iconographically including the name of the project in the release number is an important best practice.

[nicktacular]

It's important that we start with commits that are more explicit about what we do for :horse:js such as 8525522ea2aa556a876082e5f876bd3a21ac5b95 and then we move on to a plan for semver. I personally think that if we start with 0.0.0.:horse: we can make the second version 0.0.0.:horse_racing:. The question then becomes, is 0.0.0.:horse: compatible with 0.0.0.:goat:?

[deforestg]

the schema should be as semantic as possible: 0.0.0.:horse: 0.0.0.:horse::horse: 0.0.0.:horse::horse::horse: 0.0.:horse:.0 0.0.:horse:.:horse: 0.0.:horse:.:horse::horse: 0.0.:horse:.:horse::horse::horse: 0.0.:horse::horse:.0 etc

[p33rs]

whoops lol.