@dr2chase This backport issue is still open but without CherryPickApproved nor CherryPickCandidate label. Should this go back to approved but with [CL 749241](https://go.dev/cl/749241) as the new CL …
We reviewed and approved this during a release meeting, moved CherryPickApproved from https://github.com/golang/go/issues/77737#event-23078589596 to this issue. (CC @dr2chase.)
This issue was marked as fixed by [CL 747900](https://go.dev/cl/747900), but that CL is in the main branch of x/tools. That's sufficient to fix the problem in time for Go 1.27, but this issue is curr…
Thanks.
Maybe related that macOS 10.14 came out in Sept 2018, in between Go 1.11 (Aug 2018) and Go 1.12 (Feb 2019) releases. So they both probably worked, perhaps even older Go versions too given ma…
Thanks. Some minor (optional) suggestions.
Splitting this long line to one-line-per-command for readability seems good, but maybe it's worth keeping the one-command-pipe-into-another together? I don…
In the past we may have previously relied on the CheckUserCredentials check to suggest this step if it wasn't already done (see [here](https://cs.opensource.google/go/x/build/+/master:buildenv/envs.g…
The alternative path would be to resolve the merge conflict in CL 746361, which involves a 2 line diff:
```diff
func SetEntriesInAcl(countExplicitEntries uint32, explicitEntries *EXPLICIT_A…
We reviewed and approved this during a release meeting, moved CherryPickApproved from https://github.com/golang/go/issues/77659#event-23078585370 to this issue.
We reviewed and approved this during a release meeting, moved CherryPickApproved from https://github.com/golang/go/issues/77482#event-23078592981 to this issue.
Thanks for sending the change. Part of the migration appear to be incomplete, and there are some failing tests reporting that. The Go project has conventions for how to write the commit message at ht…
At https://docs.cloud.google.com/storage/docs/gsutil#should-you-use it
is suggested to prefer using 'gcloud storage' instead of gsutil. Do so.
This was originally brought to my attention via the des…
Previously, if the CSR was somehow generated without a .bots.golang.org
suffix, the hostname check would catch that it didn't match but print a
message that's not very clear. Make it more detailed.
…
Thanks. Here's the new corresponding certificate: [linux-mipsle-hooc-ag-1771954236.cert.txt](https://github.com/user-attachments/files/25526903/linux-mipsle-hooc-ag-1771954236.cert.txt).
(1 comment)
For posterity, this was a case of anchor format being different in the newer x/pkgsite doc viewer and that change not being backported the old doc viewer (compare https://pkg.go.dev/sync…
Submitting CLs on release-branches is limited to release managers. See https://go.dev/wiki/MinorReleases:
> The code review process is otherwise the same as regular CLs. Permission to submit to the …
> I also wonder why this check wasn't added to go test once it was introduced; it seems like a simple (and presumably fast) check that should have zero false negatives.
I noticed that the accepted p…
(Factored out a maintner improvement opportunity from the gopherbot-specific issue #29599.)
It'd be good if maintner's detection and reporting of issue references was improved. There is an existing …
Adding proper support to detect the verb in maintner is quite a bit of
work, and it needs to be done in a performant way because that code will
run unconditionally on all issue references.
On the ot…
> To avoid any inconsistencies, I will generate a new private key and CSR for linux-mipsle-hooc-ag and request a fresh certificate.
Sounds good. I've revoked the previous certificate and can generat…
Thanks.
Noting this part of the comment as a nearby place that's a bit more targeted on vet (and its -vettool flag) and less so on fix (and its -fixtool flag). But that seems fine as above it does s…
This builder is back online and idle, so this is resolved. It won't be receiving new work though as it was testing with macOS 11, and that stopped being needed after Go 1.24 became unsupported.
This builder is back online and idle, so this is resolved. It won't be receiving new work though as it was testing with macOS 11, and that stopped being needed after Go 1.24 became unsupported.
Yes, I don't see any problem with that. For every builder name, such as `linux-s390x-ibm--02`, there should be only 1 running instance of the swarming client process (that bootstrapswarm runs), not …
@willfaught Thanks for the report and filing a proposal.
I'll reference a subset of https://go.dev/conduct#values here:
> - Be charitable.
> - [...]
> - When we do disagree, try to understand why…
@seankhliao Thanks, that's a good idea to consider too. It sounds quite a bit simpler at a glance, though we'd still want to make sure we're able to maintain it to always be up to date (either manual…
We already have some dashboards at https://dev.golang.org/, including https://dev.golang.org/release, that can be candidates for this. Another idea to explore is whether we could also mirror the tree…
The Go tree regularly goes from "open for development" to "frozen for release" states, with 2 release cycles or 4 state transitions per year. During early tree reopening, there are some additional bu…
The {{raw `…`}} sequence is commonly used in Markdown templates to
include a block as is. If such a sequence is used in a Markdown file
while its 'template' field in metadata is accidentally set to…
@mrkfrmn Thanks. Note that I left a comment on [CL 746360](https://go.dev/cl/746360), I believe it already handles the vendoring for this backport issue as is, only its commit message does not curren…
(1 comment)
Since 'drop requirements for unsupported Go versions' is a WIP CL that comes after this one, and I understand this table tries to capture the information when a given Kernel became requi…
Thanks.
Was https://go-review.googlesource.com/c/website/+/745380/comment/fdba0ae1_5a22a858/ missed? It was about s/Repeat/Attempts/ rather than gofmt, since `type RequestJSON` definition above had …
Please see https://go.dev/wiki/MinorReleases for more information on the backport process. This cherry pick candidate is waiting to be reviewed first. We'll ask for your help with creating the backpo…
[CL 733180](https://go.dev/cl/733180) is already submitted on internal-branch.go1.26-vendor branch of x/tools, so what's left is to [vendor it](https://cs.opensource.google/go/go/+/release-branch.go…
@gopherbot Please consider this for backport to Go 1.26. It's needed to prevent overlapping stringsbuilder fixes (#77620, #76983) from causing `go fix` to generate invalid code.
Applying the stringsbuilder suggestion in an editor previously ended up
inserting (or rather leaving behind) an extraneous space:
-s += "abc"
+s .WriteString("abc")
Adjust the edit to leave the s…
> Thankfully the instructions on the website are correct.
It looks like they were fixed very recently, in commit de21bcf257f796c33ec3aa9ec7e20c55c0717993.
> that means the intent of getting this fixed in go1.21.1 is recorded only in my head
It's okay to create the backport issue as soon as you think it should be considered for backport, before the iss…
@adonovan Note that manually placing an issue in a Go minor release milestone can lead to it being missed in weekly backport review and in [minor release note](https://go.dev/doc/devel/release#go1.25…
With the release of [Go 1.26.0](https://go.dev/doc/go1.26#introduction), the two latest supported major Go releases are 1.26 and 1.25 per the [Go release policy](https://go.dev/doc/devel/release#poli…
With the release of [Go 1.26.0](https://go.dev/doc/go1.26#introduction), the two latest supported major Go releases are 1.26 and 1.25 per the [Go release policy](https://go.dev/doc/devel/release#poli…
With the release of [Go 1.26.0](https://go.dev/doc/go1.26#introduction), the two latest supported major Go releases are 1.26 and 1.25 per the [Go release policy](https://go.dev/doc/devel/release#poli…
They are. Although Go can make them too easy via `go:embed`.
See some initial comments.
I suggest either adding a quite that can be licensed via the existing BSD-3-Clause LICENSE at the top level o…
Thanks! Congrats on your first change. :D
See one inline comment that's unresolved (yellow border). You can leave a draft comment like "Done." and mark the 'Resolved' checkbox, then when you upload …