Release strategy

[montanaflynn]

Since the public API isn't finalized I've been suggesting to simply clone and vendor into your projects but I'd like others to be able to take advantage of tools like godep, glide, gopkg.in to install stats into their projects.

How can we best release changes to stats? I'd like to automate it if possible, as of now I'm building the CHANGELOG.md and git tagging manually which is slow and error prone.

Does anyone have experience with releasing packages into the Golang ecosystem?

[tamird]

Releases are more mature now that https://github.com/golang/dep is coming into its own.

For what it's worth, the current releases in this repo do more harm than good; tools like dep prefer releases over master-branch, but the releases here are several years old, forcing people to use the master branch anyway.

It would be better to either remove the existing releases until a strategy is decided on, or simply release a new version (the number won't matter).

[montanaflynn]

I've added a new release 0.3.0. Looking into https://research.swtch.com/vgo which might require adding a v prefix to the releases / tags so it can be used.