This page includes information on upgrading Rawhide, or a Fedora pre-release (Alpha, Beta, or Preview) of the next release of Fedora, to the final release.

+

{{autolang|base=yes}}

−

== Can I update the {{FedoraVersion|long|next}} Alpha/Beta/Snap#/Preview release to the '''final''' {{FedoraVersion|long|next}} release? ==

+

Starting with Fedora 13, installing an Alpha or Beta milestone puts you on the [[Releases/Branched|Branched]] release path.There may be some differences from a fresh install because the installer can do certain things slightly differently than the package update system.

−

Yes. Shortly before {{FedoraVersion|short|next}} is finally [[Releases/{{FedoraVersion||next}}/Schedule|released]], at 10am EST, there will be an updated <code>fedora-release</code> package which will change your release name from Rawhide to the general release {{FedoraVersion|full|next}}, and more importantly, change your package repositories from rawhide to the general release repositories automatically. A layman's version of the specific details [http://ivazquez.fedorapeople.org/files/RawhideSlipstream.pdf is available].

+

If you have installed [[Releases/Rawhide|Rawhide]], you would actually need to ''downgrade'' to get the final release, which is not recommended. (It might be easier to wipe the system and install from scratch.)

−

{{admon/important|Rawhide detritus|While upgrading from rawhide to final usually works without issue, some corner case issues may exist where bad interim rawhide updates leave the system in a different state than a final clean install, or even a regular {{FedoraVersion|short}} to {{FedoraVersion|short|next}} upgrade (or preupgrade). The likelihood of such issues generally decreases as the general release approaches and stabilization efforts increase.}}

+

