Fix 42 EOL Dates at all relevant places #13348
Labels
No labels
after freeze
automation
backlog
blocked
change-ack
change-nak
change-noreleng
changes
Closed As
Can't Fix
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Get back later
Closed As
Grooming
Closed As
Insufficient data
Closed As
Invalid
Closed As
It's all good
Closed As
taiga
Closed As
upstream
day-to-day
dev
docs
easyfix
epel
f26
f27
f28
f29
f30
f31
f32
f33
f34
f35
f36
f37
f38
f39
f40
f41
f42
f43
f44
f45
fedora
groomed
high-gain
high-trouble
in-progress
in-review
investigation
legal
low-gain
low-trouble
mass rebuild
medium-gain
medium-trouble
meeting
mini-initiative
new_artifact
ops
pdc_retirement
rawhide
RCA
review
script
sidetarget
sprint-0
sprint-1
sprint-2
sprint-3
sprint-4
sprint-5
unfrozen
waiting on external
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Blocks
#13352 Fedora 42 EOL
releng/tickets
Reference
releng/tickets#13348
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?
Describe the issue
It is seen that EOL date for Fedora Linux 42 has been set wrong at various places, release schedule, bodhi. fedora-release, etc We might need to see those and make it uniform.
The correct date should be May 27, 2026 (5 Weeks post the F44 release)
When do you need this? (YYYY/MM/DD)
ASAP
When is this no longer needed or useful? (YYYY/MM/DD)
F42 is EOL
If we cannot complete this, what is the impact?
All users/contributors will be confused.
Checklist
It would good to fix on bodhi, since the current date there is only 3 days away:
2026-05-13.Can this not be done as part of the Fedora N+2 release process?
Here is the current status.
Bodhi
Done.
$ bodhi releases info F42End of Life: 2026-05-27
fedora-release
Stephen Gallagher did the build [1] and the Bodhi update, it's currently sitting in
f42-updates-testing, so we should be good there.fedora-appstream-metadata
I have a PR open [2] and have reached out to @siosm as he usually handles the builds and updates.
F42 release schedule [3]
Well-known pain point. At best a handful of people have access and they are usually very busy. This is not updated and I doubt it will be, until we replace the schedule with something else that can be updated more readily.
[1] https://koji.fedoraproject.org/koji/buildinfo?buildID=2988772
[2] https://src.fedoraproject.org/rpms/fedora-appstream-metadata/pull-request/16
[3] https://fedorapeople.org/groups/schedule/f-42/f-42-releng-tasks.html
This should be done as part of the final release process, so I took the liberty of updating the SOP.
infra/docs#521
It appears that Timothee merged the PR and did the build [1], so this can be closed now. 👍
[1] https://bodhi.fedoraproject.org/updates/FEDORA-2026-d85be6a343