On Wed, Sep 3, 2025 at 2:52 PM Alejandro Saez Morollon <asm@xxxxxxxxxx> wrote: > > The idea I'm considering: maintain identical Go versions across all active Fedora releases. Ideally, starting with the next Fedora release, every new stable release will have the latest Go version. For example, by the time of Fedora 45; Fedora Rawhide, Fedora 45, and Fedora 44 would have 1.27. I would rather not apply this to the current stable releases to avoid unnecessary mass rebuilds and issues. I am of two minds on this. As a maintainer of a Go application (syncthing), this might make my life a *little bit* easier, though ... not that much: syncthing is also built for EPEL, which also lags behind the latest stable version of Go - though less bad than Fedora "oldstable". So it would make things a bit easier in Fedora, but not across Fedora *and* EPEL. Or would you coordinate shipping the Go minor updates with when they are also pushed out in RHEL minor versions? 🙃 On the other hand, I've frequently seen Go compiler updates introducing new bugs, new lints / vet things that break compiling existing packages. Pushing these compiler updates to stable releases frequently might be more disruptive than we'd like :( 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, report it: https://pagure.io/fedora-infrastructure/new_issue
