Move to semantic versioning

[marpaia]

As referenced in #22, let's consider moving to semantic versioning so that users can be aware of breaking API changes.

[spheromak]

Yea I was thinking the same thing. Dunno who is using the lib, but that merge will guarantee a break.

[spheromak]

@marpaia I pushed the 0.1.0 tag on current master, thoughts on pushing 1.0.0 so that we can direct people to using gopkg.in for a stable api import?

I want to do this before moving on more refactoring to api.go and ingeneral the fixes for #28 gopkg.in only support linking to the major version. So people will have to pull that 1.0 out. I could also tag the ref before the config change as 1.0.0 and then start hacking away either way.

[marpaia]

let's make a project roadmap wiki :D

[josephholsten]

<3