The translation is temporarily closed for contributions due to maintenance, please come back later.
Context English Portuguese (Brazil) State
_ translator-credits Wendell Borges, perlporter@gmail.com, 2018
Silvio Ap Silva, contato@kanazuchi.com, 2018
Edson Brandi, ebrandi@FreeBSD.org, 2018
Danilo G Baio, dbaio@FreeBSD.org, 2018

<email>murray@FreeBSD.org</email>
<otheraddr xlink:href="https://people.FreeBSD.org/~murray/">https://people.FreeBSD.org/~murray/</otheraddr>

<email>murray@FreeBSD.org</email>
<otheraddr xlink:href="https://people.FreeBSD.org/~murray/">https://people.FreeBSD.org/~murray/</otheraddr>
<personname> <firstname>Murray</firstname> <surname>Stokely</surname> </personname> <_:personblurb-1/> <affiliation> <_:address-2/> </affiliation> <personname> <firstname>Murray</firstname> <surname>Stokely</surname> </personname> <_:personblurb-1/> <affiliation> <_:address-2/> </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.
This paper describes the approach used by the FreeBSD release engineering team to make production quality releases of the FreeBSD Operating System. It details the methodology used for the official FreeBSD releases and describes the tools available for those interested in producing customized FreeBSD releases for corporate rollouts or commercial productization. Este artigo descreve a abordagem usada pela equipe de engenharia de release do FreeBSD para produzir versões do Sistema Operacional FreeBSD com qualidade de produção. Ele detalha a metodologia utilizada para as versões oficiais do FreeBSD e descreve as ferramentas disponíveis para aqueles interessados em produzir versões customizadas do FreeBSD para uso corporativo ou para uso em produtos comerciais.
Subversion, <uri xlink:href="http://subversion.apache.org">http://subversion.apache.org</uri> Subversion, <uri xlink:href="http://subversion.apache.org">http://subversion.apache.org</uri>
The rapid pace of <systemitem>FreeBSD</systemitem> development makes the main development branch unsuitable for the everyday use by the general public. In particular, stabilizing efforts are required for polishing the development system into a production quality release. To solve this conflict, development continues on several parallel tracks. The main development branch is the <emphasis>HEAD</emphasis> or <emphasis>trunk</emphasis> of our Subversion tree, known as <quote>FreeBSD-CURRENT</quote> or <quote>-CURRENT</quote> for short. O ritmo acelerado de desenvolvimento do <systemitem>FreeBSD</systemitem> torna a principal branch de desenvolvimento inadequada para o uso diário pelo público em geral. Em particular, são necessários esforços de estabilização para polir o sistema de desenvolvimento em uma release de qualidade apropriada para uso em ambiente produtivo. Para resolver este conflito, o desenvolvimento continua em várias trilhas paralelas. A principal branch de desenvolvimento é a <emphasis>HEAD</emphasis> ou <emphasis>trunk</emphasis> da nossa árvore do Subversion, conhecida como <quote>FreeBSD-CURRENT</quote> ou <quote>-CURRENT</quote> quando abreviado.
buildworld buildworld
Release Process Processos de Release (Versão)
<acronym>MFC</acronym> stands for <quote>Merge From CURRENT</quote> and it describes the process of merging a tested change from our -CURRENT development branch to our -STABLE branch. Project policy requires any change to be first applied to trunk, and merged to the -STABLE branches after sufficient external testing was done by -CURRENT users (developers are expected to extensively test the change before committing to -CURRENT, but it is impossible for a person to exercise all usages of the general-purpose operating system). Minimal MFC period is 3 days, which is typically used only for trivial or critical bugfixes. <acronym>MFC</acronym> significa <quote>Merge From CURRENT</quote> e descreve o processo de fusão de uma alteração testada de nossa branch de desenvolvimento -CURRENT com a nossa branch -STABLE. A política do projeto requer que qualquer mudança seja aplicada pela primeira vez ao trunk, e aplicada às branches -STABLE após testes externos suficientes serem feitos pelos usuários no -CURRENT (espera-se que os desenvolvedores testem extensivamente a mudança antes de enviarem a mesma para o -CURRENT, mas é impossível para uma pessoa exercer todos os usos de um sistema operacional de propósito geral). O período mínimo de MFC é de 3 dias, que normalmente é usado apenas para correções de bugs triviais ou críticas.
The layout of FreeBSD branches in Subversion is described in the <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/committers-guide/subversion-primer.html#subversion-primer-base-layout">Committer's Guide</link>. The first step in creating a branch is to identify the revision of the <literal>stable/<replaceable>X</replaceable></literal> sources that you want to branch <emphasis>from</emphasis>. O layout das branchs do FreeBSD no Subversion é descrito no <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/committers-guide/subversion-primer.html#subversion-primer-base-layout">Guia do Commiter</link>. O primeiro passo na criação de uma branch é identificar a revisão do código fonte do <literal>stable/<replaceable>X</replaceable></literal>, a partir do qual você deseja criar a nova <emphasis>branch</emphasis>.
<prompt>#</prompt> <userinput>svn log -v $FSVN/stable/9</userinput> <prompt>#</prompt> <userinput>svn log -v $FSVN/stable/9</userinput>
<prompt>#</prompt> <userinput>svn cp $FSVN/stable/9@REVISION $FSVN/releng/9.2</userinput> <prompt>#</prompt> <userinput>svn cp $FSVN/stable/9@REVISION $FSVN/releng/9.2</userinput>
<prompt>#</prompt> <userinput>svn co $FSVN/releng/9.2 src</userinput> <prompt>#</prompt> <userinput>svn co $FSVN/releng/9.2 src</userinput>
_ external ref='branches-head' md5='__failed__' external ref='branches-head' md5='__failed__'
_ external ref='branches-releng3' md5='__failed__' external ref='branches-releng3' md5='__failed__'
_ external ref='branches-releng4' md5='__failed__' external ref='branches-releng4' md5='__failed__'
_ external ref='branches-releng5' md5='__failed__' external ref='branches-releng5' md5='__failed__'
_ external ref='branches-releng6' md5='__failed__' external ref='branches-releng6' md5='__failed__'