From Fedora Project Wiki
(Created page with '== Begin Began Begun ==')
 
No edit summary
Line 1: Line 1:
== Begin Began Begun ==
{{autolang}}
 
Una αlpha o βeta (a partire da Fedora 13), fa automaticamente parte della fase [[Releases/Branched|Branched]], quindi per ottenere una final non occorre far altro che installare i pacchetti di aggiornamento (manualmente via yum o PackageKit GUI, oppure automaticamente, attendendo le notifiche dal sistema). Tuttavia, l'upgrade presenta alcune differenze, rispetto ad una installazione completamente nuova, per via dell'installer che opera in modo leggermente diverso rispetto al gestore dei pacchetti.
 
Se invece si ha una [[Releases/Rawhide|Rawhide]], per ottenere una final release, si dovrebbe effettuare un ''downgrade'', di cui non si garantisce l'efficacia - meglio procedere con una nuova installazione! 
Per altre situazioni, vedere [[Releases/Branched/it#Upgrade da una precedente release via Preupgrade|Upgrade da una precedente release via Preupgrade]] e [[Releases/Branched/it#Upgrade via Yum(Per gli arditi)|Upgrade via Yum]].
 
 
== 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, select the '''Software Sources''' application from ''System > Administration > Software Sources'' on the menu, or run this command:
<pre>su -c 'mv /etc/yum.repos.d/fedora-rawhide.repo.rpmnew /etc/yum.repos.d/fedora-rawhide.repo'</pre>
 
== 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 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? ==
 
You can use such avenues for discussions however for maximum efficiency, we always recommend that all actual bugs be reported to [https://bugzilla.redhat.com/ 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 {{FedoraVersion||next}} going to be released? ==
 
An up-to-date release schedule is always maintained at [[Releases/{{FedoraVersion||next}}/Schedule]].
 
== What are the new features in Fedora {{FedoraVersion||next}}? ==
 
The [[Releases/{{FedoraVersion||next}}/FeatureList|Fedora {{FedoraVersion||next}} feature list]] and [[Fedora_{{FedoraVersion||next}}_Announcement]] have more details.
 
== Should I upgrade to Fedora {{FedoraVersion||next}}? ==
 
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 {{FedoraVersion||previous}} will stop getting updates a month after Fedora {{FedoraVersion||next}} 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? ==
 
Refer to [[Upgrading]].
 
== 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 and Beta 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].
 
 
[[Category:How to]]

Revision as of 13:46, 13 August 2010

Una αlpha o βeta (a partire da Fedora 13), fa automaticamente parte della fase Branched, quindi per ottenere una final non occorre far altro che installare i pacchetti di aggiornamento (manualmente via yum o PackageKit GUI, oppure automaticamente, attendendo le notifiche dal sistema). Tuttavia, l'upgrade presenta alcune differenze, rispetto ad una installazione completamente nuova, per via dell'installer che opera in modo leggermente diverso rispetto al gestore dei pacchetti.

Se invece si ha una Rawhide, per ottenere una final release, si dovrebbe effettuare un downgrade, di cui non si garantisce l'efficacia - meglio procedere con una nuova installazione!

Per altre situazioni, vedere Upgrade da una precedente release via Preupgrade e Upgrade via Yum.


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 Package-x-generic-16.pngfedora-release. For example, if you have switched from using mirrorlist= to baseurl= for a repository definition, this situation occurs. Once Package-x-generic-16.pngfedora-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:

su -c 'mv /etc/yum.repos.d/fedora-rawhide.repo.rpmnew /etc/yum.repos.d/fedora-rawhide.repo'

I found a Fedora 40 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 40 going to be released?

An up-to-date release schedule is always maintained at Releases/40/Schedule.

What are the new features in Fedora 40?

The Fedora 40 feature list and Fedora_40_Announcement have more details.

Should I upgrade to Fedora 40?

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 38 will stop getting updates a month after Fedora 40 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?

Refer to Upgrading.

Where can I get support for 40 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.