F41 Change Proposal: Golang 1.23 (System-Wide)

Golang 1.23

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Wiki
Announced

:link: Summary

Update of Go (golang package) to the upcoming version 1.23 in Fedora 41.

:link: Owner

:link: Detailed Description

Update of Go (golang package) to the upcoming version 1.23 in Fedora 41. Go 1.23 is expected to be released in August 2024. A mass rebuild of all of the dependent packages is required.

:link: Feedback

No feedback yet.

There is an ongoing conversation about removing a patch and revert to the defaults a couple of variables.

:link: Benefit to Fedora

Up-to-date and latest Go release will be delivered to Fedora users. Being close to upstream allows us to avoid security issues and provide more up-to-date features. Therefore, Fedora will be providing a reliable development platform for the Go language and projects written in it.

For a complete list of changes, see upstream change notes at Go 1.23 Release Notes - The Go Programming Language

:link: Scope

  • Proposal owners:

Rebase Golang package in Fedora 41, and help resolve possible issues found during package rebuilds.

  • Other developers:

Fix possible issues, with help from Golang maintainers.

Rebuild of dependent packages as part of planned mass-rebuild.

  • Policies and guidelines: N/A (not needed for this Change)

  • Trademark approval: N/A (not needed for this Change)

  • Alignment with the Fedora Strategy:

It doesn’t align directly with the current objectives, but it helps maintain the quality of the project.

:link: Upgrade/compatibility impact

No upgrade or compatibility impact.

:link: How To Test

  1. Install golang 1.23 from rawhide and use it to build your application(s)/package(s).
  2. Perform a scratch build against rawhide.
  3. Your application/package built using golang 1.23 should work as expected.

:link: User Experience

Users will have a newer version of Go, with new features described in the release notes and security fixes.

:link: Dependencies

dnf repoquery -q --releasever=rawhide --disablerepo=‘’ --qf=‘%{name}’ --enablerepo=fedora-source --enablerepo=updates-source --enablerepo=updates-testing-source --archlist=src --whatrequires ‘golang’ dnf repoquery -q --releasever=rawhide --disablerepo='’ --qf=‘%{name}’ --enablerepo=fedora-source --enablerepo=updates-source --enablerepo=updates-testing-source --archlist=src --whatrequires ‘compiler(go-compiler)’ dnf repoquery -q --releasever=rawhide --disablerepo=‘*’ --qf=‘%{name}’ --enablerepo=fedora-source --enablerepo=updates-source --enablerepo=updates-testing-source --archlist=src --whatrequires ‘go-rpm-macros’

Omitted due to the number of packages listed: ~2000.

:link: Contingency Plan

  • Contingency mechanism: Revert to Go 1.22.X if significant issues are discovered
  • Contingency deadline: Beta freeze
  • Blocks release? No

:link: Documentation

:link: Release Notes

Last edited by @amoloney 2024-05-31T22:48:59Z

1 Like

How do you feel about the proposal as written?

  • Strongly in favor
  • In favor, with reservations
  • Neutral
  • Opposed, but could be convinced
  • Strongly opposed
0 voters

If you are in favor but have reservations, or are opposed but something could change your mind, please explain in a reply.

We want everyone to be heard, but many posts repeating the same thing actually makes that harder. If you have something new to say, please say it. If, instead, you find someone has already covered what you’d like to express, please simply giving that post a :heart: instead of reiterating. You can even do this by email, by replying with the heart emoji or just “+1”. This will make long topics easier to follow.

Please note that this is an advisory “straw poll” meant to gauge sentiment. It isn’t a vote or a scientific survey. See About the Change Proposals category for more about the Change Process and moderation policy.

This change proposal has now been submitted to FESCo with ticket #3224 for voting.

To find out more, please visit our Changes Policy documentation.