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

Zen

	English	Portuguese (Brazil)	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.	A Edição candidata pode ter uma especificação técnica (https://fedoraproject.org/wiki/Workstation/Technical_Specification[exemplo]) que fornece detalhes adicionais sobre as características específicas descritas no 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.	Quando todos os pré-requisitos forem atendidos e aprovados pelo Conselho do Fedora, a equipe submete a promoção como uma Mudança de Alcance Geral (System-Wide Change). Isso garante que a Engenharia de Lançamento, o FESCo e a comunidade em geral tenham a oportunidade de fornecer feedback. Isso também implica que a promoção pode ser adiada para o próximo lançamento se as peças de suporte apropriadas não estiverem em vigor até as datas de congelamento Beta ou GA.
	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.	Revisar casos de teste e critérios de lançamento com o QA. A equipe de QA irá elaborar casos de teste e critérios de lançamento com base no PRD. No entanto, a equipe da Edição deve verificar se eles são válidos. A equipe da Edição pode escolher designar uma pessoa como ligação com a equipe de QA.
	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.	Trabalhar com a Engenharia de Lançamento. A equipe da Edição deve colaborar com a engenharia de lançamento para discutir como eles estão planejando compor a nova edição, o processo de lançamento, locais de sincronização de espelhos, quaisquer alterações necessárias no koji, bodhi ou na automação de assinatura (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.	Após a aprovação da proposta de mudança, as seguintes tarefas adicionais devem ser concluídas até a data de congelamento do Beta, que deve ser considerada a data limite de contingência para a mudança. Observe que essas tarefas devem ser iniciadas o mais cedo possível.
	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ória
	This policy was approved in link:{team_issue_tracker}/issue/296[{team_name} ticket #296].

Loading…

farribeiro Suggestion removed fedora-docs-l10n/council master/pages/policy/edition-promotion-policy Portuguese (Brazil)	English History Portuguese (Brazil) 8 characters edited Current translation História 8 months ago
farribeiro Translation added fedora-docs-l10n/council master/pages/policy/edition-promotion-policy Portuguese (Brazil)	English History Portuguese (Brazil) 8 characters edited Current translation Translated História 8 months ago
farribeiro Contributor joined fedora-docs-l10n/council master/pages/policy/edition-promotion-policy Portuguese (Brazil)	Contributor joined 8 months ago
None Suggestion added fedora-docs-l10n/council master/pages/policy/edition-promotion-policy Portuguese (Brazil)	English History Portuguese (Brazil) 8 characters edited Current translation História 3 years ago