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

Translation

Source change

English type: Plain text

Portuguese (Brazil)

Needs editing

Skip

	English	Portuguese (Brazil)	Actions
	Process for promoting a Fedora deliverable to Edition
	Fedora Editions are curated sets of packages, guidelines and configuration, and artifacts built from those pieces, that address a specific, targeted use-case. The Editions are the primary Fedora outputs that most Fedora users are encouraged to use and directed towards through the download site.	As Edições do Fedora são conjuntos selecionados de pacotes, diretrizes e configurações, bem como artefatos construídos a partir desses componentes, que atendem a um caso de uso específico e direcionado. As Edições são as principais saídas do Fedora, e a maioria dos usuários do Fedora são incentivados a usá-las e são direcionados a elas por meio do site de download.
	This document describes the process for promoting an existing Fedora deliverable to Edition status.
	What makes an "Edition"?
	A Fedora Edition:	Uma Edição Fedora:
	addresses a distinct, relevant, and broad use-case or user-base that a Fedora Edition is not currently serving;
	is a long term investment for the Fedora Project; and
	is consistent with all of Fedora's Four Foundations.
	Prerequisites	Pré-Requisitos
	The candidate Edition must be backed by a team that holds regular public meetings.
	The candidate Edition must get trademark approval from the {team_name}. If this includes a name change or a new name (e.g. “Fedora Bilverslue”), plan time for legal review.	A Edição candidata deve obter a aprovação de marca registrada do Conselho do Fedora. Se isso envolver uma mudança de nome ou um novo nome (por exemplo, "Fedora Bilverslue"), planeje um tempo para a revisão legal.
	The candidate Edition must have a product requirements document (PRD) (link:{FWIKI}/Workstation/Workstation_PRD[example]). The PRD is used by other teams within Fedora. For example, the Quality Team uses it to develop release criteria and test cases and the Marketing Team uses it to develop collateral and positioning. The PRD must include:	A Edição candidata deve ter um Documento de Requisitos do Produto (PRD) (https://fedoraproject.org/wiki/Workstation/Workstation_PRD[exemplo]). O PRD é usado por outras equipes dentro do Fedora (por exemplo: a equipe de QA o usa para desenvolver critérios de lançamento e casos de teste, a equipe de marketing o usa para desenvolver material promocional e posicionamento). O PRD deve incluir:
	Market target, including key use cases and personas.
	Core services and features.
	Core applications.	Aplicações Core
	Unique policies for installation, updates, etc.
	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.

Loading…

anonymous

Suggestion added

English

Portuguese (Brazil) 0 characters edited Current translation

6 months ago

None

String updated in the repository

English

Portuguese (Brazil) 15 characters edited Current translation Needs editing

6 months ago

None

Source string changed

English 1 character edited

6 months ago

Browse all string changes

Things to check

Suggestions

There is 1 suggestion for this string.

View

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Glossary

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

String information

Source string description

type: Plain text

Source string location

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

String age

6 months ago

Last updated

6 months ago

Source string age

6 months ago

Translation file

po/pt_BR/master/pages/policy/edition-promotion-policy.po, string 15