Re: Looking for feedback: Unified Go versioning across all Fedora releases

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hey Alejandro,

On Wed, 2025-09-03 at 14:51 +0200, Alejandro Saez Morollon wrote:
> Hi everyone, I'm contemplating a change to how we handle the Go
> releases in Fedora and would like community feedback before moving
> forward with a formal proposal.

+1 from me, as a maintainer of a non-trivial but not massive Go code
base.

> Currently, each Fedora release ships with a different Go version. For
> example, right now:
>  * Fedora 41: Go 1.23 (upgraded to 1.24, see point 1 in the next
> list)
>  * Fedora 42: Go 1.24
>  * Fedora 43: Go 1.25
> This creates several problems:
>    1. Both Go and Fedora releases happen every six months, but they
> are a little off; almost end-of-life Fedora releases will have end-
> of-life Go versions for around 2 months. To avoid this scenario, we
> have to ask for an exception to upgrade Go in those versions.
>    2. Package maintainers must support multiple Go versions
> simultaneously across different Fedora releases, increasing testing
> complexity and bug surface area. Go is superb at maintaining
> retrocompatibility, but upstream projects tend to enforce the latest
> Go version for different reasons.
>    3. Go developers tend to use the latest version available as soon
> as possible, but this latest version is only available in the latest
> Fedora stable release.

This tendency of Go modules (used as dependencies) to keep updating the
required Go version has started to bother me in recent times.  It
doesn't look like the Go toolchain strictly enforces the version,
because I remember trying to build with an older version and
succeeding, or maybe I am misremembering?

Anyway, having the same recent version of Go across all stable releases
will let me sleep better because it's one less thing to worry about
when rushing to ship fixes for some important security issue in a
bundled dependency.

Cheers,
Rishi
-- 
_______________________________________________
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux