Translation status

56 Strings 0%
Browse Translate
2,292 Words 0%
17,277 Characters 0%

Strings status

Strings Words Characters
56 2,292 17,277
All strings Browse Translate Zen
56 2,292 17,277
Unfinished strings Browse Translate Zen
56 2,292 17,277
Untranslated strings Browse Translate Zen
56 2,292 17,277
Unfinished strings without suggestions Browse Translate Zen

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 8 days ago
Last commit in Weblate Translated using Weblate (Spanish) 5c144eb3d9
User avatar vareli authored 2 days ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-quick-docs/nav/
File mask po/*/master/pages/fedora-repositories.po
Translation file Download po/it/master/pages/fedora-repositories.po
Last change None
Last author None
3 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 56 2,292 17,277
Translated 0% 0 0% 0 0% 0
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 100% 56 100% 2,292 100% 17,277
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 59 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr

Quick numbers

2,292
Hosted words
56
Hosted strings
0%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
—
—
Contributors
—
User avatar None

Resource updated

  1. fedora-docs-l10n/quick-docs
  2. master/pages/fedora-repositories
  3. Italian
File “po/it/master/pages/fedora-repositories.po” was added. 8 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/quick-docs
  2. master/pages/fedora-repositories
  3. Italian
See a typo, something missing or out of date, or anything else which can be improved? Edit this document at https://pagure.io/fedora-docs/quick-docs.
 
8 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/quick-docs
  2. master/pages/fedora-repositories
  3. Italian
For this and other less important functions, we need as much feedback as possible, so it makes sense to have all pre-release testers have _updates-testing_ enabled by default, and encourage them to provide feedback through Bodhi.
 
8 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/quick-docs
  2. master/pages/fedora-repositories
  3. Italian
The main purpose is to insulate _image builds_ from potentially problematic changes. Branched images - nightly images, and the Alpha, Beta and GA (Final) _milestone_ builds and their https://fedoraproject.org/wiki/Go_No_Go_Meeting[test compose and release candidate builds] - are built from the _stable_ packages, that is, only those in the _fedora_ repository, not those in _updates-testing_. In this sense, _updates-testing_ protects not a set of users, but a set of _builds_, from potentially destabilizing changes. Especially when we are building an Alpha, Beta or GA release, we need to be able to reduce the amount of change in the package set between composes in order to produce an image of high quality. The _updates-testing_ mechanism allows for that: during https://fedoraproject.org/wiki/Milestone_freezes[Milestone freezes], new builds can be sent to _updates-testing_, but cannot move from there to _stable_ (_fedora_) without special circumstances. In this way, we can work on release images while not preventing packagers from sending out builds.
 
8 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/quick-docs
  2. master/pages/fedora-repositories
  3. Italian
When it comes to a Branched pre-release, the expectation is that anyone who installs it wants to help test it: we effectively consider anyone running a Branched release to be a tester. The function of _updates-testing_ is different in this case. There is not a 'general user population' of Branched users who run with _updates-testing_ disabled, and are protected from problematic updates by the group of update testers. Instead, _updates-testing_ in Branched serves other important functions.
 
8 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/quick-docs
  2. master/pages/fedora-repositories
  3. Italian
The reason is that the purpose of the _updates-testing_ system is somewhat different in each case. For stable releases, the system's goal is to prevent broken updates reaching the general Fedora user population. In most cases, Fedora systems are expected to have the _updates-testing_ repository disabled. Some QA testers then enable the repository on testing systems to try out the updates and provide feedback. The testers perform the job of making sure the updates are OK before they reach the general user population.
 
8 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/quick-docs
  2. master/pages/fedora-repositories
  3. Italian
While Branched development releases and stable releases both use an _updates-testing_ repository together with the Bodhi update feedback system to stage packages before they reach the release's _stable_ state, it is enabled by default in Branched, but not in stable releases.
 
8 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/quick-docs
  2. master/pages/fedora-repositories
  3. Italian
Why is _updates-testing_ enabled by default in pre-releases?
 
8 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/quick-docs
  2. master/pages/fedora-repositories
  3. Italian
Before a stable release occurs, this mechanism is not necessary. Before the release is declared to be done, there is no _frozen_ state of the release: effectively, the whole Branched development process is _working towards_ what will become the _frozen_ state of the release, so of course package builds for the Branched release land directly in the _fedora_ repository.
 
8 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/quick-docs
  2. master/pages/fedora-repositories
  3. Italian
Since we wish to maintain this _frozen_ state for the _fedora_ repository, we cannot place updates directly into it. The necessity for the _updates_ repository therefore becomes obvious - we need a place to put updates to stable releases that is outside the _frozen_ state of the release.
 
8 months ago
Browse all translation changes