Marking as resolved (per discussion in other thread). There are still some failures on https://ci.chromium.org/ui/p/golang/builders/ci/gotip-plan9-amd64, but that can be tracked in a followup to #636…
Made the [second pre-release tag](https://pkg.go.dev/github.com/go-gl/glfw/v3.4/glfw@v0.1.0-pre.2) to include some of the follow up fixes to v3.4/glfw. If some time passes and there aren't problems r…
Thanks for preparing this. Closing since this change needs to happen upstream. Note that by now v3.4 has superseded v3.3, so it may make sense to redirect our attention towards the latest version in …
Thanks for preparing this. Closing since this change needs to happen upstream. Note that by now v3.4 has superseded v3.3, so it may make sense to redirect our attention towards the latest version in …
One more note. In the PR description it was mentioned that this change was done with `go mod edit -go=1.26`. In most cases it should be a better experience to manage the `go` directive with the `go g…
Thanks, this generally looks good. I left two minor comments.
I suggest picking `1.26.0` for the `go` directive here.
Prior to Go 1.21, major releases didn't have a ".0" at the end. See https://go.…
Sounds good, thanks.
If someone wishes to use an older version of go-gerrit before its `go` directive increased for a while longer, even if you don't tag, they could still use the corresponding ps…
> Go 1.27.0 is the current upstream release, so the supported window moves to 1.27 + 1.26 per the [Go Release Policy](https://go.dev/doc/devel/release.html#policy) the README commits to. [...] The `g…
(2 comments)
This isn't quite right. According to the spec, the optional [init statement](https://go.dev/ref/spec#InitStmt) is a [simple statement](https://go.dev/ref/spec#SimpleStmt), which in addi…
(1 comment)
At least in Go 1 package documentation it was a documented bug that gave the heads up that the behavior may change in a future version:
https://pkg.go.dev/encoding/json@go1#pkg-note-BUG
How does this compare with CL 812781?
This looks good too, just please coordinate with Michael. Thanks.
For #80818? Or is there another tracking issue for these perf builders?
See https://go-revie…
Thanks.
I don't mind seeing a note like this in a code review comment, but I'm not sure about including it in the commit message itself. Perhaps this is still a topic being discussed and I may chang…
(4 comments)
Consider making this commit message much shorter, focusing on the problem being surfaced by the Go 1.26 vet check (#72850). For example, compare with similar CLs for x/sys and x/exp: CL…
As suggested at https://go.dev/issue/80220#issuecomment-5350598333,
it can be helpful to say a few more words about the exact Python 3
version that should be used. Also, an optional reference, point …
Thank you!
Yes, proposal #69095 was about having a policy and automation to maintain the minimum value of the `go` directive in golang.org/x modules, and this CL is a part of that, but it's possible…
With the release of [Go 1.27.0](https://go.dev/doc/go1.27), the two supported major Go releases are 1.27 and 1.26 per the [Go release policy](https://go.dev/doc/devel/release#policy). Closing this 1.…
With the release of [Go 1.27.0](https://go.dev/doc/go1.27), the two supported major Go releases are 1.27 and 1.26 per the [Go release policy](https://go.dev/doc/devel/release#policy). Closing this 1.…
With the release of [Go 1.27.0](https://go.dev/doc/go1.27), the two supported major Go releases are 1.27 and 1.26 per the [Go release policy](https://go.dev/doc/devel/release#policy). Closing this 1.…
With the release of [Go 1.27.0](https://go.dev/doc/go1.27), the two supported major Go releases are 1.27 and 1.26 per the [Go release policy](https://go.dev/doc/devel/release#policy). Closing this 1.…
With the release of [Go 1.27.0](https://go.dev/doc/go1.27), the two supported major Go releases are 1.27 and 1.26 per the [Go release policy](https://go.dev/doc/devel/release#policy). Closing this 1.…
With the release of [Go 1.27.0](https://go.dev/doc/go1.27), the two supported major Go releases are 1.27 and 1.26 per the [Go release policy](https://go.dev/doc/devel/release#policy). Closing this 1.…
With the release of [Go 1.27.0](https://go.dev/doc/go1.27), the two supported major Go releases are 1.27 and 1.26 per the [Go release policy](https://go.dev/doc/devel/release#policy). Closing this 1.…
With the release of [Go 1.27.0](https://go.dev/doc/go1.27), the two supported major Go releases are 1.27 and 1.26 per the [Go release policy](https://go.dev/doc/devel/release#policy). Closing this 1.…
@xcolwell I believe support for type aliases in x/mobile was already added as of [CL 740861](https://go.dev/cl/740861), so the temporary workaround of setting GODEBUG manually in the environment shou…
I found [go.dev/cl/804720](https://go.dev/cl/804720) that matches this description, is that what you're referring to? If so, the issue in that CL is that it's on the main branch, so it needs to use "…
@srinivas-pokala Thanks for reporting this. Can you please include links to where you ran into this?
One possibility is that the builder names and repository branch names are out of alignment. In th…
As visible on the build dashboard¹² and reported in go.dev/issue/80703,
the power8 builders are gone. Annotate them with a known issue to hide
some purple boxes from the build dashboard, making it …
This is the tracking issue for writing the Go 1.28 Release Notes. The version at tip can be viewed at https://tip.golang.org/doc/next.
When we have a fairly complete release notes draft, enough for …
The Go 1.27.0 release is out, so 1.26 is the oldest supported release.¹
The previous infrastructure (cmd/coordinator) does this automatically,
whereas here I authored this CL manually. We'll explore…
Thanks.
Since by now a stable version of Go 1.27 is also available and should work as well as Go 1.26 and better, you could go to it directly. Its other advantage is that it'll be supported for 6 mo…
Thanks. One optional comment.
Hmm, I noticed that in [Go 1.24 release notes](https://go.dev/doc/go1.24) and older this was linked. I'm not sure why 1.25 onwards stopped doing it, and I wonder if may…
Hello,
I see that the README at https://github.com/gophers-latam/go-tour-es#%EF%B8%8F-reportar-issues already points to this issue tracker for issues with the Spanish translation of the Go tour. How…
(1 comment)
In future commit messages, please consider this commit message suggestion from https://go.dev/wiki/CommitMessage:
> when referencing CLs, prefer saying “CL nnn” or using a go.dev/cl…
@thiagomowszet@gmail.com Is there an issue tracker that can be used to report issues related to the Spanish translation of the tour at https://go-tour-lat.appspot.com/ ? The 'submit feedback' button …
(1 comment)
Is it expected that `go mod tidy` seemingly undoes this change (because the newly added requirements are only indirectly used)? This repo seems to use go-git/v5.
Patchset 3 passed all trybots, except go1.25-wasip1-wasm_wasmtime failed in time package due a timeout. It doesn't seem related, and it passed on second try, so adding bypass.