Upgrading

In other languages: English (en) español (es) italiano (it) русский (ru) 中文（中国大陆） (zh-cn) Ελληνικά (el) [edit]

Upgrading Fedora Products

This section has some notes on upgrading to Fedora products. Fedora 21 introduced three new products: Workstation, Server and Cloud. If you are unfamiliar with them, you may wish to refer to Fedora.next first.

Do I need to specify or worry about products when upgrading from Fedora 21 or newer?

No, you don't need to specify a product for upgrades of Fedora 21 or later. Since the products were introduced in Fedora 21, all Fedora 21+ installs have a product identifier (even if that's 'nonproduct'). You only need to specify this when upgrading from a release older than Fedora 21 (which is no longer supported).

Upgrading with DNF system upgrade plugin

Recommended Upgrade Method
This is the recommended method for Fedora upgrades.

For instructions on upgrading with the DNF system upgrade plugin, refer to the dedicated page.

Upgrading directly using yum or DNF

Not a recommended upgrade method
This is NOT an officially recommended method for Fedora upgrades.

Upgrading directly from one release to the next using dnf (or yum for releases before Fedora 22) is not explicitly tested by Fedora QA and issues with it are not considered blockers for a release, but in practice it works for many users, probably due to our packaging guidelines providing detailed information on maintaining upgradability. To learn more, refer to Upgrading Fedora using dnf or yum.

Upgrading from a pre-release (Alpha, Beta, or other development snapshot) to the final release

If you are using a pre-release of Fedora, and want to know more about upgrading to the final release, refer to Upgrading from pre-release to final.

Tips

• Ensure you have a good backup of your data.

• Ensure you read the Release Notes carefully before attempting an upgrade.

Rawhide

Rawhide is a development version of Fedora that is updated daily. It is suitable for people who are developing or testing Fedora before broad public release.

Rawhide is not for casual use!
Packages in rawhide aren't inherently unstable, but interactions and dependencies between packages there can be unpredictable. The testing performed in release branches to prevent these conflicts isn't there in rawhide - or, more correctly, it happens in rawhide so that the release branches can benefit. Do not use Rawhide just for newer versions of a package; use it when you are an experienced user that wants to actively contribute to a stable rawhide.

• To move from Rawhide to a stable release, refer to Upgrading from pre-release to final.
• To move from a stable release to Rawhide, refer to Releases/Rawhide.