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".
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).
changed the title
Proposal: x/vgo: disable standalone 'vgo' binary for Go 1.11 and aboveOct 11, 2018