fedora-docs-l10n/council/master/pages/policy/edition-promotion-policy — Portuguese (Portugal) @ Fedora Weblate: History

Zen

	English	Portuguese (Portugal)	Actions
	Scope of hardware support (including anything that is explicitly unsupported).
	Produced deliverables, and whether or not they should be considered release blocking.
	The candidate Edition may have a technical specification (link:{FWIKI}/Workstation/Technical_Specification[example]) that provides additional detail about the specific features described in the PRD.
	It is helpful to have someone on the team assigned to handle the bureaucratic tasks.
	Process	Processo
	When all of the prerequisites have been met and approved by the {team_name}, the team submits promotion as a System-Wide Change. This ensures that Release Engineering, FESCo, and the community at large have the opportunity to provide input. It also implies that the promotion may be delayed to the next release if the appropriate supporting pieces are not in place by the Beta or GA freezes.
	Prior to submitting the Change proposal, the following tasks should be completed:
	Approval from the {team_name}. File a ticket and participate in related discussion.
	Review test cases and release criteria with the Quality Team. The Quality Team will draft test cases and release criteria based on the PRD. However, the Edition team must verify that these are valid. The Edition team may choose to assign a person to be the liaison with the Quality Team.
	Work with Release Engineering. The Edition team should work with release engineering on how they are planning on composing the new edition, release process, mirrors sync locations, any changes needed to koji, bodhi or autosigning.
	After the change proposal is approved, the following additional tasks should be completed no later than the Beta freeze, which should be considered the contingency deadline for the change. Note that these tasks should be started as early as possible.
	Request design deliverables. If customized graphics for the website, stickers, et cetera are needed, the Edition team should contact the Design Team as soon as possible.
	Provide updated website content. The Edition team should send text, graphics, and screenshots to the Websites & Apps Team as soon as possible to ensure fedoraproject.org will be up-to-date on release day.
	Notify Documentation and Translation teams. The Edition team should let the Documentation team know of any updates or new documentation required. The Edition team should also inform the Translation team of incoming website and documentation updates so they can prepare to translate it in advance of the release.
	Provide marketing blurbs. The Edition team should send basic promotional text to the Marketing and Magazine teams. This will allow the release announcement, et cetera to include meaningful information about the new Edition. The Edition team may consider writing one or several full Fedora Magazine articles in support of the Edition.
	History	Histórico
	This policy was approved in link:{team_issue_tracker}/issue/296[{team_name} ticket #296].	Esta política foi aprovada no https://pagure.io/Fedora-Council/tickets/issue/296['Conselho', pedido #296].
	The policy was amended in October, 2024 to relax the "distinct" requirement in link:{team_issue_tracker}/issue/507[{team_name} ticket #507].	Esta política foi aprovada no https://pagure.io/Fedora-Council/tickets/issue/296['Conselho', pedido #296].

Loading…

mansil

Translation added

English

Portuguese (Portugal) 9 characters edited Current translation Translated

2 years ago

None

Suggestion added

English

Portuguese (Portugal) 8 characters edited

3 years ago

Browse all string changes

Things to check

Suggestions

There is 1 suggestion for this string.

View

Inconsistent

This string has more than one translation in this project or is untranslated in some components.

Reset

Glossary

English	Portuguese (Portugal)
No related strings found in the glossary.

String information

Source string description

type: Title ==

Flags

no-wrap

Source string location

pages/policy/edition-promotion-policy.adoc:80

String age

3 years ago

Last updated

a year ago

Source string age

3 years ago

Translation file

po/pt_PT/master/pages/policy/edition-promotion-policy.po, string 32

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.