Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English CC-BY-SA-3.0 0 0 0 0 0 0 0
Arabic CC-BY-SA-3.0 0% 40 946 6,598 40 0 0 0
Chinese (Simplified) CC-BY-SA-3.0 0% 40 946 6,598 40 0 1 0
Czech CC-BY-SA-3.0 0% 40 946 6,598 40 0 1 0
French CC-BY-SA-3.0 0% 40 946 6,598 40 0 0 0
German CC-BY-SA-3.0 0% 40 946 6,598 40 0 0 0
Italian CC-BY-SA-3.0 0% 40 946 6,598 40 0 0 0
Japanese CC-BY-SA-3.0 0% 40 946 6,598 40 0 0 0
Portuguese (Brazil) CC-BY-SA-3.0 0% 40 946 6,598 40 0 0 0
Portuguese (Portugal) CC-BY-SA-3.0 0% 40 946 6,598 40 0 0 0
Spanish CC-BY-SA-3.0 0% 40 946 6,598 40 0 0 0
Telugu CC-BY-SA-3.0 0% 40 946 6,598 40 0 0 0
Please sign in to see the alerts.

Overview

Project website pagure.io/fedora-docs-l10n/quick-docs
Instructions for translators

Mailing list for translators: <<trans@lists.fedoraproject.org>
Translation license Creative Commons Attribution Share Alike 3.0 Unported
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository ssh://pagure.io/fedora-docs-l10n/quick-docs.git
Repository branch master
Last remote commit automatic update of pot/po files 07a1b530fd
♪ I'm a bot, bot, bot ♪ authored 2 days ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-quick-docs/nav/
File mask po/*/master/pages/upgrading-fedora-new-release.po
2 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 480 11,352 79,176
Source 40 946 6,598
Translated 8% 40 8% 946 8% 6,598
Needs editing 0% 0 0% 0 0% 0
Read-only 8% 40 8% 946 8% 6,598
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 1% 2 1% 20 1% 96
Untranslated strings 91% 440 91% 10,406 91% 72,578
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 372 changes 0 changes 4 changes 0 changes 0 changes 0 changes 102 changes 0 changes 41 changes 0 changes 0 changes 0 changes 42 changes 0 changes 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

11,352
Hosted words
480
Hosted strings
8%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

+4%
Hosted words
+100%
+2%
Hosted strings
+100%
—
Translated
+8%
−100%
Contributors
+100%
User avatar None

Resource updated

  1. fedora-docs-l10n/quick-docs
  2. master/pages/upgrading-fedora-new-release
  3. Chinese (Simplified)
The "po/zh_Hans/master/pages/upgrading-fedora-new-release.po" file was changed. 2 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/quick-docs
  2. master/pages/upgrading-fedora-new-release
  3. Chinese (Simplified)
Fedora releases up to 17 included upgrade functionality in the 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 16 or older, it is highly recommended to upgrade to 16 and perform an installer upgrade from 16 to 17 before upgrading any further.
 
2 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/quick-docs
  2. master/pages/upgrading-fedora-new-release
  3. Chinese (Simplified)
Upgrading using the Fedora Linux installer (anaconda)?
 
2 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/quick-docs
  2. master/pages/upgrading-fedora-new-release
  3. Chinese (Simplified)
Upgrading to pre-released versions of Fedora Linux can be enabled in Gnome software using the following command:
 
2 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/quick-docs
  2. master/pages/upgrading-fedora-new-release
  3. Chinese (Simplified)
Fedora strongly discourages running an end-of-life release on any production system, or any system connected to the public internet. You should never allow a production Fedora Linux deployment to reach end-of-life in the first place.
 
2 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/quick-docs
  2. master/pages/upgrading-fedora-new-release
  3. Chinese (Simplified)
link:++https://fedoraproject.org/wiki/Releases/Rawhide++[Rawhide] and link:++https://fedoraproject.org/wiki/Releases/Branched++[Branched] are the development releases of Fedora Linux. They are suitable for users developing or testing Fedora Linux 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 Release 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.
 
2 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/quick-docs
  2. master/pages/upgrading-fedora-new-release
  3. Chinese (Simplified)
If you are using a pre-release of Fedora Linux, 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 upgrade` 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.
 
2 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/quick-docs
  2. master/pages/upgrading-fedora-new-release
  3. Chinese (Simplified)
Upgrading between Fedora Linux releases without the xref:upgrading-fedora-offline.adoc[DNF System Upgrade plugin] or xref:#_upgrading_to_the_next_fedora_workstation_release[GNOME Software] are not tested by the Fedora Quality team, and are therefore not supported by the community. You can follow xref:upgrading-fedora-online.adoc[Upgrading Fedora Linux using package manager], but you're doing that *at your own risk*.
 
2 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/quick-docs
  2. master/pages/upgrading-fedora-new-release
  3. Chinese (Simplified)
Can I upgrade between Fedora Linux releases using only DNF?
 
2 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/quick-docs
  2. master/pages/upgrading-fedora-new-release
  3. Chinese (Simplified)
Upgrading between major versions (such as from Fedora Linux 38 to Fedora Linux 39) can be completed using the Software application. Alternatively, Silverblue can be upgraded between major versions using the `ostree` command..
 
2 days ago
Browse all component changes