Translation

(itstool) path: sect2/para
English
Following the code slush, the next phase of the release cycle is the code freeze. This is the point at which all commits to the stable branch require explicit approval from the FreeBSD Release Engineering Team. This is enforced by pre-commit hooks in the Subversion repository by editing <filename>base/svnadmin/conf/approvers</filename> to include a regular expression matching the <literal>stable/<replaceable>12</replaceable>/</literal> branch for the release:
467/4630
Context English Portuguese (Brazil) State
This section describes the general procedures of the FreeBSD release cycle from an extablished <literal>stable/</literal> branch. Esta seção descreve os procedimentos gerais do ciclo de release do FreeBSD a partir de uma branch <literal>stable/</literal>.
FreeBSD <literal>stable</literal> Branch Code Slush Code Slush da branch <literal>stable</literal> do FreeBSD
In preparation for the code freeze on a <literal>stable</literal> branch, several files need to be updated to reflect the release cycle is officially in progress. These files are all relative to the top-most level of the stable branch: Na preparação para o code freeze em uma branch <literal>stable</literal>, vários arquivos precisam ser atualizados para refletir o ciclo de release que está oficialmente em andamento. Esses arquivos são todos relativos ao nível mais alto da branch stable:
<filename>sys/conf/newvers.sh</filename> <filename>sys/conf/newvers.sh</filename>
Update the <varname>BRANCH</varname> value to reflect <literal>PRERELEASE</literal> Atualize o valor da <varname>BRANCH</varname> para refletir <literal>PRERELEASE</literal>
<filename>Makefile.inc1</filename> <filename>Makefile.inc1</filename>
Update <varname>TARGET_TRIPLE</varname> Atualize o <varname>TARGET_TRIPLE</varname>
<filename>lib/clang/llvm.build.mk</filename> <filename>lib/clang/llvm.build.mk</filename>
Update <varname>OS_VERSION</varname> Atualize o <varname>OS_VERSION</varname>
<filename>Makefile.libcompat</filename> <filename>Makefile.libcompat</filename>
Update <literal>LIB32CPUFLAGS</literal> Atualize o <literal>LIB32CPUFLAGS</literal>
<filename>gnu/usr.bin/groff/tmac/mdoc.local.in</filename> <filename>gnu/usr.bin/groff/tmac/mdoc.local.in</filename>
Add a new <literal>.ds</literal> entry for the FreeBSD version, and update <varname>doc-default-operating-system</varname> (FreeBSD 11.x and earlier only) Adiciona uma nova entrada <literal>.ds</literal> para a versão do FreeBSD, e atualiza <varname>doc-default-operating-system</varname> (FreeBSD 11.x e anteriores apenas)
In the <literal>doc</literal> repository, also update <filename>head/en_US.ISO8859-1/htdocs/releases/<replaceable>12.0</replaceable>R/Makefile.hardware</filename>, switching the value of <varname>_BRANCH</varname> to <literal>BETA<replaceable>X</replaceable></literal>, <literal>RC<replaceable>X</replaceable></literal>, or <literal>RELEASE</literal>, respectively. No repositório <literal>doc</literal>, atualize também <filename>head/pt_BR.ISO8859-1/htdocs/releases/<replaceable>12.0</replaceable>R/Makefile.hardware</filename>, alternando o valor de <varname>_BRANCH</varname> para <literal>BETA<replaceable>X</replaceable></literal>, <literal>RC<replaceable>X</replaceable></literal> ou <literal>RELEASE</literal>, respectivamente.
FreeBSD <literal>BETA</literal> Builds Builds <literal>BETA</literal> do FreeBSD
Following the code slush, the next phase of the release cycle is the code freeze. This is the point at which all commits to the stable branch require explicit approval from the FreeBSD Release Engineering Team. This is enforced by pre-commit hooks in the Subversion repository by editing <filename>base/svnadmin/conf/approvers</filename> to include a regular expression matching the <literal>stable/<replaceable>12</replaceable>/</literal> branch for the release: Após o code slush, a próxima fase do ciclo de release é o code freeze. Este é o ponto no qual todos os commits para a branch stable requerem aprovação explícita da Equipe de Engenharia de Release do FreeBSD. Isto é reforçado por hooks de pré-commit no repositório Subversion editando <filename>base/svnadmin/conf/approvers</filename> para incluir uma expressão regular que coincida com a branch <literal>stable/<replaceable>12</replaceable>/</literal> para a release:
^/<literal>stable/<replaceable>12</replaceable>/</literal> re
^/<literal>releng/<replaceable>12.0</replaceable>/</literal> re
^/<literal>stable/<replaceable>12</replaceable>/</literal> re
^/<literal>releng/<replaceable>12.0</replaceable>/</literal> re
There are two general exceptions to requiring commit approval during the release cycle. The first is any change that needs to be committed by the Release Engineer in order to proceed with the day-to-day workflow of the release cycle, the other is security fixes that may occur during the release cycle. Há duas exceções gerais para exigir aprovação de commit durante o ciclo de release. A primeira é qualquer alteração que precise ser "committed" pelo Engenheiro de Release para continuar com o fluxo de trabalho diário do ciclo de lançamento, e a outra são as correções de segurança que podem ocorrer durante o ciclo de lançamento.
Once the code freeze is in effect, the next build from the branch is labeled <literal>BETA1</literal>. This is done by updating the <varname>BRANCH</varname> value in <filename>sys/conf/newvers.sh</filename> from <literal>PRERELEASE</literal> to <literal>BETA1</literal>. Quando o code freeze estiver em vigor, a próxima construção da branch será rotulada como <literal>BETA1</literal>. Isso é feito atualizando o valor de <varname>BRANCH</varname> em <filename>sys/conf/newvers.sh</filename> de <literal>PRERELEASE</literal> para <literal>BETA1</literal>.
Once this is done, the first set of <literal>BETA</literal> builds are started. Subsequent <literal>BETA</literal> builds do not require updates to any files other than <filename>sys/conf/newvers.sh</filename>, incrementing the <literal>BETA</literal> build number. Feito isso, o primeiro conjunto de builds <literal>BETA</literal> é iniciado. Builds <literal>BETA</literal> subseqüentes não requerem atualizações em nenhum arquivo diferente do <filename>sys/conf/newvers.sh</filename>, incrementando o número de compilação da versão <literal>BETA</literal>.
Creating the <literal>releng/<replaceable>12.0</replaceable>/</literal> Branch Criando a branch <literal>releng/<replaceable>12.0</replaceable>/</literal>
When the first <literal>RC</literal> (Release Candidate) build is ready to begin, the <literal>releng/</literal> branch is created. This is a multi-step process that must be done in a specific order, in order to avoid anomalies such as overlaps with <varname>__FreeBSD_version</varname> values, for example. The paths listed below are relative to the repository root. The order of commits and what to change are: Quando a primeira construção <literal>RC</literal> (Release Candidate) está pronta para começar, a branch <literal>releng/</literal> é criada. Este é um processo de várias etapas que deve ser feito em uma ordem específica, a fim de evitar anomalias, como sobreposições com valores de <varname>__ FreeBSD_version</varname>, por exemplo. Os caminhos listados abaixo são relativos ao repositório raiz. A ordem dos commits e o que mudar são:
<prompt>%</prompt> <userinput>svn cp ^/<literal>stable/<replaceable>12</replaceable>/</literal> <literal>releng/<replaceable>12.0</replaceable>/</literal></userinput> <prompt>%</prompt> <userinput>svn cp ^/<literal>stable/<replaceable>12</replaceable>/</literal> <literal>releng/<replaceable>12.0</replaceable>/</literal></userinput>
<filename>releng/<replaceable>12.0</replaceable>/sys/conf/newvers.sh</filename> <filename>releng/<replaceable>12.0</replaceable>/sys/conf/newvers.sh</filename>
Change <literal>BETA<replaceable>X</replaceable></literal> to <literal>RC1</literal> Altere <literal>BETA<replaceable>X</replaceable></literal> para <literal>RC1</literal>
<filename>releng/<replaceable>12.0</replaceable>/sys/sys/param.h</filename> <filename>releng/<replaceable>12.0</replaceable>/sys/sys/param.h</filename>
Update <varname>__FreeBSD_version</varname> Atualize o <varname>__ FreeBSD_version</varname>
<filename>releng/<replaceable>12.0</replaceable>/etc/pkg/FreeBSD.conf</filename> <filename>releng/<replaceable>12.0</replaceable>/etc/pkg/FreeBSD.conf</filename>
Replace <literal>latest</literal> with <literal>quarterly</literal> as the default package repository location Substitua <literal>latest</literal> por <literal>quarterly</literal> (trimestral) como a localização padrão do repositório de pacotes
<filename>releng/<replaceable>12.0</replaceable>/release/pkg_repos/release-dvd.conf</filename> <filename>releng/<replaceable>12.0</replaceable>/release/pkg_repos/release-dvd.conf</filename>
Update <literal>BETA<replaceable>X</replaceable></literal> with <literal>PRERELEASE</literal> Atualize <literal>BETA<replaceable>X</replaceable></literal> para <literal>PRERELEASE</literal>

Loading…

Following the code slush, the next phase of the release cycle is the code freeze. This is the point at which all commits to the stable branch require explicit approval from the FreeBSD Release Engineering Team. This is enforced by pre-commit hooks in the Subversion repository by editing <filename>base/svnadmin/conf/approvers</filename> to include a regular expression matching the <literal>stable/<replaceable>12</replaceable>/</literal> branch for the release:
Após o code slush, a próxima fase do ciclo de release é o code freeze. Este é o ponto no qual todos os commits para a branch stable requerem aprovação explícita da Equipe de Engenharia de Release do FreeBSD. Isto é reforçado por hooks de pré-commit no repositório Subversion editando <filename>base/svnadmin/conf/approvers</filename> para incluir uma expressão regular que coincida com a branch <literal>stable/<replaceable>12</replaceable>/</literal> para a release:
a month ago
Browse all component changes

Glossary

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

Source information

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