Lynn Boger

Is the plan to stop providing golang binaries for Go 1.19 and beyond? What about the binaries that already exist, can they stay?

> > Is the plan to stop providing golang binaries for Go 1.19 and beyond? > > I'm hopeful that we can provide binaries using cross-compilation. > > > What...

> If we do this, we'll provide toolchains that use cgo by default but that rely on the host C compiler to complete the cgo build. I think the only...

> The idea would be to build toolchain that didn't use cgo itself, but had cgo enabled by default. That wouldn't require a cross-compiler to build, so shipping the binaries...

> Otherwise it sounds like people are mostly on board. I'm still a bit concerned about the language for broken ports and removal from releases. Some of it is vague...

Here are comments on some of the language, some a few suggestions: > We should not assume that maintainers will respond within 2 or 4 weeks; people are busy. What...

> spoke with @heschi, and the release team is OK with committing to posting cross-compiled toolchains for secondary ports with an appropriate disclaimer on them. What is the disclaimer? I...

I can see where you would only want to run the default trybots when making a change that touches only general purpose files that may or may not affect secondary...

This change causes build errors on ppc64le on master with Openshift. Please hold off on backporting. I have asked the testers to open an issue with reproducer information.

This happens on ppc64le.