Bug 2105402
Summary: | [RFE] start using os-release SUPPORT_END=YYYY-MM-DD | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Pat Riehecky <riehecky> |
Component: | fedora-release | Assignee: | Mohan Boddu <mboddu> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | bcotton, fedoraproject, jkeating, kellin, kevin, mboddu, pbrobinson, sgallagh, thrcka, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | fedora-release-37-15 fedora-release-36-21 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-12-08 02:06:17 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Pat Riehecky
2022-07-08 17:48:17 UTC
Yeah. https://github.com/systemd/systemd/pull/23962 adds a notification in systemd itself. So there'll be a notification on the console during boot and a message in the logs. To make visible for users, we'd need to add some sort of a graphical notification. According to https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html: for F35: SUPPORT_END=2022-11-15 for F36: SUPPORT_END=2023-05-16 (I'm assuming that the on the specified date bugs are closed with EOL notifications, i.e. we can treat F35 stops being supported when day 2022-11-15 starts.) Since Fedora 37 is nearly out the door, I'd love to see this in os-release for Fedora 38. (In reply to Zbigniew Jędrzejewski-Szmek from comment #1) > (I'm assuming that the on the specified date bugs are closed with EOL > notifications, > i.e. we can treat F35 stops being supported when day 2022-11-15 starts.) I generally start the EOL closures early in my work day because it can take a while to churn through them all. Strictly speaking, EOL is a little fuzzy because of that. But for practical purposes, I think we can consider 0000 UTC on the EOL date to be the end. (In reply to Pat Riehecky from comment #2) > Since Fedora 37 is nearly out the door, I'd love to see this in os-release > for Fedora 38. Zbigniew, is this something we could drop in mid-cycle (I ask you with both your systemd and FESCo hats on)? I don't see a reason why we couldn't, but you have a better sense than I do here. > is this something we could drop in mid-cycle (I ask you with both your systemd and FESCo hats on)?
I think we wouldn't want to add, for example, a graphical notification mechanism, during the
the cycle, but I think it's totally fine to the metadata during the cycle. On its own,
the metadata does not "do" anything. It might also make it easier to support older
images in the future if this catches on.
Is there a way I can help get this over the line? Pat, I plan on submitting PRs for fedora-release later this week. If you beat me to it, I won't complain. https://src.fedoraproject.org/rpms/fedora-release/pull-request/233 adds support in Rawhide (for F38). If the general idea is valid, we can backport it to other supported versions (although F35–37 doesn't have a systemd version that explicitly supports it, so the utility may be minimal) Rawhide package updated: https://bodhi.fedoraproject.org/updates/FEDORA-2022-349d66504a F35–37 PRs pending: 35: https://src.fedoraproject.org/rpms/fedora-release/pull-request/236 36: https://src.fedoraproject.org/rpms/fedora-release/pull-request/235 37: https://src.fedoraproject.org/rpms/fedora-release/pull-request/234 FEDORA-2022-e7ac664b5b has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-e7ac664b5b FEDORA-2022-01f4c53e2c has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-01f4c53e2c FEDORA-2022-0a4e0d91f1 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0a4e0d91f1 FEDORA-2022-e7ac664b5b has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-e7ac664b5b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-e7ac664b5b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-01f4c53e2c has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-01f4c53e2c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-01f4c53e2c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-0a4e0d91f1 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-0a4e0d91f1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-0a4e0d91f1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-e7ac664b5b has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-0a4e0d91f1 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. |