Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English CC-BY-SA-3.0 0 0 0 0 1 0 0
French CC-BY-SA-3.0 0% 109 3,295 21,902 109 0 2 0
Please sign in to see the alerts.

Overview

Project website pagure.io/fedora-docs-l10n/package-maintainers
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/package-maintainers.git
Repository branch master
Last remote commit automatic update of pot/po files 99bca1b
♪ I'm a bot, bot, bot ♪ authored 5 days ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-package-maintainers/nav/
File mask po/*/master/pages/Package_Update_Guide.po
5 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 218 6,590 43,804
Source 109 3,295 21,902
Translated 50% 109 50% 3,295 50% 21,902
Needs editing 0% 0 0% 0 0% 0
Read-only 50% 109 50% 3,295 50% 21,902
Failing checks 1% 1 1% 80 1% 523
Strings with suggestions 1% 2 1% 3 1% 24
Untranslated strings 50% 109 50% 3,295 50% 21,902
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 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 287 changes 0 changes 0 changes 0 changes 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

6,590
Hosted words
218
Hosted strings
50%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

+15%
Hosted words
+100%
−3%
Hosted strings
+100%
—
Translated
+50%
+100%
Contributors
—
User avatar None

Resource updated

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/Package_Update_Guide
  3. French
The “po/fr/master/pages/Package_Update_Guide.po” file was changed. 5 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/Package_Update_Guide
  3. French
For more on the Fedora development process, see xref:releases::lifecycle.adoc[Fedora Release Life Cycle].
 
5 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/Package_Update_Guide
  3. French
When a release is in stable state, the _updates-testing_ repository is disabled by default, but Quality team members and others run with it enabled in order to provide testing and Bodhi feedback. The main user population will see your update only when it passes Bodhi, is marked as _stable_ and reaches the _updates_ repository. Both _updates-testing_ and _updates_ repositories are regenerated daily.
 
5 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/Package_Update_Guide
  3. French
For Branched releases after updates-testing activation, the _updates-testing_ repository is enabled by default so most users will get your update soon after it is pushed there, but only packages that have been pushed to _stable_ are used in building composes (both nightlies and the Beta and Final candidates and releases). The _updates-testing_ repository is regenerated daily.
 
5 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/Package_Update_Guide
  3. French
For Rawhide and Branched before updates-testing activation, when an update goes _stable_ it is tagged for inclusion in the next compose. Composes are usually run daily at 05:15 UTC and take several hours. After a compose completes, it takes some more time for it to reach the public mirrors. All users will see your update when they update their systems after a successful compose containing your update has reached the mirrors.
 
5 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/Package_Update_Guide
  3. French
A tool called `waiverdb-cli` exists for filing waivers manually, though this should rarely be necessary. The tool is also missing some features needed to correctly specify waivers in some cases, like the ability to specify a scenario. It is not currently packaged in Fedora. You can get it from the https://pagure.io/waiverdb[the waiverdb repository], which also has some instructions on usage.
 
5 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/Package_Update_Guide
  3. French
Any failure of a gating test will prevent your update from being released. On the update's _Details_ page in the Bodhi web interface, the *Test Gating* status will be shown as _N of N required tests failed_, and one or more red rows with asterisks should be present on the _Automated Tests_ tab. If you are absolutely sure such a failure is a false one, you can 'waive' all failed gating tests from the Bodhi web interface by clicking the *Waive Test Results* button. This button is only present when an update has failed gating tests, and you have privileges to control the update. At present it is not possible to waive the absence of a result for a gating test in this way. If needed, this can be done with `waiverdb-cli`. Please do not waive failures of openQA tests - those whose names start with _update._ - without checking with the https://fedoraproject.org/wiki/QA#Communicate[Fedora Quality team].
 
5 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/Package_Update_Guide
  3. French
The Fedora Quality team proactively investigates failed openQA tests and will usually resolve them or post a comment on the update explaining the problem and suggesting a resolution.
 
5 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/Package_Update_Guide
  3. French
The tests are not all 100% accurate, but they are fairly often correct. Especially failures of openQA tests - those whose name starts with _update._ - should always be investigated and resolved before an update is pushed stable. If you see a failure, it is a very good idea to click on the result (which will take you to a detailed log) and investigate the issue. If you are unsure what the test indicates, you can contact the relevant team for help. When a test has failed gating, a box is shown with contact details.
 
5 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/Package_Update_Guide
  3. French
Tests shown with a blue background and an hourglass icon are pending.
 
5 days ago
Browse all component changes