Use GitHub Releases for binaries

[ddollar]

Use GitHub Releases for binaries

[ddollar]

The compilation is done on Heroku and the releases are stored on S3. What is gained by adding more pieces to this process?

[nikolay]

What's accomplished is the ability to use GitHub API to query available versions, latest version, specific version's binaries, etc. Many projects are using this already, so, it's nice to use a more standard approach.

[jdx]

@nikolay if you use osx, we just added the forego formula

[ddollar]

This would involve creating a system to do the cross-compile builds and manage releases using Github's API. This is a decent amount of software to write for a benefit that is still not clear to me.

[nikolay]

@dickeyxxx Yes, this is how I found about forego (the rewrite in Go). Thanks!

[nikolay]

@ddollar Can't this be done by using Travis CI? Let me look into it and I will make a more specific suggestion, maybe even a PR. Thanks for responding so quickly!

[jdx]

@nikolay @ddollar I want to get a good release strategy for https://github.com/heroku/hk, so I'm thinking of working on a good generic strategy for go packaging/building. I don't think travis will work though since I don't think you can use the cross-compilation on it. (Although I could be incorrect)

[nikolay]

@dickeyxxx I've seen people using gox more and more recently for cross compilation, but you most probably are right about the Travis concern.

[jdx]

travis-ci/travis-ci#2207 looks like they need to support ARM

[jdx]

I wonder if the rest would work?

[ddollar]

Travis does not seem like the appropriate venue to me. Travis builds for every branch created, pull requests, all sorts of things. Special casing code off of master sounds janky.