Wiki - https://fedoraproject.org/wiki/Changes/CoreOSStopPublishingOSTree Discussion thread - https://discussion.fedoraproject.org/t/f43-change-proposal-stop-publishing-updates-to-ostree-repository-for-coreos-self-contained/148878
This is a proposed Change for Fedora Linux. This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee. == Summary == Stop publishing new updates for Fedora CoreOS to the cannonical OStree repository at ostree.fedoraproject.org. Instead, rely on OCI Images from the fedora quay.io repository. == Owners == * Name: [[User:jbtrystram| Jean-Baptiste Trystram]] <jbtryst...@redhat.com> * Name: [[User:Dustymabe| Dusty Mabe]] <dm...@redhat.com> == Detailed Description == With the rebase to Fedora 42 for Fedora CoreOS, we changed the source of updates from the OSTree repository to OCI containers from quay.io/fedora/fedora-coreos. During the Fedora 42 release cycle, we will migrate existing Fedora CoreOS nodes to use OCI images as well. See https://fedoraproject.org/wiki/Changes/CoreOSOstree2OCIUpdates for more details As a continuation of that change, we will stop publishing updates to the CoreOS branches built on Fedora 43 content in the OSTree repository as they will no longer be used. == Feedback == None yet. == Benefit to Fedora == This will reduce releases workload and use less resources from Fedora Infrastructure. == Scope == * Proposal owners: ** Will update Fedora CoreOS release pipeline to stop publishing data to the OSTree repository. ** Will update relevant documentation in Fedora CoreOS docs. * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) * Alignment with the Fedora Strategy: This align with the bootable containers initiative. == Upgrade/compatibility impact == <!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --> == How To Test == New images of Fedora CoreOS next are already set to be deployed from containers since the rebase to Fedora 42. You can start a 42.20250316.1.0 image and watch it update from quay.io instead of the usual OSTree repository. == User Experience == Users who have not opted out of the OCI migration in Fedora 42 will experience no change. Users who have opted out of the OCI migration and are still using the OSTree repo for updates will need to migrate to OCI to continue to receive updates for Fedora 43+. == Contingency Plan == Keep releasing to the OSTree repository. == Documentation == To be written. Tracked in: https://github.com/coreos/fedora-coreos-tracker/issues/1895 == Release Notes == To be written. Tracked in: https://github.com/coreos/fedora-coreos-tracker/issues/1895 -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- _______________________________________________ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
