When managing Linux systems, one of the most critical considerations is understanding your operating system’s support lifecycle. If you’re running Fedora Linux, staying ahead of EOL (End of Life) dates is essential due to its rapid release cycle and relatively short support windows.
Today, we’ll provide a comprehensive and systematic overview of Fedora Linux EOL schedules across all versions. This information is essential for system administrators and developers from a practical perspective.
1. What is Fedora Linux? At the Forefront of Rapidly Evolving Open Source
Fedora Linux is a community-driven Linux distribution sponsored by Red Hat. Since its inception in 2003 as the successor to Red Hat Linux, it has been renowned for adopting cutting-edge open source technologies faster than any other distribution. Fedora serves as the upstream source for Red Hat Enterprise Linux (RHEL), making it a platform where you can experience the future of enterprise Linux.
Currently, Fedora offers six editions:
- Fedora Workstation: Desktop environment for developers and general users
- Fedora Server: Server-focused edition
- Fedora CoreOS: Container-centric operating system
- Fedora Silverblue: Immutable desktop system
- Fedora IoT: Internet of Things devices
- Fedora KDE Desktop: KDE Plasma desktop environment (promoted to full Edition status starting with Fedora 42)
2. Fedora’s Unique Release Policy: Why So Fast?
Fedora maintains an aggressive six-month release cycle, driven by its philosophy of rapidly adopting new technologies. This results in relatively short support periods.
Core Support Policy:
- Each Fedora version receives approximately 13 months of support
- The exact formula: “X+2 version release plus 4 weeks”
- For example, Fedora 40 reaches EOL 4 weeks after Fedora 42’s release
This policy is documented in the Fedora Release Life Cycle official documentation.
3. Currently Supported Fedora Versions
As of September 2025, here are the currently supported Fedora versions:
| Version | Release Date | Expected EOL Date | Support Status |
|---|---|---|---|
| Fedora 42 | 2025-04-15 | Fall 2026 | ✅ Current Latest |
| Fedora 41 | 2024-10-29 | Spring 2026 | ✅ Supported |
Key Features of Fedora 42 “Adams”:
- KDE Plasma promoted to full Edition status
- New COSMIC desktop environment Spin
- X11 default support removed (complete Wayland transition)
- Python 3.8 support discontinued
- Official WSL (Windows Subsystem for Linux) images
Fedora 40 already reached EOL on May 13, 2025, so if you’re currently using it, please upgrade immediately.
4. Complete EOL Timeline for All Fedora Versions
4-1. EOL’d Fedora Versions (2020+)
| Version | Codename | Release Date | EOL Date | Support Duration |
|---|---|---|---|---|
| Fedora 40 | – | 2024-04-23 | 2025-05-13 | 385 days |
| Fedora 39 | – | 2023-11-07 | 2024-11-26 | 381 days |
| Fedora 38 | – | 2023-04-18 | 2024-05-21 | 399 days |
| Fedora 37 | – | 2022-11-15 | 2023-12-05 | 385 days |
| Fedora 36 | – | 2022-05-10 | 2023-05-16 | 371 days |
| Fedora 35 | – | 2021-11-02 | 2022-12-13 | 406 days |
| Fedora 34 | – | 2021-04-27 | 2022-06-07 | 399 days |
| Fedora 33 | – | 2020-10-27 | 2021-11-30 | 399 days |
| Fedora 32 | – | 2020-04-28 | 2021-05-25 | 392 days |
| Fedora 31 | – | 2019-10-29 | 2020-11-24 | 392 days |
| Fedora 30 | – | 2019-04-30 | 2020-05-26 | 393 days |
4-2. Historical Fedora Versions (2010s)
| Version | Codename | Release Date | EOL Date | Support Duration |
|---|---|---|---|---|
| Fedora 29 | – | 2018-10-30 | 2019-11-26 | 392 days |
| Fedora 28 | – | 2018-05-01 | 2019-05-28 | 393 days |
| Fedora 27 | – | 2017-11-14 | 2018-11-30 | 381 days |
| Fedora 26 | – | 2017-07-11 | 2018-05-29 | 333 days |
| Fedora 25 | – | 2016-11-22 | 2017-12-12 | 386 days |
| Fedora 24 | – | 2016-06-21 | 2017-08-08 | 413 days |
| Fedora 23 | – | 2015-11-03 | 2016-12-20 | 413 days |
| Fedora 22 | – | 2015-05-26 | 2016-07-19 | 420 days |
| Fedora 21 | – | 2014-12-09 | 2015-12-01 | 357 days |
| Fedora 20 | Heisenbug | 2013-12-17 | 2015-06-23 | 553 days |
| Fedora 19 | Schrödinger’s Cat | 2013-07-02 | 2015-01-06 | 553 days |
| Fedora 18 | Spherical Cow | 2013-01-15 | 2014-01-14 | 364 days |
| Fedora 17 | Beefy Miracle | 2012-05-29 | 2013-07-30 | 427 days |
| Fedora 16 | Verne | 2011-11-08 | 2013-02-12 | 462 days |
| Fedora 15 | Lovelock | 2011-05-24 | 2012-06-26 | 399 days |
| Fedora 14 | Laughlin | 2010-11-02 | 2011-12-09 | 402 days |
| Fedora 13 | Goddard | 2010-05-25 | 2011-06-24 | 395 days |
| Fedora 12 | Constantine | 2009-11-17 | 2010-12-02 | 380 days |
| Fedora 11 | Leonidas | 2009-06-09 | 2010-06-25 | 381 days |
4-3. Early Fedora Versions (2000s)
| Version | Codename | Release Date | EOL Date | Support Duration |
|---|---|---|---|---|
| Fedora 10 | Cambridge | 2008-11-25 | 2009-12-17 | 387 days |
| Fedora 9 | Sulphur | 2008-05-13 | 2009-07-10 | 423 days |
| Fedora 8 | Werewolf | 2007-11-08 | 2009-01-07 | 426 days |
| Fedora 7 | Moonshine | 2007-05-31 | 2008-06-13 | 379 days |
| Fedora Core 6 | Zod | 2006-10-24 | 2007-12-07 | 409 days |
| Fedora Core 5 | Bordeaux | 2006-03-20 | 2007-07-02 | 469 days |
| Fedora Core 4 | Stentz | 2005-06-13 | 2006-08-07 | 420 days |
| Fedora Core 3 | Heidelberg | 2004-11-08 | 2006-01-16 | 434 days |
| Fedora Core 2 | Tettnang | 2004-05-18 | 2005-04-11 | 328 days |
| Fedora Core 1 | Yarrow | 2003-11-06 | 2004-09-20 | 320 days |
The Fedora Core era used a different naming convention.
5. Fedora EOL Management Best Practices
5-1. Pre-Migration Checklist
When managing systems approaching EOL, follow this systematic approach:
Step 1: Check Current Version
cat /etc/fedora-release
# or
hostnamectl
Step 2: Verify Upgrade Compatibility
sudo dnf system-upgrade download --refresh --releasever=42
Step 3: Backup Critical Data
- Configuration files:
/etc/directory - User data:
/home/directory - Application databases
5-2. Upgrade vs Clean Installation
Upgrade Recommended For:
- Development or test environments
- Systems without complex configurations
- 1-2 version difference upgrades
Clean Installation Recommended For:
- Production server environments
- 3+ version major upgrades
- Systems with instability or persistent issues
6. Automated EOL Monitoring to Stay Ahead
Here are practical tips to ensure you don’t miss EOL schedules:
6-1. System Monitoring Setup
Automated checks via crontab:
# Weekly EOL status check every Monday at 9 AM
0 9 * * 1 /usr/local/bin/check-fedora-eol.sh
Simple check script example:
#!/bin/bash
CURRENT_VERSION=$(rpm -E %fedora)
EOL_DATE=$(curl -s https://endoflife.date/api/v1/products/fedora/$CURRENT_VERSION.json | jq -r '.eol')
echo "Current Fedora $CURRENT_VERSION, EOL scheduled: $EOL_DATE"
6-2. External Tools
- endoflife.date: iCal subscription available at https://endoflife.date/fedora
- Fedora Official Schedule: https://fedorapeople.org/groups/schedule/
- RSS Feeds: Subscribe to Fedora Project announcements
7. Fedora EOL Strategy for Enterprise Environments
Enterprise Fedora deployments require more systematic approaches.
7-1. Staging Environment Architecture
Development Environment → Staging Environment → Production Environment
↓ ↓ ↓
Latest Version Stable Version Verified Version
Recommended Version Management Strategy:
- Development: Latest or latest-1 version
- Staging: Latest-1 or latest-2 version
- Production: Latest-2 version (thoroughly tested)
7-2. Migration Planning
Begin migration preparation 6 months before EOL with this timeline:
| Timeline | Task |
|---|---|
| EOL -6 months | New version review and compatibility testing plan |
| EOL -4 months | Begin staging environment testing with new version |
| EOL -3 months | Complete application compatibility testing |
| EOL -2 months | Document migration procedures and establish backup plans |
| EOL -1 month | Execute production environment migration |
8. Managing EOL’d Fedora Systems (When Necessary)
Sometimes special circumstances require continuing with EOL’d Fedora versions. Here’s how to handle such situations.
8-1. Archive Repository Usage
EOL’d Fedora packages move to archive repositories:
# Modify /etc/yum.repos.d/fedora.repo
[fedora]
name=Fedora $releasever - $basearch
baseurl=https://archives.fedoraproject.org/pub/archive/fedora/linux/releases/$releasever/Everything/$basearch/os/
enabled=1
gpgcheck=1
⚠️ Critical Security Considerations:
- No security updates provided
- Firewall and network security hardening essential
- Upgrade as soon as possible
8-2. Containerization Considerations
For legacy applications, containerization can minimize risks:
FROM fedora:40
# Install necessary configurations and applications
RUN dnf install -y your-legacy-app
9. Key Points for Stable Fedora Operations
While Fedora Linux’s rapid innovation pace is certainly attractive, systematic EOL management is crucial.
Key Takeaways:
- 13-Month Support Principle: All Fedora versions receive approximately 13 months of support
- 6-Month Release Cycle: New versions are released approximately every 6 months
- Advance Planning Importance: Begin migration planning 6 months before EOL
- Testing Environment Usage: Thorough testing before production upgrades is essential
- Security Priority: Immediately upgrade EOL’d systems or implement appropriate security measures
To safely leverage Fedora’s innovative technologies, understanding and systematically managing these EOL schedules is key. Regularly check the Fedora official documentation for your system management needs.
Useful Related Links: