From Fedora Project Wiki
m (Add trackers)
 
(25 intermediate revisions by 4 users not shown)
Line 3: Line 3:
== Summary ==
== Summary ==


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


== Owners ==
== Owners ==
Line 16: Line 17:
== Current status ==
== Current status ==
[[Category:SystemWideChange]]
[[Category:SystemWideChange]]
[[Category:ChangeAcceptedF37]]


* Targeted release: [[Releases/34 | Fedora 34 ]]  
* Targeted release: [[Releases/37 | Fedora 37 ]]  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
Line 26: Line 28:
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
-->
-->
* FESCo issue:  
* [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/OSHZEHWTYSACVKJEPLVL2EVJ3GDY3AE2/ Devel list thread]
* Tracker bug:  
* FESCo issue: [https://pagure.io/fesco/issue/2823 #2823]
* Release notes tracker:  
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2106823 #2106823]
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/856 #856]


== Detailed Description ==
== Detailed Description ==


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


Prerequisites are tracked bellow :
[https://fedoraproject.org/wiki/Editions/Promotion_Process#Prerequisites Prerequisites] are tracked bellow :


* Edition has a team with regular public meeting : [https://apps.fedoraproject.org/calendar/meeting/9437/ weekly meeting happening on #fedora-meeting-1]  
* Edition has a team with regular public meeting : [https://apps.fedoraproject.org/calendar/meeting/9437/ weekly meeting happening on #fedora-meeting-1]  
Line 45: Line 48:


== Feedback ==
== Feedback ==
This change was previously submitted for Fedora 34 and feedback were collected in the following [https://pagure.io/fesco/issue/2516 FESCo ticket].
The 2 main feedback received are either addressed or in the process of being addressed.
* FCOS should not trail behind the latest Major Fedora version: see [[https://fedoraproject.org/wiki/Changes/FedoraCoreOS#Major_Fedora_Version_release_Go/NoGo|Major Fedora Version release Go/NoGo criteria]]
* FCOS should demonstrate the test case mapping to the Basic Release Criteria: see [[https://fedoraproject.org/wiki/Changes/FedoraCoreOS#Basic_Release_Criteria|Basic Release Criteria]]


== Benefit to Fedora ==
== Benefit to Fedora ==


Make Fedora CoreOS an official edition, will help spread adoption and position Fedora as credible solution for running container workflow.
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 [https://discussion.fedoraproject.org/t/fedora-coreos-survey/34408/2 a community survey]. Part of these monthly update are [https://discussion.fedoraproject.org/t/this-month-in-fedora-coreos-may-2022/39942#fcos-count-me-stats-3 the count me stats] which gives us a good understanding of FCOS adoption.


== Scope ==
== Scope ==
Line 62: Line 74:


== Upgrade/compatibility impact ==
== Upgrade/compatibility impact ==
N/A


== How To Test ==
== How To Test ==
See QA test cases : https://fedoraproject.org/wiki/Category:CoreOS_Test_Cases
See QA test cases : https://fedoraproject.org/wiki/Category:CoreOS_Test_Cases and Fedora CoreOS own test suite Kola https://github.com/coreos/coreos-assembler/blob/main/docs/kola.md#testing-with-kola
 
We also have regular tests days, for example https://fedoramagazine.org/fedora-coreos-test-day/
 
=== Basic Release Criteria ===
 
We are currently evaluating our compliance to the Fedora Basic Release Criteria https://github.com/coreos/fedora-coreos-tracker/issues/1239.
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 [https://docs.fedoraproject.org/en-US/fedora-coreos/platforms/#_well_known_ids platforms] are supported and can be configured directly using Ignition.
 
The [https://github.com/coreos/mantle/tree/cl/kola 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 ([https://github.com/coreos/fedora-coreos-streams/issues/242 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 [https://github.com/coreos/fedora-coreos-tracker issue tracker] and discussed during the weekly [https://github.com/coreos/fedora-coreos-tracker#meetings 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 https://github.com/coreos/fedora-coreos-tracker/blob/main/Design.md#major-fedora-version-rebases (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 ==
== User Experience ==
Line 73: Line 127:


== Dependencies ==
== Dependencies ==
Contingency mechanism: (What to do? Who will do it?) Delay promotion until F35
Contingency deadline: F34 Final release date
Blocks release? No


== Contingency Plan ==
== Contingency Plan ==
Contingency mechanism: (What to do? Who will do it?) Delay promotion until F38
Contingency deadline: F37 Final release date
Blocks release? No


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


== Release Notes ==
== Release Notes ==

Latest revision as of 15:25, 13 July 2022

Make Fedora CoreOS a Fedora Edition

Summary

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

Owners

  • Name: Clement Verna
  • Email: cverna@fedoraproject.org
  • 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 :

Feedback

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.

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

Upgrade/compatibility impact

N/A

How To Test

See QA test cases : https://fedoraproject.org/wiki/Category:CoreOS_Test_Cases and Fedora CoreOS own test suite Kola https://github.com/coreos/coreos-assembler/blob/main/docs/kola.md#testing-with-kola

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

Basic Release Criteria

We are currently evaluating our compliance to the Fedora Basic Release Criteria https://github.com/coreos/fedora-coreos-tracker/issues/1239. 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 https://github.com/coreos/fedora-coreos-tracker/blob/main/Design.md#major-fedora-version-rebases (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

Pros

Enhancement opportunities

Dependencies

Contingency Plan

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

Contingency deadline: F37 Final release date

Blocks release? No

Documentation

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

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/FedoraCoreOS&oldid=649446"