COVID-19 risk assessment

The primary concern of the Fedora leadership remains the health and safety of the Fedora community. However, we are tracking the risk to Fedora release deliverables as the situation evolves. This document is maintained by the Fedora Program Manager (Ben Cotton) with the Fedora Project Leader (Matthew Miller) as a backup.


Table 1. Project status
Project Status

Fedora 35

On track


  • 2021-06-14 - bcotton

    • F34 is in the past

  • 2021-02-17 - bcotton

    • Remove past events

    • Add Fedora 35 release since program managers are not supposed to be optimistic

  • 2020-10-26 - bcotton

    • Remove Fedora 33. We released it!

  • 2020-10-14 - bcotton

    • Remove datacenter move

    • Add Fedora 34 release since we probably want to keep this up into that cycle

  • 2020-06-17 - bcotton

    • The dc move is nearly complete, so reflect the reduced risk

  • 2020-06-17 - bcotton

    • Final hardware shipment is en route to IAD2

    • Upgrade F33 and move status to on track

  • 2020-05-18 - bcotton - Update with latest Datacenter move status

  • 2020-04-28 - bcotton

    • Fedora 32 is released, no need to track

    • Fedora 33 is now being tracked and is at risk because of the DC move

    • The DC move timeline has slipped

  • 2020-04-17 - bcotton - Change Datacenter move to green until such time as risks manifest

  • 2020-03-20 - bcotton - Initial version

Points of contact

Table 2. Points of contact
Area Name Email Location/time zone

Program Management

Ben Cotton

bcotton AT redhat DOT com

Indiana, US (Eastern)

Fedora Project Leader

Matthew Miller

mattdm AT redhat DOT com

Massachusetts, US (Eastern)


Kevin Fenzi

kfenzi AT redhat DOT com

Oregon, US (Pacific)

Release Engineering

Mohan Boddu

mboddu AT redhat DOT com

Massachusetts, US (Eastern)


Adam Williamson

awilliam AT redhat DOT com

British Columbia, CA (Pacific)

Fedora Linux 35 release

Key Dates:

  • 2021-07-01 - Mass rebuild begins

  • 2021-08-19 - Mass rebuild ends

  • 2021-09-14 - Beta Release early target

  • 2021-09-21 - Beta Release target

  • 2021-10-19 - Final Release early target

  • 2021-10-26 - Final Release target

Table 3. Fedora 35 risks
Risk area Impact Likelihood Mitigation & Notes

Release engineering staff



Release Engineering knowledge is duplicated across multiple people with large geographic separation

Infrastucture staff



Infrastructure knowledge is duplicated across multiple people with large geographic separation

QA test staff



Testing staff (both Red Hat and non-Red Hat contributors) are widely distributed across the globe

openQA test platform



Adam Williamson is the primary admin for openQA. However, other members of the team have knowledge and could keep the platform going if Adam is unavailable.

QA test hardware



Some QA tests require physical access to hardware located in Red Hat offices (see table below). Some of these can be done with contributor’s personally-owned hardware and others may be skipped if Red Hat offices remain closed through the release.

Test cases at risk

The table below represents test cases identified by the QA team which may be impacted by lack of access to Red Hat offices. Where “use contributor-owned hardware” is listed in the mitigation section, someone has volunteered to run those tests. For others, we will put out public calls for testing and may decide to exclude those tests for this release if office shutdown continues.

Table 4. Fedora 35 at-risk test cases
Test case Mitigation


Use contributor-owned hardware. May require a longer period between release candidate compose and go/no-go decision


Use contributor-owned hardware.





Use contributor-owned hardware.