2. fedora-docs-l10n/program_management
3. Search

Filters

• Untranslated strings • state:empty
• Unfinished strings • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with screenshots • has:screenshot
• Strings with labels • has:label
• Strings with context • has:context
• Unfinished strings without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

state:>=translated

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Target string
• String age
• Last updated
• Number of words
• Number of comments
• Number of failing checks
• Key
• String location

	Translation	Source string	Target string
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/blocker-email — English	When there's an update with a candidate fix: "QA to verify <update ID>"	When there's an update with a candidate fix: "QA to verify <update ID>"
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/changes-process — English	If the Change involves creating a new Spin, send the owners the xref:releases::spins/creating.adoc[Creating a Spin docs]. Otherwise, the coordination with Websites et al will probably be overlooked.	If the Change involves creating a new Spin, send the owners the xref:releases::spins/creating.adoc[Creating a Spin docs]. Otherwise, the coordination with Websites et al will probably be overlooked.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/changes-contingency — English	Completion deadline (100% complete) FESCo issue template	Completion deadline (100% complete) FESCo issue template
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/elections-open — English	devel-announce list (FESCo election)	devel-announce list (FESCo election)
	fedora-docs-l10n/program_management/master/pages/pgm_guide/release_process — English	Bug rebase notes	Bug rebase notes
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	This should be descriptive, but unique. For example "glibc 2.29" is preferable to "glibc upgrade".	This should be descriptive, but unique. For example "glibc 2.29" is preferable to "glibc upgrade".
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	Release Engineering	Release Engineering
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	Release Engineering	Ingeniería de Lanzamiento
	fedora-docs-l10n/program_management/master/pages/covid19 — English	2021-08-19 - Mass rebuild ends	2021-08-19 - Mass rebuild ends
	fedora-docs-l10n/program_management/master/pages/pgm_guide/schedule — English	Edit the appropriate file	Edit the appropriate file
	fedora-docs-l10n/program_management/master/pages/pgm_guide/pgm_communication — English	Add the bug owner to the bcc list if they have an action item. Also include anyone marked as needinfo.	Add the bug owner to the bcc list if they have an action item. Also include anyone marked as needinfo.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/release-new — English	Fedora Linux NN Accepted System-Wide Changes	Fedora Linux NN Accepted System-Wide Changes
	fedora-docs-l10n/program_management/master/pages/pgm_guide/release_process — English	Bugs that meet all of the following conditions are branched from Rawhide to the newly-created version:	Bugs that meet all of the following conditions are branched from Rawhide to the newly-created version:
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/fridays_fedora_facts — English	Proposal. This is the title of the proposal with a link to the wiki page.	Proposal. This is the title of the proposal with a link to the wiki page.
	fedora-docs-l10n/program_management/nav — English	xref:pgm_guide/sop/release_day.adoc[Release day]	xref:pgm_guide/sop/release_day.adoc[Release day]
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/release_day — English	Resolution: _CURRENTRELEASE_	Resolution: _CURRENTRELEASE_
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/blocker-email — English	When the bug is in VERIFIED state: "(none)"	When the bug is in VERIFIED state: "(none)"
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/changes-contingency — English	On Tuesday, <DATE> we reached the Change Checkpoint: Completion deadline (100% complete). At this milestone all the F<VERSION> Changes should be fully complete, which is indicated by "ON_QA" status of a tracking bug. A [Bugzilla query](pass:[https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&f1=blocked&list_id=12817824&o1=substring&v1=F<VERSION>Changes]) shows all the tracking bugs which are not in "ON_QA" state and are not considered complete. System-Wide Changes with the contingency date in bold are past the stated contingency date.	On Tuesday, <DATE> we reached the Change Checkpoint: Completion deadline (100% complete). At this milestone all the F<VERSION> Changes should be fully complete, which is indicated by "ON_QA" status of a tracking bug. A [Bugzilla query](pass:[https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&f1=blocked&list_id=12817824&o1=substring&v1=F<VERSION>Changes]) shows all the tracking bugs which are not in "ON_QA" state and are not considered complete. System-Wide Changes with the contingency date in bold are past the stated contingency date.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/elections-open — English	Post to Fedora Discussion with a link to the Community Blog post and a link to the wiki page in the:	Post to Fedora Discussion with a link to the Community Blog post and a link to the wiki page in the:
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/changes-process — English	RELEASE NOTES: most Changes should be considered for release notes, but sometimes this does not make sense. When a Change will not result in any notable impact on end users that can comprehensibly be explained to them, a release note is not necessary. An example of such a Change is https://fedoraproject.org/wiki/Changes/PortingToModernC : this is a highly technical Change that is only of consequence and interest to Fedora maintainers, not end users. When it does not make sense for a Change to have release notes, put "Release Notes tracker: N/A" in the "Current status" section of the Change page.	RELEASE NOTES: most Changes should be considered for release notes, but sometimes this does not make sense. When a Change will not result in any notable impact on end users that can comprehensibly be explained to them, a release note is not necessary. An example of such a Change is https://fedoraproject.org/wiki/Changes/PortingToModernC : this is a highly technical Change that is only of consequence and interest to Fedora maintainers, not end users. When it does not make sense for a Change to have release notes, put "Release Notes tracker: N/A" in the "Current status" section of the Change page.
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Make sure your page is in the `Changes` namespace (e.g. call it `Changes/glibc_2.29`)	Make sure your page is in the `Changes` namespace (e.g. call it `Changes/glibc_2.29`)
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	For all system-wide changes you must file an issue in https://pagure.io/releng/issues[releng pagure] to check if your change requires Release Engineering involvement.	For all system-wide changes you must file an issue in https://pagure.io/releng/issues[releng pagure] to check if your change requires Release Engineering involvement.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/release_process — English	product == "Fedora" or "Fedora Container Images"	product == "Fedora" or "Fedora Container Images"
	fedora-docs-l10n/program_management/master/pages/pgm_guide/pgm_communication — English	Include an action summary at the top.	Include an action summary at the top.
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	For all system-wide changes you must file an issue in https://pagure.io/releng/issues[releng pagure] to check if your change requires Release Engineering involvement.	Para cambios en todo el sistema debe presentar un problema en https://pagure.io/releng/issues[releng pagure] para comprobar si su cambio requiere la participación de Release Engineering.
	fedora-docs-l10n/program_management/master/pages/covid19 — English	2021-09-14 - Beta Release early target	2021-09-14 - Beta Release early target
	fedora-docs-l10n/program_management/master/pages/pgm_guide/schedule — English	`make publish` to rsync to fedorapeople	`make publish` to rsync to fedorapeople
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/release-new — English	{{Anchor|accepted_self_contained}}	{{Anchor|accepted_self_contained}}
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/fridays_fedora_facts — English	Type. (System-Wide or Self-Contained)	Type. (System-Wide or Self-Contained)
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/release_day — English	Comment: Something to the effect of "F<VERSION> was released today, so I am closing this tracker. If this Change was not completed, please notify me ASAP."	Comment: Something to the effect of "F<VERSION> was released today, so I am closing this tracker. If this Change was not completed, please notify me ASAP."
	fedora-docs-l10n/program_management/nav — English	xref:pgm_guide/sop/eol-warning.adoc[EOL warning]	xref:pgm_guide/sop/eol-warning.adoc[EOL warning]
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/blocker-email — English	When there's informating missing: " "<person> to provide <missing info>"	When there's informating missing: " "<person> to provide <missing info>"
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/changes-process — English	Rejected proposals	Rejected proposals
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/changes-contingency — English	These changes are presented for FESCo review to determine what action, if any, should be taken.	These changes are presented for FESCo review to determine what action, if any, should be taken.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/elections-open — English	`#council` tag (Council election)	`#council` tag (Council election)
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Summary	Summary
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	Release Engineering tickets are not required by default for self-contained changes, but may be necessary if the change involves, for example, adding a new output artifact.	Release Engineering tickets are not required by default for self-contained changes, but may be necessary if the change involves, for example, adding a new output artifact.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/release_process — English	version == rawhide	version == rawhide
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	Release Engineering tickets are not required by default for self-contained changes, but may be necessary if the change involves, for example, adding a new output artifact.	Los tickets a Release Engineering no se requieren de forma predeterminada para los cambios autónomos, pero pueden ser necesarios si el cambio implica, por ejemplo, añadir un nuevo artefacto de salida.
	fedora-docs-l10n/program_management/master/pages/covid19 — English	2021-09-21 - Beta Release target	2021-09-21 - Beta Release target
	fedora-docs-l10n/program_management/master/pages/pgm_guide/schedule — English	Commit and push your edits	Commit and push your edits
	fedora-docs-l10n/program_management/master/pages/pgm_guide/pgm_communication — English	Send the email to the devel and test mailing lists, and bcc the people you identified above.	Send the email to the devel and test mailing lists, and bcc the people you identified above.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/release-new — English	Fedora Linux NN Accepted Self-Contained Changes	Fedora Linux NN Accepted Self-Contained Changes
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/fridays_fedora_facts — English	Status. One of "announced" (include a link to the https://lists.fedoraproject.org/archives/list/devel%40lists.fedoraproject.org/[devel mailing list] thread), "FESCo #<ticket number>" (include a link to the FESCo ticket), approved, rejected, or withdrawn.	Status. One of "announced" (include a link to the https://lists.fedoraproject.org/archives/list/devel%40lists.fedoraproject.org/[devel mailing list] thread), "FESCo #<ticket number>" (include a link to the FESCo ticket), approved, rejected, or withdrawn.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/release_day — English	Then close the FNNTracking bug.	Then close the FNNTracking bug.
	fedora-docs-l10n/program_management/nav — English	xref:pgm_guide/sop/eol-day.adoc[EOL day]	xref:pgm_guide/sop/eol-day.adoc[EOL day]
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/blocker-email — English	Tips	Tips
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/changes-process — English	If a Change proposal is rejected by FESCo:	If a Change proposal is rejected by FESCo:
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/elections-open — English	`#mindshare` tag (Mindshare election)	`#mindshare` tag (Mindshare election)
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Motivation section below, and this part should answer the question "What?" rather than "Why?".	A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Motivation section below, and this part should answer the question "What?" rather than "Why?".
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	Trademark Approval	Trademark Approval
	fedora-docs-l10n/program_management/master/pages/pgm_guide/release_process — English	component != "Package Review"	component != "Package Review"
	fedora-docs-l10n/program_management/master/pages/pgm_guide/schedule — English	Product Pages	Product Pages
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	Trademark Approval	Aprobación de Marca
	fedora-docs-l10n/program_management/master/pages/covid19 — English	2021-10-19 - Final Release early target	2021-10-19 - Final Release early target
	fedora-docs-l10n/program_management/nav — English	xref:pgm_guide/sop/changes.adoc[Changes]	xref:pgm_guide/sop/changes.adoc[Changes]
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/fridays_fedora_facts — English	Changes status. After the branch point, begin including a table of Change statuses. This is a table with the following columns:	Changes status. After the branch point, begin including a table of Change statuses. This is a table with the following columns:
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/blocker-email — English	The following is general advice.	The following is general advice.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/changes-process — English	Add `{{Change_Rejected_Banner}}` to the proposal's wiki page below the title	Add `{{Change_Rejected_Banner}}` to the proposal's wiki page below the title
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/release_day — English	You can use https://bugzilla.redhat.com/buglist.cgi?f1=blocked&list_id=11983255&o1=substring&query_format=advanced&v1=F39Changes[this Bugzilla query] with the version number changed.	You can use https://bugzilla.redhat.com/buglist.cgi?f1=blocked&list_id=11983255&o1=substring&query_format=advanced&v1=F39Changes[this Bugzilla query] with the version number changed.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/elections-open — English	Halfway through the nomination period, nudge the emails (only devel) and Discussion threads to remind people of the nomination deadline.	Halfway through the nomination period, nudge the emails (only devel) and Discussion threads to remind people of the nomination deadline.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/release-new — English	Add the new release to the https://fedoraproject.org/wiki/Changes[Changes wiki page]	Add the new release to the https://fedoraproject.org/wiki/Changes[Changes wiki page]
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Assume that not everyone who sees this will know what you're talking about. Give a brief description of packages or services where it makes sense.	Assume that not everyone who sees this will know what you're talking about. Give a brief description of packages or services where it makes sense.
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	If your Change may require trademark approval (for example, if it is a new Spin), https://pagure.io/Fedora-Council/tickets/issues[file a ticket] requesting trademark approval from the Fedora Council.	If your Change may require trademark approval (for example, if it is a new Spin), https://pagure.io/Fedora-Council/tickets/issues[file a ticket] requesting trademark approval from the Fedora Council.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/release_process — English	component != "Container Review"	component != "Container Review"
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	If your Change may require trademark approval (for example, if it is a new Spin), https://pagure.io/Fedora-Council/tickets/issues[file a ticket] requesting trademark approval from the Fedora Council.	Si su Cambio puede requerir aprobación de marca (por ejemplo, si es un nuevo Spin), https://pagure.io/Fedora-Council/tickets/issues[presente un ticket] pidiendo aprobación de marca del Fedora Council.
	fedora-docs-l10n/program_management/master/pages/covid19 — English	2021-10-26 - Final Release target	2021-10-26 - Final Release target
	fedora-docs-l10n/program_management/master/pages/pgm_guide/schedule — English	https://pp.engineering.redhat.com/[Product Pages] is the central resource for Red Hat internal product schedule and status information.	https://pp.engineering.redhat.com/[Product Pages] is the central resource for Red Hat internal product schedule and status information.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/fridays_fedora_facts — English	Status. The Bugzilla status.	Status. The Bugzilla status.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/release_day — English	Wiki	Wiki
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/blocker-email — English	Don't worry about getting too deep into the technical aspects. You're not there to diagnose issues.	Don't worry about getting too deep into the technical aspects. You're not there to diagnose issues.
	fedora-docs-l10n/program_management/nav — English	xref:pgm_guide/sop/changes-announce.adoc[Announcing Changes]	xref:pgm_guide/sop/changes-announce.adoc[Announcing Changes]
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/changes-process — English	Update the wiki page category to `Category:ChangePageIncomplete`	Update the wiki page category to `Category:ChangePageIncomplete`
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Owner	Owner
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	Change process	Change process
	fedora-docs-l10n/program_management/master/pages/pgm_guide/release_process — English	component != "kernel"	component != "kernel"
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	Change process	Proceso de cambio
	fedora-docs-l10n/program_management/master/pages/covid19 — English	Fedora 35 risks	Fedora 35 risks
	fedora-docs-l10n/program_management/master/pages/pgm_guide/schedule — English	To register a new version in product pages:	To register a new version in product pages:
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/fridays_fedora_facts — English	Count. The number of tracking bugs in that status.	Count. The number of tracking bugs in that status.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/release_day — English	Edit the ChangeSet page in the wiki to include a link to the release notes and take the table of contents off the top.	Edit the ChangeSet page in the wiki to include a link to the release notes and take the table of contents off the top.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/blocker-email — English	Update bugs if the state is inconsistent with reality. (e.g. if an upstream PR exists, set it to POST)	Update bugs if the state is inconsistent with reality. (e.g. if an upstream PR exists, set it to POST)
	fedora-docs-l10n/program_management/nav — English	xref:pgm_guide/sop/changes-submit.adoc[Submitting Changes]	xref:pgm_guide/sop/changes-submit.adoc[Submitting Changes]
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/changes-process — English	If a tracking bug was pre-created, close it with Status _CLOSED -> DEFERRED_.	If a tracking bug was pre-created, close it with Status _CLOSED -> DEFERRED_.
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	For change proposals to qualify as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.	For change proposals to qualify as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	This is the general flow for change proposals:	This is the general flow for change proposals:
	fedora-docs-l10n/program_management/master/pages/pgm_guide/release_process — English	component != "Changes Tracking"	component != "Changes Tracking"
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	This is the general flow for change proposals:	Este es el flujo general para las propuestas de cambio:
	fedora-docs-l10n/program_management/master/pages/covid19 — English	|Risk area|Impact|Likelihood|Mitigation & Notes |Release engineering staff|High|Low|Release Engineering knowledge is duplicated across multiple people with large geographic separation |Infrastucture staff|High|Low|Infrastructure knowledge is duplicated across multiple people with large geographic separation |QA test staff|High|Low|Testing staff (both Red Hat and non-Red Hat contributors) are widely distributed across the globe |openQA test platform|Medium|Medium|Adam Williamson is the primary admin for openQA. However, other members of the team have knowledge and could keep the platform going if Adam is unavailable. |QA test hardware|Medium|High|Some QA tests require physical access to hardware located in Red Hat offices (see table below). Some of these can be done with contributor’s personally-owned hardware and others may be skipped if Red Hat offices remain closed through the release.	|Risk area|Impact|Likelihood|Mitigation & Notes |Release engineering staff|High|Low|Release Engineering knowledge is duplicated across multiple people with large geographic separation |Infrastucture staff|High|Low|Infrastructure knowledge is duplicated across multiple people with large geographic separation |QA test staff|High|Low|Testing staff (both Red Hat and non-Red Hat contributors) are widely distributed across the globe |openQA test platform|Medium|Medium|Adam Williamson is the primary admin for openQA. However, other members of the team have knowledge and could keep the platform going if Adam is unavailable. |QA test hardware|Medium|High|Some QA tests require physical access to hardware located in Red Hat offices (see table below). Some of these can be done with contributor’s personally-owned hardware and others may be skipped if Red Hat offices remain closed through the release.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/schedule — English	Go to admin page (*Platforms* > *Fedora Project* > *Overview*)	Go to admin page (*Platforms* > *Fedora Project* > *Overview*)
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/fridays_fedora_facts — English	Blockers. List all active blockers for the next release milestone, starting after branch day. (You can choose to include final blockers prior to the beta release, if you feel like doing the work.) List blockers in a table with the following columns:	Blockers. List all active blockers for the next release milestone, starting after branch day. (You can choose to include final blockers prior to the beta release, if you feel like doing the work.) List blockers in a table with the following columns:
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/release_day — English	Update the https://fedoraproject.org/wiki/Changes[Changes wiki page] to move the release to the "Previous Releases" section.	Update the https://fedoraproject.org/wiki/Changes[Changes wiki page] to move the release to the "Previous Releases" section.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/blocker-email — English	If you're short on time, skip the bugs that seem likely to be rejected.	If you're short on time, skip the bugs that seem likely to be rejected.
	fedora-docs-l10n/program_management/nav — English	xref:pgm_guide/sop/changes-process.adoc[Processing Changes]	xref:pgm_guide/sop/changes-process.adoc[Processing Changes]
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Use your Bugzilla email in the `email` field to make your Program Manager happy.	Use your Bugzilla email in the `email` field to make your Program Manager happy.
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	The owner submits the change proposal by setting the wiki page to the *ChangeReadyForWrangler* category.	The owner submits the change proposal by setting the wiki page to the *ChangeReadyForWrangler* category.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/release_process — English	keyword ''FutureFeature'' is '''not''' present	keyword ''FutureFeature'' is '''not''' present
	fedora-docs-l10n/program_management/master/pages/pgm_guide/schedule — English	Click *Add new release* button	Click *Add new release* button
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	The owner submits the change proposal by setting the wiki page to the *ChangeReadyForWrangler* category.	El propietario envía la propuesta de cambio estableciendo la página wiki a la categoria *ChangeReadyForWrangler*.
	fedora-docs-l10n/program_management/master/pages/covid19 — English	Test cases at risk	Test cases at risk

• 13 / 15
  / 15