Alternatively, you can switch to the Branched pre-Alpha release immediately after it becomes available. See [[Releases/Branched#Yum_update_from_previous_official_release]] for how to do this using yum.

−

{{admon/caution|<code>fedora-release</code> changes back to Rawhide a few weeks after release|If you delay updating too long after {{FedoraVersion|short|next}} is released, you may miss the final {{FedoraVersion|short|next}} <code>fedora-release</code> transition package, and instead of going from Rawhide to {{FedoraVersion|full|next}}, you will remain on Rawhide.}}

+

+

== Performing the upgrade ==

+

+

You shouldn't need to do anything to get the final public release, other than install package updates as they become available. You can use "yum update" or wait for desktop notification.

== After updating to '''final''', I see the new '''fedora''' and '''updates''' repos, but why is my '''rawhide''' repo also still enabled? ==

== After updating to '''final''', I see the new '''fedora''' and '''updates''' repos, but why is my '''rawhide''' repo also still enabled? ==

−

This will happen if you have manually modified your {{filename|/etc/yum.repos.d/fedora-rawhide.repo}} file before updating {{package|fedora-release}}. For example, if you have switched from using <code>mirrorlist=</code> to <code>baseurl=</code> for a repository definition, this situation occurs. Once {{package|fedora-release}} is updated, rather than overwrite your configuration changes, the new Rawhide repository file is created as {{filename|fedora-rawhide.repo.rpmnew}}. To disable Rawhide, either toggle <code>enabled=0</code> in your modified configuration, or, more simply, do:

+

This will happen if you have manually modified your {{filename|/etc/yum.repos.d/fedora-rawhide.repo}} file before updating {{package|fedora-release}}. For example, if you have switched from using <code>mirrorlist=</code> to <code>baseurl=</code> for a repository definition, this situation occurs. Once {{package|fedora-release}} is updated, rather than overwrite your configuration changes, the new Rawhide repository file is created as {{filename|fedora-rawhide.repo.rpmnew}}. To disable Rawhide, either toggle <code>enabled=0</code> in your modified configuration, select the '''Software Sources''' application from ''System > Administration > Software Sources'' on the menu, or run this command:

== After updating to '''final''', why does yum complain about mismatched package versions even though my '''rawhide''' repo is disabled? ==

+

+

This can happen if your '''rawhide''' repository was enabled at any time you ran a branched release. It can also happen if you install an Alpha or Beta pre-release and later upgrade to the final release. Packages in the '''rawhide''' and '''updates-testing''' repositories may not make it into the '''fedora''' or '''updates''' repositories, leaving your system stranded with newer versions than those that are in the final release.

+

+

To fix this, run this command to bring your system into sync with the final release:

+

<pre>su -c 'yum distro-sync'</pre>

== I found a {{FedoraVersion|long|next}} ISO leak before release day! Is it legit or is it exploited? ==

== I found a {{FedoraVersion|long|next}} ISO leak before release day! Is it legit or is it exploited? ==

−

The only way to know for sure is to [http://fedoraproject.org/en/verify verify] the leaked SHA1SUM's GPG signature (if available) with the official [https://fedoraproject.org/static/fedora.gpg Fedora GPG key]. If you can't, or won't do this, it's safer to just be patient and wait for release day. Also note that even if the early leak does check out, it might not be the FINAL release. Fedora has in the past had to re-push last-minute changes to the official releases.

+

The only way to know for sure is to [http://fedoraproject.org/en/verify verify] the leaked SHA256SUM CHECKSUM file's GPG signature (if available) with the official [https://fedoraproject.org/static/fedora.gpg Fedora GPG key]. If you can't, or won't do this, it's safer to just be patient and wait for release day. Also note that even if the early leak does check out, it might not be the FINAL release. Fedora has in the past had to re-push last-minute changes to the official releases.

== If I report my problem to fedora-test list or post in fedora forum, will my issues reach the developers? ==

== If I report my problem to fedora-test list or post in fedora forum, will my issues reach the developers? ==

Line 27:

Line 37:

== What are the new features in Fedora {{FedoraVersion||next}}? ==

== What are the new features in Fedora {{FedoraVersion||next}}? ==

−

The [http://fedoraproject.org/wiki/Fedora_11_FAQ Fedora 11 FAQ] and [[Releases/{{FedoraVersion||next}}/FeatureList|Fedora {{FedoraVersion||next}} feature list]] has more details.

+

The [[Releases/{{FedoraVersion||next}}/FeatureList|Fedora {{FedoraVersion||next}} feature list]] and [[Fedora_{{FedoraVersion||next}}_announcement]] have more details.

−

<!-- It makes no sense to have more links here. The rest of the page has been carefully edited to allow it to move along with the Fedora release numbers, and these links will be wrong as soon as the wiki moves to the next iteration of release numbers. -->

== Where can I get support for {{FedoraVersion||next}} pre-releases? ==

== Where can I get support for {{FedoraVersion||next}} pre-releases? ==

−

For IRC Support, please use the #fedora-qa channel instead of the main #fedora channel. The [http://fedoraforum.org FedoraForum site] has a dedicated forum for Alpha, Beta, and Preview pre-releases; please use that forum instead of the main forum. For email list discussions, please use the [https://www.redhat.com/mailman/listinfo/fedora-test-list fedora-test-list].

+

For IRC Support, please use the #fedora-qa channel instead of the main #fedora channel. The [http://fedoraforum.org FedoraForum site] has a dedicated forum for Alpha and Beta pre-releases; please use that forum instead of the main forum. For email list discussions, please use the [https://lists.fedoraproject.org/mailman/listinfo/test fedora-test-list].

+

[[Category:How to]]

[[Category:How to]]

Revision as of 05:59, 20 August 2011

Starting with Fedora 13, installing an Alpha or Beta milestone puts you on the Branched release path.There may be some differences from a fresh install because the installer can do certain things slightly differently than the package update system.

If you have installed Rawhide, you would actually need to downgrade to get the final release, which is not recommended. (It might be easier to wipe the system and install from scratch.)

Performing the upgrade

You shouldn't need to do anything to get the final public release, other than install package updates as they become available. You can use "yum update" or wait for desktop notification.

After updating to final, I see the new fedora and updates repos, but why is my rawhide repo also still enabled?

This will happen if you have manually modified your /etc/yum.repos.d/fedora-rawhide.repo file before updating fedora-release. For example, if you have switched from using mirrorlist= to baseurl= for a repository definition, this situation occurs. Once fedora-release is updated, rather than overwrite your configuration changes, the new Rawhide repository file is created as fedora-rawhide.repo.rpmnew. To disable Rawhide, either toggle enabled=0 in your modified configuration, select the Software Sources application from System > Administration > Software Sources on the menu, or run this command:

After updating to final, why does yum complain about mismatched package versions even though my rawhide repo is disabled?

This can happen if your rawhide repository was enabled at any time you ran a branched release. It can also happen if you install an Alpha or Beta pre-release and later upgrade to the final release. Packages in the rawhide and updates-testing repositories may not make it into the fedora or updates repositories, leaving your system stranded with newer versions than those that are in the final release.

To fix this, run this command to bring your system into sync with the final release:

su -c 'yum distro-sync'

I found a Fedora 28 ISO leak before release day! Is it legit or is it exploited?

The only way to know for sure is to verify the leaked SHA256SUM CHECKSUM file's GPG signature (if available) with the official Fedora GPG key. If you can't, or won't do this, it's safer to just be patient and wait for release day. Also note that even if the early leak does check out, it might not be the FINAL release. Fedora has in the past had to re-push last-minute changes to the official releases.

If I report my problem to fedora-test list or post in fedora forum, will my issues reach the developers?

You can use such avenues for discussions however for maximum efficiency, we always recommend that all actual bugs be reported to the Fedora bug tracker (Bugzilla) against the appropriate package in rawhide. This is the only assured way of reaching the right developers.

When is Fedora 28 going to be released?

What are the new features in Fedora 28?

Should I upgrade to Fedora 28?

We offer you the choice of the greatest and latest release. Per the Fedora lifecyle policy, each release of Fedora is maintained until a month after the second following release. For example, Fedora 26 will stop getting updates a month after Fedora 28 release. We highly recommend that users of unmaintained, "end-of-life" (EOL) releases upgrade to a newer release to continue getting critical security fixes.

How can I upgrade?

Where can I get support for 28 pre-releases?

For IRC Support, please use the #fedora-qa channel instead of the main #fedora channel. The FedoraForum site has a dedicated forum for Alpha and Beta pre-releases; please use that forum instead of the main forum. For email list discussions, please use the fedora-test-list.