-
Notifications
You must be signed in to change notification settings - Fork 18k
all: Go 1.16 release status #44292
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
Comments
Log
|
Latest build: go1.16
Log
|
Change https://golang.org/cl/292689 mentions this issue: |
For golang/go#44292. Updates golang/go#27155. Co-authored-by: Matt Pearring <[email protected]> Change-Id: I6e0d6731d5848f81fce7e77cbb068174462c0e4e Reviewed-on: https://go-review.googlesource.com/c/blog/+/292689 Trust: Dmitri Shuralyov <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]>
@toothrot Do you know when https://go.googlesource.com/tools.git/+refs gets updated with a 1.16 version? |
@zikaeroh Ah ok, I was asking because I made a PR to bump the homebrew formula and their CI requires that to be present: Homebrew/homebrew-core#71289 |
That's the case laid out in #36882 (comment), yeah. I'll defer to an actual Go team member, clearly (IDK if the policy actually changed given #36882 is open), I just recalled that thread existing. 🙂 |
Similar to what @zikaeroh helpfully said, the canonical x/repo version info for a Go release is contained in the appropriate I'm not sure what the tools repository is used for in homebrew, but the versioning strategy should probably be discussed somewhere listed here: http://golang.org/wiki/Questions. |
For golang/go#44292. Updates golang/go#27155. Co-authored-by: Matt Pearring <[email protected]> Change-Id: I6e0d6731d5848f81fce7e77cbb068174462c0e4e Reviewed-on: https://go-review.googlesource.com/c/blog/+/292689 Trust: Dmitri Shuralyov <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> X-Blog-Commit: c4aa98e750f4c42d7ff9b909ac5e5d83d0b92769
Issue tracking the go1.16 release by releasebot.
The text was updated successfully, but these errors were encountered: