On Tue, Dec 21, 2021 at 10:18 AM Alejandro Saez Morollon <asm@xxxxxxxxxx> wrote: > > I was planning on doing the first, push go 1.18 beta/rc to rawhide (beta1 is already there in fact). Great, that's good to know. It broke my only Go package, but at least go 1.18 is already in rawhide :) > Go 1.18 beta 1 is already in the rawhide branch, so I guess we won't need a second mass rebuild for golang. > Regarding the Fedora 34 /35 impacting the decision. What happens if, for whatever reason, 1.18 breaks a lot of builds and we decide to push back the update. > As 1.17 was never used in a mass rebuild, aren't the stable versions of Go more suitable for the fall-back mass rebuild? Go 1.17 has probably been in rawhide long enough that any big problems should have been noticed already, so I don't think falling back to Go 1.17 for F36 should be a problem, in case 1.18 is very disruptive. Fabio _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
