Next steps for Go

Hi, everyone! Looking for your thoughts on how to finish the initial cleanup of Go ports.

Go 1.26 is right around the corner, and it comes with dropping support for 1.24, which is an issue for any port that says `USES=go:1.24` (without a +). We’re way too late to try to fix up go124 dependencies before 1.26 drops.

We need ports to switch from `USES=1.24` to `USES=1.24+`. Similarly, in 6 months we’ll need to do the same to USES=1.25.

Questions:
- Should we create a PR or review and tag each maintainer?
- Should we send emails and explain the problem and ask them to help with their port?
- Should we Just Fix It ourselves, given it’s a trivial change and we’re perhaps best positioned to know when a go port actually is 1.24+?

- What kind of timeline should we shoot for? If it’s a Just Fix it we can get it done real quick, but if we want maintainers to get involved we should have an end date in place.

- Should we include USES=1.25 now to get it out of the way, or do it again in 6 months?

- Should go.mk have a new warning message that says, “You specified USES=go:1.22, but you probably wanted USES=go:1.22+”?


—
Adam Weinberger
adamw@adamw.org
https://www.adamw.org