Release workflow

We are using GitHub Releases for our release workflow. GitHub Releases are based on git tags.

CI builders

• Travis CI - for Linux and OSX builds
• AppVeyor - for Windows builds

Workflow

We only use lightweight tags for releases. This is because as of this writing, AppVeyor cannot start a build when you use annotated tags. See this discussion for more information.

For the tag name, we follow the format v{major}.{minor}.{patch}. For example:

v1.0.0
v1.2.3-rc
v1.2.3-beta

Basically, the release can be done like this:

Update version information in cmd/version.go.

$ git checkout master
$ git pull
$ git tag v1.0.0
$ git push --tags

This will start the CI builds. If all builds are successful, binaries for Windows, OSX and Linux will be uploaded to the tagged release, using the tag name as the release title. The last part of the process is to edit the release notes (maybe add the list of bug fixes).