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/vgo: delete repo in March 2019 (1 month after Go 1.12) #27563
Comments
We did intend for vgo to remain a kind of "preview of next cmd/go" if needed. I don't know that we really want to cut off 1.11. Especially since vgo right now is basically exactly "the go 1.11 cmd/go". |
/cc @bcmills for thoughts |
Talked with @bcmills. Plan is that vgo will stay as it is. There is benefit to letting vgo work with both 1.10 and 1.11, so that it's OK to use vgo and update to 1.11 without changing all the mentions of vgo. But moving on, vgo will not be updated. Once Go 1.12 is out, Go 1.10 will be deprecated, at which point all supported versions of Go will have module support. Then we can remove vgo entirely (maybe a month or so after the Go 1.12 release). |
@bcmills - A CL which removes all code will still keep the repo. I guess it will be better for someone with admin permissions to remove the the git repo altogether at https://go.googlesource.com/vgo/. |
Since Go 1.11 was released several issues related to mixing vgo and go 1.11 have been logged, eg, #27562
I propose that vgo should be changed to work only with versions of Go in the range [1.10.3,1.11)
The text was updated successfully, but these errors were encountered: