Go 1.25 in Fedora 42 #3570
Labels
No labels
document it
fast track
meeting
next release
nonresponsive maintainer
packager revocation
pending announcement
provenpackager
python 2 exception
self contained change
stalled
Status
Accepted
Status
Duplicate
Status
Insufficient data
Status
Invalid
Status
Rejected
system wide change
updates policy exception
vote-in-progress
No milestone
No project
No assignees
8 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
fesco/tickets#3570
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fedora 42 has Go 1.24, which is effectively EOL since 1.26.0 came out recently.
As in previous requests, can we update the version in Fedora 42 to Go 1.25 to avoid the EOL and allow packages to be updated?.
Previously, it was suggested to make this part of the usual release process for newer versions of Go, but I don't recall adding it to the 1.26 proposal, so I open this ticket once more for transparency.
+1
Metadata Update from @decathorpe:
+1, but also:
Proposal: Given that the Go schedule is predictable and not aligned with Fedora's stable lifecycle, FESCo grants a blanket permission to update stable Fedora releases to newer Go releases.
Yeah, +1 this request, but also +1 a persistent approval.
Yes to the permanent exception. +1
+1, with the caveat that for now, I'd only think this should happen on Fedora N-1 as soon as the Go version there is EOL upstream. A permanent blanket exception for stable branches is something that could be considered, but that would require more discussion IMO.
+1 to both too. (Though I agree with decathorpe that it'd be better to do this separately, with a concrete proposal text.)
Absolutely, when I said, "make this part of the usual release process", I meant to do it only on Fedora N-1 and only when the Go version goes EOL. I do believe it is the sane and conservative way to handle the schedule mismatch.
OK, I'll revise my previous Proposal to be more constrained.
Proposal: Given that the Go schedule is predictable and not aligned with Fedora's stable lifecycle, FESCo grants a blanket permission to update stable Fedora releases to the next supported release once the version that was shipped at Fedora's GA has gone end-of-life.
Note: this restarts the seven-day voting period for the permanent exception, but the original request on this ticket will be approved tomorrow, assuming no -1 votes appear.
+1 for the specific exception
Also +1 for the blanket permission in stable releases if the golang version shipped goes EOL per Stephen's last proposal
+1 to the revised proposal.
+1 to revised proposal.
+1 to revised proposal.
+1 to revised proposal and pre-emptively approving permanent exception.
The first part is approved after a week:
APPROVED (+5, 0, 0): "update the version in Fedora 42 to Go 1.25 to avoid the EOL and allow packages to be updated"
Metadata Update from @zbyszek:
I filed fesco/docs#128 based on @sgallagh's proposal.
The PR was merged.
Announced in the 2026-02-24 meeting summary
Metadata Update from @sgallagh:
Reopening while we resolve the question of a permanent exception. It was probably premature to merge the docs MR yet, but in the unlikely event that we reject this proposal, we can revert it.
Metadata Update from @sgallagh:
Oh indeed, I shouldn't have done that. But let's just wait for the clock to run out.
I think both parts (the one-time exception and the permanent exception) can be considered approved now. It's been enough time and there haven't been negative votes.
Metadata Update from @decathorpe: