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/changes_guide — English	If this is a new functionality, what capabilities does it bring? For example: This change allows package upgrades to be performed automatically and rolled-back at will.	If this is a new functionality, what capabilities does it bring? For example: This change allows package upgrades to be performed automatically and rolled-back at will.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/schedule — English	*People*: update this as appropriate	*People*: update this as appropriate
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	New change proposals may be submitted using the guidelines described elsewhere and until the appropriate change proposal submission deadline. For a given release, this date is available in the https://fedorapeople.org/groups/schedule/[release schedule] and will be announced well in advance.	New change proposals may be submitted using the guidelines described elsewhere and until the appropriate change proposal submission deadline. For a given release, this date is available in the https://fedorapeople.org/groups/schedule/[release schedule] and will be announced well in advance.
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	New change proposals may be submitted using the guidelines described elsewhere and until the appropriate change proposal submission deadline. For a given release, this date is available in the https://fedorapeople.org/groups/schedule/[release schedule] and will be announced well in advance.	Las nuevas propuestas de cambio se pueden enviar siguiendo las directrices descritas en otra parte y hasta el plazo apropiado de envío de propuestas de cambio. Para un lanzamiento dado, esta fecha está disponible en el https://fedorapeople.org/groups/schedule/[calendario de lanzamiento] y será anunciada por anticipado.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/fridays_fedora_facts — English	Refer to the Community Blog https://communityblog.fedoraproject.org/writing-community-blog-article/[contribution documentation] and https://communityblog.fedoraproject.org/editor-guidelines/[article guidelines] for more details.	Refer to the Community Blog https://communityblog.fedoraproject.org/writing-community-blog-article/[contribution documentation] and https://communityblog.fedoraproject.org/editor-guidelines/[article guidelines] for more details.
	fedora-docs-l10n/program_management/nav — English	xref:pgm_guide/sop/elections-setup.adoc[Election app setup]	xref:pgm_guide/sop/elections-setup.adoc[Election app setup]
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Does this improve some specific package or set of packages? For example: This change modifies a package to use a different language stack that reduces install size by removing dependencies.	Does this improve some specific package or set of packages? For example: This change modifies a package to use a different language stack that reduces install size by removing dependencies.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/schedule — English	*Communication*: list of important IRC channels and mailing lists	*Communication*: list of important IRC channels and mailing lists
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	Changes do not have to be accepted by this deadline, but they must have been submitted to the Program Manager by then.	Changes do not have to be accepted by this deadline, but they must have been submitted to the Program Manager by then.
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	Changes do not have to be accepted by this deadline, but they must have been submitted to the Program Manager by then.	Los cambios no tienen que ser aceptados en este plazo, pero deben haber sido enviados al Program Manager entonces.
	fedora-docs-l10n/program_management/nav — English	xref:pgm_guide/sop/elections-results.adoc[Election results]	xref:pgm_guide/sop/elections-results.adoc[Election results]
	fedora-docs-l10n/program_management/master/pages/pgm_guide/schedule — English	Status updates	Status updates
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	Code complete (testable) deadline	Code complete (testable) deadline
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	Code complete (testable) deadline	Plazo del código completo (para probar)
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Does this improve specific Spins or Editions? For example: This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server.	Does this improve specific Spins or Editions? For example: This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server.
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Does this make the distribution more efficient? For example: This change replaces thousands of individual %post scriptlets in packages with one script that runs at the end.	Does this make the distribution more efficient? For example: This change replaces thousands of individual %post scriptlets in packages with one script that runs at the end.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/schedule — English	Update the phases when there's a significant change (e.g. Beta release -> change to testing).	Update the phases when there's a significant change (e.g. Beta release -> change to testing).
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	By this date, a new change must be feature complete or close enough to completion that a majority of its functionality can be tested prior the Beta release.	By this date, a new change must be feature complete or close enough to completion that a majority of its functionality can be tested prior the Beta release.
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	By this date, a new change must be feature complete or close enough to completion that a majority of its functionality can be tested prior the Beta release.	Para esta fecha, un nuevo cambio debe tener todas las funciones o estar lo suficientemente cerca de completarse como para que la mayoría de su funcionalidad se pueda probar antes del lanzamiento Beta.
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Is this an improvement to maintainer processes? For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly.	Is this an improvement to maintainer processes? For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/schedule — English	Update the status on a weekly basis (due Thursday afternoon US East coast time). Green means no risks and no slippage; you don't need to say much. Yellow means there are risks, but we have it under control. Describe what went wrong and how we're going to address it. Red means "oh noes!"; explain a lot more.	Update the status on a weekly basis (due Thursday afternoon US East coast time). Green means no risks and no slippage; you don't need to say much. Yellow means there are risks, but we have it under control. Describe what went wrong and how we're going to address it. Red means "oh noes!"; explain a lot more.
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	If a change proposal page specifies a change will be enabled by default, it must be so by this milestone.	If a change proposal page specifies a change will be enabled by default, it must be so by this milestone.
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	If a change proposal page specifies a change will be enabled by default, it must be so by this milestone.	Si una página de propuesta de cambio especifica que un cambio será habilitado de forma predeterminada, debe ser así para ese hito.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/schedule — English	Historical notes	Historical notes
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	Changes that are testable should have their tracking bug set to the *MODIFIED* status.	Changes that are testable should have their tracking bug set to the *MODIFIED* status.
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	Changes that are testable should have their tracking bug set to the *MODIFIED* status.	Los cambios que se pueden probar deben tener su estado en el rastreador de errores establecido a *MODIFIED*.
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Is this an improvement targeted at specific contributors? For example: Ensuring that a minimal set of tools required for contribution to Fedora are installed by default eases the onboarding of new contributors.	Is this an improvement targeted at specific contributors? For example: Ensuring that a minimal set of tools required for contribution to Fedora are installed by default eases the onboarding of new contributors.
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	When a Change has multiple benefits, it's better to list them all.	When a Change has multiple benefits, it's better to list them all.
	fedora-docs-l10n/program_management/master/pages/pgm_guide/schedule — English	This section is a collection of loosely-organized facts that give some of the history of schedule wrangling.	This section is a collection of loosely-organized facts that give some of the history of schedule wrangling.
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	At this point, Rawhide and the immediately-upcoming "N+1" release are already separate branches. If development, testing, integration — and integration testing! — are not really all lined up by this point, there is no shame in re-targeting for the next (N+2) release. Now is the time for you to bring that to FESCo. Or, if this change is time-sensitive, but needs more resources or attention from across the community, bring that to FESCo, to the Fedora Council, and to the Fedora community at large.	At this point, Rawhide and the immediately-upcoming "N+1" release are already separate branches. If development, testing, integration — and integration testing! — are not really all lined up by this point, there is no shame in re-targeting for the next (N+2) release. Now is the time for you to bring that to FESCo. Or, if this change is time-sensitive, but needs more resources or attention from across the community, bring that to FESCo, to the Fedora Council, and to the Fedora community at large.
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	At this point, Rawhide and the immediately-upcoming "N+1" release are already separate branches. If development, testing, integration — and integration testing! — are not really all lined up by this point, there is no shame in re-targeting for the next (N+2) release. Now is the time for you to bring that to FESCo. Or, if this change is time-sensitive, but needs more resources or attention from across the community, bring that to FESCo, to the Fedora Council, and to the Fedora community at large.	En este punto, Rawhide y las versión inmediata que llega "N+1" están ya separadas en ramas. ¡Si se trata de desarrollo, pruebas, integración y pruebas de integración! — en realidad no todos están alineados en este punto y no es ninguna vergüenza plantearlos para la siguiente versión (N+2). Ahora es el momento de que lleve esto a FESCo. O, si este cambio es sensible al momento, pero necesita más recursos o atención de la comunidad llévelo a FESCo, al Fedora Council y a toda la comunidad de Fedora.
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Scope	Scope
	fedora-docs-l10n/program_management/master/pages/pgm_guide/schedule — English	Schedules used to be done with TaskJuggler (version 2, specifically). If you ever need to do anything with the old schedule files, you will need to get a copy of that. (By the time you read this, it will likely be retired from Fedora.)	Schedules used to be done with TaskJuggler (version 2, specifically). If you ever need to do anything with the old schedule files, you will need to get a copy of that. (By the time you read this, it will likely be retired from Fedora.)
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	Code complete (100%) deadline	Code complete (100%) deadline
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	Code complete (100%) deadline	Código completo (100%) fecha límite
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Proposal owners: What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?	Proposal owners: What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?
	fedora-docs-l10n/program_management/master/pages/pgm_guide/schedule — English	We used to copy key milestones to a wiki page. Ben Cotton stopped doing that because it was annoying and he's error-prone.	We used to copy key milestones to a wiki page. Ben Cotton stopped doing that because it was annoying and he's error-prone.
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	Changes must be code complete, meaning all the code required to enable the new change is finished.	Changes must be code complete, meaning all the code required to enable the new change is finished.
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	Changes must be code complete, meaning all the code required to enable the new change is finished.	Los cambios deben ser con el código completo, lo que significa que todo el código requerido para habilitar el nuevo cambio está terminado.
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	The level of code completeness is reflected as tracker bug state *ON_QA*. The change does not have to be fully tested by this deadline.	The level of code completeness is reflected as tracker bug state *ON_QA*. The change does not have to be fully tested by this deadline.
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	The level of code completeness is reflected as tracker bug state *ON_QA*. The change does not have to be fully tested by this deadline.	El nivel de integridad del código se refleja como estado del rastreador *ON_QA*. El cambio no tiene que estar totalmente probado para esta fecha límite.
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Other developers: *REQUIRED FOR SYSTEM-WIDE CHANGES* What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?	Other developers: *REQUIRED FOR SYSTEM-WIDE CHANGES* What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	Code complete (100%) deadline coincides with the Beta Freeze date because that is the last date on which it can be ensured that a build will appear in a milestone release. The idea is really that these requirements be met in the Beta release, but due to the nature of the milestone freezes, in order to ensure this is the case, the requirements must be met by the freeze date.	Code complete (100%) deadline coincides with the Beta Freeze date because that is the last date on which it can be ensured that a build will appear in a milestone release. The idea is really that these requirements be met in the Beta release, but due to the nature of the milestone freezes, in order to ensure this is the case, the requirements must be met by the freeze date.
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	Code complete (100%) deadline coincides with the Beta Freeze date because that is the last date on which it can be ensured that a build will appear in a milestone release. The idea is really that these requirements be met in the Beta release, but due to the nature of the milestone freezes, in order to ensure this is the case, the requirements must be met by the freeze date.	La fecha límite de código completo (100%) coincide con la fecha de Beta Freeze porque esta es la última fecha en la que se puede asegurar que una compilación aparecerá en una versión importante. La idea es realmente que estos requisitos se cumplan en la versión Beta, pero debido a la naturaleza de los hitos de congelación, para garantizar que esto sea así, los requisitos deben cumplirse antes de la fecha de congelación.
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Release engineering: *REQUIRED FOR SYSTEM-WIDE CHANGES* Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? Include a link to the releng issue. The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication.	Release engineering: *REQUIRED FOR SYSTEM-WIDE CHANGES* Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? Include a link to the releng issue. The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication.
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	Bugzilla trackers	Bugzilla trackers
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	Bugzilla trackers	Rastreadores Bugzilla
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Policies and guidelines: Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. Where possible, file a pull request against the appropriate policy documents _before submitting the change proposal_. That way, the community and FESCo can evaluate the specific changes required.	Policies and guidelines: Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. Where possible, file a pull request against the appropriate policy documents _before submitting the change proposal_. That way, the community and FESCo can evaluate the specific changes required.
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Trademark approval: If your Change may require trademark approval (for example, if it is a new Spin), file a https://pagure.io/Fedora-Council/tickets/issues[Fedora Council ticket] requesting trademark approval.	Trademark approval: If your Change may require trademark approval (for example, if it is a new Spin), file a https://pagure.io/Fedora-Council/tickets/issues[Fedora Council ticket] requesting trademark approval.
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	Approved change proposals will have Bugzilla issues created by the Program Manager. The following status fields should be used to reflect the status of the change:	Approved change proposals will have Bugzilla issues created by the Program Manager. The following status fields should be used to reflect the status of the change:
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	Approved change proposals will have Bugzilla issues created by the Program Manager. The following status fields should be used to reflect the status of the change:	Las propuestas de cambio aprobadas tendrán cuestiones en Bugzilla creadas por el Administrador del Programa. Los siguientes campos de estado deben ser usados para reflejar el estado del cambio:
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	Bugzilla tracker statuses	Bugzilla tracker statuses
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	Bugzilla tracker statuses	Estados del rastreador Bugzilla
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Alignment with Objectives: Does your proposal align with the xref:project::objectives.adoc[current Fedora Objectives]? This will not apply to many Changes, but it's important to consider when proposing a Change. Being out of alignment isn't an automatic rejection, it's just one more aspect to consider.	Alignment with Objectives: Does your proposal align with the xref:project::objectives.adoc[current Fedora Objectives]? This will not apply to many Changes, but it's important to consider when proposing a Change. Being out of alignment isn't an automatic rejection, it's just one more aspect to consider.
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Upgrade/compatibility impact	Upgrade/compatibility impact
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	|BZ Status|Meaning |ASSIGNED|Change approved by FESCo |MODIFIED|Change is code complete enough to be testable |ON_QA|Change is 100% code complete	|BZ Status|Meaning |ASSIGNED|Change approved by FESCo |MODIFIED|Change is code complete enough to be testable |ON_QA|Change is 100% code complete
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	|BZ Status|Meaning |ASSIGNED|Change approved by FESCo |MODIFIED|Change is code complete enough to be testable |ON_QA|Change is 100% code complete	|Estado BZSignificado |ASSIGNED|Cambio aprobado por FESCo |MODIFIED|El cambio tiene el código lo suficientemente completo para poder ser probado |ON_QA|El cambio tiene el 100% del código completo
	fedora-docs-l10n/program_management/master/pages/changes_policy — English	Do not close tracking bugs when a change is complete. The Program Manager will do that as part of release housekeeping.	Do not close tracking bugs when a change is complete. The Program Manager will do that as part of release housekeeping.
	fedora-docs-l10n/program_management/master/pages/changes_policy — Spanish	Do not close tracking bugs when a change is complete. The Program Manager will do that as part of release housekeeping.	No cierre el rastreador de errores cuando se complete el cambio. El Administrador del Programa lo hará como parte de la gestión interna de la liberación.
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	*REQUIRED FOR SYSTEM-WIDE CHANGES* What happens to systems that have had a previous versions of Fedora Linux installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported?	*REQUIRED FOR SYSTEM-WIDE CHANGES* What happens to systems that have had a previous versions of Fedora Linux installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported?
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	How To Test	How To Test
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	*REQUIRED FOR SYSTEM-WIDE CHANGES* This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.	*REQUIRED FOR SYSTEM-WIDE CHANGES* This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.	Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	A good "how to test" should answer these four questions:	A good "how to test" should answer these four questions:
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	What special hardware / data / etc. is needed (if any)?	What special hardware / data / etc. is needed (if any)?
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	How do I prepare my system to test this change? What packages need to be installed, config files edited, etc.?	How do I prepare my system to test this change? What packages need to be installed, config files edited, etc.?
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	What specific actions do I perform to check that the change is working like it's supposed to?	What specific actions do I perform to check that the change is working like it's supposed to?
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	What are the expected results of those actions?	What are the expected results of those actions?
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	User Experience	User Experience
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	If this change proposal is noticeable by users, how will their experiences change as a result?	If this change proposal is noticeable by users, how will their experiences change as a result?
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	This section partially overlaps with the Benefit to Fedora section above. This section should be primarily about the User Experience, written in a way that does not assume deep technical knowledge. More detailed technical description should be left for the Benefit to Fedora section.	This section partially overlaps with the Benefit to Fedora section above. This section should be primarily about the User Experience, written in a way that does not assume deep technical knowledge. More detailed technical description should be left for the Benefit to Fedora section.
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Describe what Users will see or notice, for example:	Describe what Users will see or notice, for example:
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Packages are compressed more efficiently, making downloads and upgrades faster by 10%.	Packages are compressed more efficiently, making downloads and upgrades faster by 10%.
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Kerberos tickets can be renewed automatically. Users will now have to authenticate less and become more productive. Credential management improvements mean a user can start their work day with a single sign on and not have to pause for reauthentication during their entire day.	Kerberos tickets can be renewed automatically. Users will now have to authenticate less and become more productive. Credential management improvements mean a user can start their work day with a single sign on and not have to pause for reauthentication during their entire day.
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	LibreOffice is one of the most commonly installed applications on Fedora Linux and it is now available by default to help users "hit the ground running".	LibreOffice is one of the most commonly installed applications on Fedora Linux and it is now available by default to help users "hit the ground running".
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora Linux users being the most relaxed users of any operating system.	Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora Linux users being the most relaxed users of any operating system.
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Dependencies	Dependencies
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	*REQUIRED FOR SYSTEM-WIDE CHANGES* What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)?	*REQUIRED FOR SYSTEM-WIDE CHANGES* What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)?
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Contingency Plan	Contingency Plan
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	*REQUIRED FOR SYSTEM-WIDE CHANGES* If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If your feature is not completed in time, we want to assure others that other parts of Fedora will not be in jeopardy.	*REQUIRED FOR SYSTEM-WIDE CHANGES* If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If your feature is not completed in time, we want to assure others that other parts of Fedora will not be in jeopardy.
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	A contingency plan should include:	A contingency plan should include:
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Contingency mechanism: (What to do? Who will do it?)	Contingency mechanism: (What to do? Who will do it?)
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Contingency deadline: When is the last time the contingency mechanism can be put in place?	Contingency deadline: When is the last time the contingency mechanism can be put in place?
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	The contingency deadline will most likely be the beta freeze. In some cases, it may be more appropriate to set it to the start of the mass rebuild or branch day. Rarely, you can use final freeze, but this should only be used for Changes that are trivially-revertable.	The contingency deadline will most likely be the beta freeze. In some cases, it may be more appropriate to set it to the start of the mass rebuild or branch day. Rarely, you can use final freeze, but this should only be used for Changes that are trivially-revertable.
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Documentation	Documentation
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	*REQUIRED FOR SYSTEM-WIDE CHANGES* Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved.	*REQUIRED FOR SYSTEM-WIDE CHANGES* Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved.
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	Release Notes	Release Notes
	fedora-docs-l10n/program_management/master/pages/changes_guide — English	The Fedora Linux Release Notes inform end-users about what is new in the release. Examples of xref:release-notes::index.adoc[past release notes] are on Fedora Docs. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this change, indicate them here. A link to upstream documentation will often satisfy this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release.	The Fedora Linux Release Notes inform end-users about what is new in the release. Examples of xref:release-notes::index.adoc[past release notes] are on Fedora Docs. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this change, indicate them here. A link to upstream documentation will often satisfy this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release.

• 15 / 15
  / 15