Fix 42 EOL Dates at all relevant places #13348

Closed
opened 2026-05-07 15:53:47 +00:00 by jnsamyak · 4 comments
Owner

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

  • I have checked existing issues for duplicates
  • I have filled out all the fields above
  • I have provided relevant links or references (if applicable)
## 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 - [x] I have checked existing issues for duplicates - [x] I have filled out all the fields above - [x] I have provided relevant links or references (if applicable)

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?

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?
Member

Here is the current status.

Bodhi

Done.

$ bodhi releases info F42
End 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

Here is the current status. ### Bodhi Done. `$ bodhi releases info F42` End 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
Member

This should be done as part of the final release process, so I took the liberty of updating the SOP.

infra/docs#521

This should be done as part of the final release process, so I took the liberty of updating the SOP. https://forge.fedoraproject.org/infra/docs/pulls/521
Member

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

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
Sign in to join this conversation.
No milestone
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#13352 Fedora 42 EOL
releng/tickets
Reference
releng/tickets#13348
No description provided.