Translation status

52 Strings 0%
Browse Translate
745 Words 0%
5,136 Characters 0%

Strings status

Strings Words Characters
52 745 5,136
All strings Browse Translate Zen
52 745 5,136
Unfinished strings Browse Translate Zen
52 745 5,136
Untranslated strings Browse Translate Zen
52 745 5,136
Unfinished strings without suggestions Browse Translate Zen

Overview

Project website pagure.io/fedora-docs-l10n/program_management
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/program_management.git
Repository branch master
Last remote commit automatic update of pot/po files a5178f74
♪ I'm a bot, bot, bot ♪ authored 6 days ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-program_management/nav/
File mask po/*/master/pages/pgm_guide/release_process.po
Translation file Download po/bg/master/pages/pgm_guide/release_process.po
Last change None
Last author None
a week ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 52 745 5,136
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% 52 100% 745 100% 5,136
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 30 changes 0 changes 0 changes 0 changes 0 changes 132 changes 0 changes 0 changes 0 changes 0 changes 0 changes 7 changes 0 changes 0 changes 0 changes
May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr

Quick numbers

745
Hosted words
52
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/program_management
  2. master/pages/pgm_guide/release_process
  3. Bulgarian
The “po/bg/master/pages/pgm_guide/release_process.po” file was changed. 7 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/program_management
  2. master/pages/pgm_guide/release_process
  3. Bulgarian
If there are proposed or accepted blocker bugs, the meeting becomes a blocker review meeting to evaluate them. This portion of the meeting can be led by a member of the QA team or by the Program Manager. It is not uncommon to defer some bugs until later in the meeting so that last-minute testing can be performed.
 
7 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/program_management
  2. master/pages/pgm_guide/release_process
  3. Bulgarian
The compose section is generally very quick. Release Engineering or QA will confirm that a candidate compose exists. If there is no candidate compose, skip straight to a "no-go" decision.
 
7 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/program_management
  2. master/pages/pgm_guide/release_process
  3. Bulgarian
The https://pagure.io/fedora-pgm/pgm_communication/blob/main/f/go_nogo.txt[meeting script] in the xref:pgm_guide/sop/go-nogo.adoc[Go/No-Go SOP] provides a general framework for running the Go/No-Go meeting. The general flow is to verify that a compose is available, review blocker bugs, check that the test matrices are completed, and that CoreOS and IoT are ready.
 
7 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/program_management
  2. master/pages/pgm_guide/release_process
  3. Bulgarian
[[gonogo_notes]]Go/No-Go Meeting notes
 
7 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/program_management
  2. master/pages/pgm_guide/release_process
  3. Bulgarian
Bug rebase notes
 
7 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/program_management
  2. master/pages/pgm_guide/release_process
  3. Bulgarian
This is the email that should be sent out 1-3 weeks before the Branch point. The actual rebase is covered in the xref:pgm_guide/sop/branch.adoc[Branching SOP].
 
7 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/program_management
  2. master/pages/pgm_guide/release_process
  3. Bulgarian
Rebase warning mail
 
7 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/program_management
  2. master/pages/pgm_guide/release_process
  3. Bulgarian
Follow xref:pgm_guide/sop/eol-day.adoc[EOL day SOP] for the N-2 release
 
7 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/program_management
  2. master/pages/pgm_guide/release_process
  3. Bulgarian
Four weeks after release day
 
7 months ago
Browse all translation changes