New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/build/cmd/relui: create GitHub releases #15966
Comments
I think I'd rather have a release API hosted on golang.org that provides a list of releases, tag names, binary URLs, etc. |
One advantage would be to provide an API via Github for tools like |
I would vote for utilizing GitHub's releases feature. In fact it is already being utilized but only the source files are released. The only overhead I can think of is the added step in the release process, which is not an issue since it will be automated using GitHub's Releases API. A few advantages that I can think of are following:
Note: To sanitize automatic source releases on GitHub, |
@broady why not both? |
@broady, want to make a decision? |
The only downside I can think of is that it makes it a little more difficult for analytics on downloads. I'll add this to the release tool. I don't see a pressing need for a separate API on golang.org. The only thing to consider is whether to use @gopherbot's credentials or the end-user's GitHub credentials. I'd lean toward @gopherbot, and have gopherbot's token available from some endpoint gated by the "user-release" build token. |
I'm looking into this, if you accept a PR I would submit it. However, I would before define the expected behavior for the command.
|
@andybons Do you have any suggestion? |
Some corporate firewalls block anything from dl.google.com which currently hosts binary releases. |
CC @golang/release. |
I would like to add that having a single format (i.e. schema to parse) for downloading/upgrading binaries from (vs having to build everything), is a huge advantage to many folks. I've already written my own batch job that automates downloading new releases from GitHub, so GO has become a one-off that I have to remember to manually check. |
That would be an absolute killer feature for me as a Go dev. I'd get an eMail automatically (wouldn’t have to check manually) triggering me to add the new Go version (and the new archs) to my apps' CI matrices. |
@Al2Klimov The golang-announce mailing list should serve that purpose for you. |
GitHub has a "releases" feature that provides downloadable releases in a well-known location. We could make Go releases available via GitHub as well as our download page.
Assuming we want to do so, we could modify the
release
tool to create and populate those releases for us automatically.But do we want to do this? What are the advantages? What are the disadvantages?
The text was updated successfully, but these errors were encountered: