The translation is temporarily closed for contributions due to maintenance, please come back later.

Translation

(itstool) path: sect1/para
English
Although a general rule to wait a minimum of three days before merging from <literal>head/</literal>, there are a few special circumstances where an immediate merge may be necessary, such as a critical security fix, or a bug fix that directly inhibits the release build process.
348/2780 · 278
Context English Portuguese (Brazil) State
_ translator-credits Edson Brandi, ebrandi@FreeBSD.org, 2018
Lucas Andrade, slucasandrade@protonmail.ch, 2018
André Franciosi, andre@franciosi.org, 2018
Vinícius Zavam, egypcio@googlemail.com, 2018
Silvio Ap Silva, contato@kanazuchi.com, 2018
Danilo G. Baio, dbaio@FreeBSD.org, 2020
FreeBSD Release Engineering Engenharia de Release do FreeBSD
<email>gjb@FreeBSD.org</email> <email>gjb@FreeBSD.org</email>
<personname> <firstname>Glen</firstname> <surname>Barber</surname> </personname> <affiliation> <orgname class="nonprofit"> <link xlink:href="https://www.freebsdfoundation.org">The FreeBSD Foundation</link></orgname> </affiliation> <affiliation> <orgname> <link xlink:href="https://www.netgate.com">Rubicon Communications, LLC (Netgate)</link></orgname> <_:address-1/> </affiliation> <personname> <firstname>Glen</firstname> <surname>Barber</surname> </personname> <affiliation> <orgname class="nonprofit"> <link xlink:href="https://www.freebsdfoundation.org">The FreeBSD Foundation</link></orgname> </affiliation> <affiliation> <orgname> <link xlink:href="https://www.netgate.com">Rubicon Communications, LLC (Netgate)</link></orgname> <_:address-1/> </affiliation>
FreeBSD is a registered trademark of the FreeBSD Foundation. FreeBSD is a registered trademark of the FreeBSD Foundation.
Intel, Celeron, Centrino, Core, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Intel, Celeron, Centrino, Core, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the <quote>™</quote> or the <quote>®</quote> symbol. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the <quote>™</quote> or the <quote>®</quote> symbol.
$FreeBSD: head/en_US.ISO8859-1/articles/freebsd-releng/article.xml 54556 2020-09-30 15:54:17Z gjb $ $FreeBSD: head/en_US.ISO8859-1/articles/freebsd-releng/article.xml 54556 2020-09-30 15:54:17Z gjb $
This article describes the release engineering process of the FreeBSD Project. Este artigo descreve o processo por trás do modelo de engenharia de release adotado pelo Projeto FreeBSD.
Introduction to the FreeBSD Release Engineering Process Introdução ao Processo de Engenharia de Release do FreeBSD
Development of FreeBSD has a very specific workflow. In general, all changes to the FreeBSD base system are committed to the <literal>head/</literal> branch, which reflects the top of the source tree. O desenvolvimento do FreeBSD segue um fluxo muito específico. Em geral, todas as mudanças no sistema base do FreeBSD são feitas em uma branch chamada <literal>head/</literal>, a qual reflete o topo da árvore de código fonte.
After a reasonable testing period, changes can then be merged to the <literal>stable/</literal> branches. The default minimum timeframe before merging to <literal>stable/</literal> branches is three (3) days. Após um período razoável de testes, as alterações podem ser fundidas na branch <literal>stable/</literal>. O período de tempo mínimo padrão antes da fusão das alterações na branch <literal>stable/</literal> é de três (3) dias.
Although a general rule to wait a minimum of three days before merging from <literal>head/</literal>, there are a few special circumstances where an immediate merge may be necessary, such as a critical security fix, or a bug fix that directly inhibits the release build process. Embora seja uma regra geral esperar pelo menos três (3) dias antes de fundir o código produzido na branch <literal>head/</literal>, existem algumas circunstâncias especiais em que uma fusão imediata pode ser necessária, tal como uma correção de segurança crítica ou uma correção de bug que inibe diretamente o processo de compilação de uma release.
After several months, and the number of changes in the <literal>stable/</literal> branch have grown significantly, it is time to release the next version of FreeBSD. These releases have been historically referred to as <quote>point</quote> releases. Após vários meses, quando o número de mudanças na branch <literal>stable/</literal> cresceu significativamente, é hora de lançar a próxima versão do FreeBSD. Essas versões foram historicamente chamadas de <quote>point</quote> releases.
In between releases from the <literal>stable/</literal> branches, approximately every two (2) years, a release will be cut directly from <literal>head/</literal>. These releases have been historically referred to as <quote>dot-zero</quote> releases. Entre as versões das branches <literal>stable/</literal>, aproximadamente a cada dois (2) anos, uma nova versão é criada vinda diretamente da branch <literal>head/</literal>. Essas versões foram historicamente chamadas de versões <quote>dot-zero</quote>.
This article will highlight the workflow and responsibilities of the FreeBSD Release Engineering Team for both <quote>dot-zero</quote> and <quote>point</quote>' releases. Este artigo irá destacar o fluxo de trabalho e as responsabilidades da Equipe de Engenharia de Release do FreeBSD para ambas as versões <quote>dot-zero</quote> e <quote>point release</quote>.
The following sections of this article describe: As seções a seguir deste artigo descrevem:
General information and preparation before starting the release cycle. Informações gerais e preparativos antes de iniciar o ciclo de release.
Website Changes During the Release Cycle Alterações na Página Web Durante o Ciclo de Release
Terminology and general information, such as the <quote>code slush</quote> and <quote>code freeze</quote>, used throughout this document. Terminologia e informações gerais, como <quote>code slush</quote> e <quote>code freeze</quote>, usadas por todo este documento.
The Release Engineering process for a <quote>dot-zero</quote> release. O processo de Engenharia de Release para uma versão <quote>dot-zero</quote>.
The Release Engineering process for a <quote>point</quote> release. O processo de Engenharia de Release para uma versão <quote>point release</quote>.
Information related to the specific procedures to build installation medium. Informações relacionadas aos procedimentos específicos para construir o meio de instalação.
Procedures to publish installation medium. Procedimentos para publicar um meio de instalação.
Wrapping up the release cycle. Encerrando o ciclo de release.
General Information and Preparation Informação Geral e Preparativos
Approximately two months before the start of the release cycle, the FreeBSD Release Engineering Team decides on a schedule for the release. The schedule includes the various milestone points of the release cycle, such as freeze dates, branch dates, and build dates. For example: Aproximadamente dois meses antes do início do ciclo de vida de uma nova versão, a Equipe de Engenharia de Release do FreeBSD decide sobre um cronograma para o seu lançamento. A programação inclui os vários milestones do ciclo de release, como datas de congelamento, datas para as branches e datas para compilação do código. Por exemplo:
Milestone Milestone

Loading…

User avatar dbaio

Translation changed

FreeBSD Doc (Archived) / articles_freebsd-releng — Portuguese (Brazil)

Although a general rule to wait a minimum of three days before merging from <literal>head/</literal>, there are a few special circumstances where an immediate merge may be necessary, such as a critical security fix, or a bug fix that directly inhibits the release build process.
Embora seja uma regra geral esperar pelo menos três (3) dias antes de fundir o código produzido na branch <literal>head/</literal>, existem algumas circunstâncias especiais em que uma fusão imediata pode ser necessária, tal como uma correção de segurança crítica ou uma correção de bug que inibe diretamente o processo de compilação de uma release.
3 months ago
Browse all component changes

Glossary

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

Source information

Source string comment
(itstool) path: sect1/para
Source string location
article.translate.xml:83
String age
a year ago
Source string age
a year ago
Translation file
articles/pt_BR/freebsd-releng.po, string 13