Given the release schedule, I highly doubt that a non beta/rc will be available at the time of the mass rebuild.
It's not the first time this has happened as far as I'm aware. That's the problem with the Go schedule and why I sent an email couple days ago
asking for input about it.
A solution to this situation will be to use modules and keep Fedora N in a previous release. But this does only solves
the demands of the users, packages cannot use module streams, right?. Correct me if I'm wrong, please.
My biggest concern is that currently, we have 1.16 in Fedora 34 and Fedora 35.
So if we can't update Fedora 36 to Go 1.18, by the EOL we will
have a non upstream supported Go version with ~1900 packages depending on it.
In that scenario, I would personally like to do a mass rebuild to make 1.17 available on Fedora 35 and 36.
But I'm not sure about how possible this is.
Any suggestion is highly welcome :)