From Fedora Project Wiki

Make Fedora CoreOS a Fedora Edition


This change is to promote Fedora CoreOS to Edition status alongside Cloud, IoT, Server and Workstation.


  • Name: Clement Verna
  • Email:
  • Products: Fedora CoreOS
  • Responsible WGs: Fedora CoreOS Group

Current status

Detailed Description

This change is to promote Fedora CoreOS to Edition status alongside Cloud, IoT, Server and Workstation.

Prerequisites are tracked bellow :


This change was previously submitted for Fedora 34 and feedback were collected in the following FESCo ticket. The 2 main feedback received are either addressed or in the process of being addressed.

  • FCOS should demonstrate the test case mapping to the Basic Release Criteria: see [Release Criteria]

Benefit to Fedora

Make Fedora CoreOS an official edition, will help spread adoption and position Fedora as credible solution for running container workflow.

We have started to publish monthly update of what is happening in Fedora CoreOS based on the feedback received from a community survey. Part of these monthly update are the count me stats which gives us a good understanding of FCOS adoption.


  • Proposal owners: see change owners
  • Other developers: N/A
  • Release engineering: Fedora CoreOS is already being composed and released.
  • Policies and guidelines: N/A

Upgrade/compatibility impact


How To Test

See QA test cases : and Fedora CoreOS own test suite Kola

We also have regular tests days, for example

Basic Release Criteria

We are currently evaluating our compliance to the Fedora Basic Release Criteria This is an effort that will be done during the Fedora 37 development cycle.

Supported Architecture and Platforms

Fedora CoreOS is currently built for the x86_64, aarch64 and s390x architecture, These platforms are supported and can be configured directly using Ignition.

The kola test suite is run for each stream release on AWS, Azure, GCP and OpenStack.

Stream release Go/NoGo

Stream releases are scheduled fortnightly, a GitHub issue (example) is created for each stream release with the release process. The release status can be tracked in each ticket. If each steps and validation were successful the release is considered GO.

Issues are reported in the issue tracker and discussed during the weekly IRC meeting. A stream release can become a NOGO during these meeting, the blocker issue is then linked to the release GitHub issue.

Major Fedora Version release Go/NoGo

The policies around the Major version rebases are described in Fedora CoreOS document (see copy below)

The release process integrates with Fedora's release milestones in the following ways:

Fedora Beta Release

 The next stream is switched over to the new release.

Fedora Final Freeze

 The next stream switches to weekly releases to closely track the GA content set.

Fedora General Availability Fedora CoreOS re-orients its release schedule in the following way:

 Week -1 (Fedora "Go" Decision): next release:
    next release with final Fedora GA content
 Week 0 (GA release): triple release:
    testing release promoted from previous next
    next release contains latest Fedora N content, including Bodhi updates
 Week 2: triple release:
    stable release promoted from previous testing, now fully rebased to Fedora N
    testing and next are now in sync

User Experience


Enhancement opportunities


Contingency Plan

Contingency mechanism: (What to do? Who will do it?) Delay promotion until F38

Contingency deadline: F37 Final release date

Blocks release? No


Release Notes