Skip to content

process: start publishing binary releases #384

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

Closed
zombiezen opened this issue Jun 23, 2017 · 2 comments
Closed

process: start publishing binary releases #384

zombiezen opened this issue Jun 23, 2017 · 2 comments

Comments

@zombiezen
Copy link
Contributor

(Opening this up as a backlog item, not saying we're going to get to this right now.)

This would improve the experience of first-time setup of protoc, since we can say just to download a few binaries. Not sure at what frequency these should be generated (maybe even every commit?).

@twoism
Copy link

twoism commented Jul 20, 2017

Just tagging releases with the source code at the very least would be really helpful. gRPC does this https://github.com/grpc/grpc-go/releases and it makes dependency management much more reasonable. Especially when you have 10s of projects all with a random git SHA in their glide.yaml.

@dsnet dsnet changed the title Start publishing binary releases process: start publishing binary releases Mar 9, 2018
@dsnet
Copy link
Member

dsnet commented Jun 6, 2018

We have begun tagging releases. I don't think it's necessary to keep an issue open regarding this.

@dsnet dsnet closed this as completed Jun 6, 2018
@golang golang locked and limited conversation to collaborators Jun 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants