#117 Fix EOL date for F37 in https://fedorapeople.org/groups/schedule/f-37/f-37-all-milestones.json
Closed by siosm. Opened by siosm.

This is currently the only place where we can get the Fedora 37 EOL date from the schedule and it has not been updated following the latest F39 release delays.

See "EOL" in https://fedorapeople.org/groups/schedule/f-37/f-37-all-milestones.json

See: https://pagure.io/fedora-pgm/schedule/pull-request/116

Another option to fix this is to add a "Fedora Linux 37 end of life" key to https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html / https://fedorapeople.org/groups/schedule/f-37/f-37-key.json similarly to what's in https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html / https://fedorapeople.org/groups/schedule/f-38/f-38-key.json.

Thanks!


It hasn't been updated for the same reason as the other issue: the script does not generate the all milestones file any more.

I'm still confused why you want to get the date from the schedule. It is way way easier to get it from Bodhi. It's two lines of Python:

import requests
print(requests.get("https://bodhi.fedoraproject.org/releases/F37").json().get("eol"))

that's it. The date in Bodhi is available long before the release actually goes EOL - it currently provides EOL dates up to F39. If there's a reason you can't use Bodhi for this, I didn't see it yet.

We could update the key tasks, I'm just confused as to why you seem to be really wedded to the idea of getting this out of the schedule, when it's needlessly difficult.

Thanks,. I couldn't find anywhere in the docs how to do it.

I'm reworking https://src.fedoraproject.org/rpms/fedora-appstream-metadata to use Bodhi for EOL dates.

Thanks

Metadata Update from @siosm:
- Issue status updated to: Closed (was: Open)

Metadata