In _Fedora Workstation_, when the next stable release is available, a graphical notification will appear similar to the update notifications.
Clicking this, or running the **Software** application and going to the **Updates** pane, will display a simple graphical interface for upgrading the system.
**Important:** Before you start upgrading, your system needs to be fully up-to-date, to ensure
Upgrading between major versions (such as from Fedora 32 to Fedora 33) can be completed using the Software application. Alternatively, Silverblue can be upgraded between major versions using the `ostree` command..
For instructions on upgrading Fedora Silverblue Host, refer to the link:++https://docs.fedoraproject.org/en-US/fedora-silverblue/updates-upgrades-rollbacks/#upgrading++[dedicated page].
Upgrading between Fedora releases without the xref:dnf-system-upgrade.adoc[DNF System Upgrade plugin] or <<sect-upgrading-to-the-next-fedora-workstation-release,GNOME Software>> are not tested by the Fedora QA team, and are therefore not supported by the community. You can follow xref:upgrading-fedora-online.adoc[Upgrading Fedora using package manager], but you're doing that *at your own risk*.
If you are using a pre-release of Fedora, you shouldn't need to do anything to get the final public release, other than updating packages as they become available. You can use `sudo dnf update` or wait for desktop notification. When the pre-release is released as final, the `fedora-repos` packages will be updated and your `updates-testing` repository will be disabled. Once this happens (on the release day), it is highly recommended to run `sudo dnf distro-sync` in order to align package versions with the current release.
link:++https://fedoraproject.org/wiki/Releases/Rawhide++[Rawhide] and link:++https://fedoraproject.org/wiki/Releases/Branched++[Branched] are the development releases of Fedora.
They are suitable for users developing or testing Fedora before public release.
They are *NOT SUITABLE* for regular day-to-day use unless you are a fairly experienced user, and certainly not suitable for mission-critical use.
You should read through those pages carefully before deciding to run Branched or Rawhide.
See the link:++https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle++[Fedora Life Cycle] for more information on how the whole Fedora cycle works from Rawhide, to Branched, to the milestone releases (Beta), to the 'Final' release.
With that in mind, if you do have an end-of-life release installed on a system you cannot just discard or re-deploy, you upgrade using xref:dnf-system-upgrade.adoc[DNF System Upgrade].
Note that upgrades are only tested from the two previous releases.
Fedora releases up to Fedora 17 included upgrade functionality in the Fedora installer, anaconda.
This can be a better choice than a package manager upgrade for some End Of Life (EOL) upgrades.
If you are attempting to upgrade from Fedora 16 or older, it is highly recommended to upgrade to Fedora 16 and perform an installer upgrade from Fedora 16 to Fedora 17 before upgrading any further.
To upgrade using the installer, boot the system from a network install or DVD image for the target release, and run through the initial steps of the install process.
After you select storage devices the installer should offer you the option to upgrade the installed system.
[IMPORTANT]
====
If your installation is located on a 'specialized' storage device, be sure to configure and select it.
