Fedora (RHEL Upstream)

Fedora is a community Linux distribution sponsored by Red Hat and the upstream source for RHEL. Every RHEL major version is built upon a specific Fedora release. Understanding the relationship between Fedora and RHEL helps you grasp the trajectory of Enterprise Linux technology development.

Fedora and RHEL Relationship

Fedora → CentOS Stream → RHEL → AlmaLinux / Rocky Linux / ...

Fedora’s role in the EL ecosystem is as the frontier innovation lab. Red Hat engineers introduce and test new technologies in Fedora, and after community validation, mature components are selected for the next RHEL major version.

Version Mapping

RHEL Version	Based on Fedora	Release Year
RHEL 7	Fedora 19/20	2014
RHEL 8	Fedora 28	2019
RHEL 9	Fedora 34	2022
RHEL 10	Fedora 40	2025

This means when you use Fedora 40, you are getting an early preview of the technology foundation for RHEL 10.

The Fedora to RHEL Pipeline

1. Technology debuts in Fedora: New kernel versions, system components, default configurations
2. Community validation: Fedora’s large user base helps discover issues
3. Enters CentOS Stream: Mature technologies enter CentOS Stream for further integration testing
4. RHEL GA release: After comprehensive QA, released as a RHEL major version

Fedora Editions

Fedora offers multiple editions targeting different use cases.

Fedora Workstation

The flagship edition for desktop users and developers:

• GNOME desktop environment (usually the latest stable release)
• Pre-installed development tools
• PipeWire audio system
• Wayland display protocol
• Flatpak application support

Best for: Linux desktop users, developer workstations

Fedora Server

The edition for servers and infrastructure:

• Minimal installation
• Cockpit web management interface
• Modular package management
• Server Roles management

Best for: Test and development servers, lab environments

Fedora IoT

The edition for Internet of Things and edge computing:

• OSTree-based immutable system
• Automatic updates (rpm-ostree)
• Container-first workload model
• Supports ARM and x86 devices

Fedora CoreOS

A minimal operating system for containerized workloads:

• Automatic updates
• Declarative deployment via Ignition configuration
• Designed specifically for running containers
• Ideal OS for Kubernetes nodes

# Fedora CoreOS is configured via Ignition
# It does not use the traditional Anaconda installer
# Instead, it uses declarative configuration files for deployment

Fedora Spins

Fedora also offers variants with different desktop environments pre-installed:

• KDE Plasma
• Xfce
• LXQt
• MATE-Compiz
• Cinnamon
• i3 / Sway (tiling window managers)
• Budgie

Release Cycle

Fedora follows an approximately 6-month release cycle:

• One release each spring and fall
• Each version is maintained for approximately 13 months (about 1 month after the next version releases)
• Version numbers increment sequentially (Fedora 39, 40, 41, 42…)

Comparison with EL Release Cycle

Feature	Fedora	RHEL
Release cycle	~6 months	~3 years (major)
Support cycle	~13 months	~10 years
Kernel version	Tracks upstream	Frozen + backports
Package versions	Latest stable	Version-locked
Positioning	Cutting-edge innovation	Enterprise stability

Package Characteristics

Cutting-Edge Software Versions

Fedora typically ships the latest stable versions of software:

# Fedora's software versions are usually much newer than RHEL
# For example, Fedora 41:
# GCC 14.x    (RHEL 9: GCC 11.x)
# Python 3.13 (RHEL 9: Python 3.9)
# kernel 6.x  (RHEL 9: kernel 5.14)
# GNOME 47    (RHEL 9: GNOME 40)

“First” Policy

Fedora follows a “First” policy — being among the first major distributions to adopt new technologies:

• First mainstream distro to default to systemd
• First mainstream distro to default to Wayland
• First mainstream distro to default to PipeWire
• First mainstream desktop distro to default to Btrfs

These “first-mover” technologies, once validated in Fedora, are often adopted by RHEL and other distributions.

DNF 5

Fedora was the first to adopt the DNF 5 package manager in its newer releases:

# Package management on Fedora
dnf install <package>
dnf update
dnf search <keyword>
dnf remove <package>

# DNF 5 improvements over DNF 4:
# - Significantly improved performance
# - Core rewritten in C++
# - Better transaction handling

Fedora and EPEL

What is EPEL

EPEL (Extra Packages for Enterprise Linux) is an additional software repository provided by the Fedora project for RHEL and its compatible distributions.

Packages in EPEL originate from Fedora but are adjusted to compile and run on EL systems:

# Install EPEL on RHEL/AlmaLinux/Rocky Linux
dnf install -y epel-release

# EPEL provides many packages not in official RHEL repositories
# Examples: htop, neofetch, nginx (newer versions), nodejs, etc.

Why EPEL Matters

For EL users, EPEL is an almost essential third-party repository:

• Provides thousands of additional packages
• Maintained by the Fedora community with quality assurance
• Does not conflict with official RHEL repositories
• Follows RHEL compatibility guidelines

When to Use Fedora vs EL

Choose Fedora For

• Daily desktop use: Latest desktop environments and applications
• Developer workstations: Latest development tools and language runtimes
• Technology enthusiasts: Want to experience the newest Linux technologies
• Fedora as RHEL preview: Understand the technology direction of the next RHEL
• Short-lifecycle environments: Test systems that do not need long-term maintenance

Choose EL For

• Production servers: Need long-term stability and support
• Enterprise applications: Running certified commercial software
• Compliance requirements: Security certifications and auditing
• Long-term operations: Prefer not to upgrade the OS frequently
• Consistency: Maintaining uniform versions across large-scale deployments

Hybrid Strategy

Many teams adopt a hybrid approach:

Developer workstations: Fedora Workstation (latest tools)
CI/CD environment:      CentOS Stream (pre-test compatibility)
Production servers:     RHEL / AlmaLinux / Rocky Linux (long-term stable)

Installation and Experience

Getting Fedora

Download: fedoraproject.org

Quick Experience

# Quick Fedora experience using Podman (on an EL system)
podman run -it fedora:latest bash

# Or use toolbox (Fedora's containerized development tool)
toolbox create --distro fedora --release 41
toolbox enter fedora-toolbox-41

Package Management on Fedora

# Update the system
sudo dnf update -y

# Install development tools
sudo dnf groupinstall -y "Development Tools"

# Install specific software versions
sudo dnf install -y python3.13 nodejs22

# System upgrade (across versions)
sudo dnf system-upgrade download --releasever=42
sudo dnf system-upgrade reboot

Fedora Community

Fedora has a large and active community:

• Fedora Discussion: discussion.fedoraproject.org
• Bugzilla: bugzilla.redhat.com
• Wiki: fedoraproject.org/wiki
• IRC/Matrix: Fedora chat channels

Fedora Change Proposals

All major changes in Fedora go through a public Change Proposal process:

• Proposers submit change descriptions
• FESCo (Fedora Engineering Steering Committee) reviews
• Community discussion
• Vote on inclusion

This transparent process makes Fedora’s technical evolution predictable — by watching Fedora Changes, you can broadly foresee RHEL’s technical direction for the coming years.

Summary

Fedora is an indispensable part of understanding RHEL and the entire EL ecosystem. It is not only the technical headwater for RHEL but also one of the most influential innovation platforms in the Linux world. As an EL user, following Fedora’s development is following the future of your operating system.