Changes/FedoraCoreOS

Make Fedora CoreOS a Fedora Edition

Summary

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

Owners

• Name: Clement Verna
• Email: cverna@fedoraproject.org
• Products: Fedora CoreOS
• Responsible WGs: Fedora CoreOS Group

Current status

• Targeted release: Fedora 35
• Last updated: 2021-02-12
• FESCo issue: #2516
• Tracker bug: <will be assigned by the Wrangler>
• Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

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

Prerequisites are tracked bellow :

• Edition has a team with regular public meeting : weekly meeting happening on #fedora-meeting-1

• Trademark approval from the Fedora Council : council ticket

• Product requirements document (PRD) : https://fedoraproject.org/wiki/CoreOS/PRD

• Technical specification : https://github.com/coreos/fedora-coreos-tracker/blob/master/Design.md

Benefit to Fedora

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

Scope

• Proposal owners: see change owners

• Other developers: N/A

• Release engineering: Fedora CoreOS is already being composed and released.

• Policies and guidelines: N/A

• Trademark approval: https://pagure.io/Fedora-Council/tickets/issue/340

Upgrade/compatibility impact

N/A

How To Test

See QA test cases : https://fedoraproject.org/wiki/Category:CoreOS_Test_Cases

We also have regular tests days, for example https://fedoramagazine.org/fedora-coreos-test-day/

Stream Release Criteria

The following are the proposed criteria that MUST be met for each stream to be promoted.

Supported Architecture and Platforms

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

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

Kola test suite

Details of the tests we run

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.

Contingency Plan

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

Contingency deadline: F34 Final release date

Blocks release? No

Documentation

https://docs.fedoraproject.org/en-US/fedora-coreos/