Create annotated tags for releases

[benma]

Hi

It would be great if you tagged the current HEAD with v1.0.0, and in the future, occasionally bump the version and make new tags with new releases. I suggest using the semver.org versioning scheme, where you have major.minor.patch, and you bump the major for incompatible changes and the minor for compatible changes to the API.

[alexjlockwood]

Thanks for the suggestion! There are a few changes I've been wanting to make to this library to support new features but am not familiar with how versioning works in go, TBH. I've been afraid that incompatible changes I make will break people who have already go-getted this library for their own projects. Do you have any suggestions on where I could read up on this?

[benma]

As far as I know, there is no standard way of doing versioning in Go projects.

Since Go 1.5, vendoring is the recommended way of handling dependencies:
https://golang.org/cmd/go/#hdr-Vendor_Directories

If people use this and vendor a specific version of your package, incompatible upgrades to it won't break the project (i.e. when it is fetched with go get, which just gets master).

I suggest to follow http://semver.org/, as it is pretty simple (see my first comment).
It is of course also a good idea to maintain a changelist that details the changes, and a way forward for breaking changes.