Translation

(itstool) path: sect2/para
English
To request an Errata Notice after a release cycle has completed, a developer should fill out the <link xlink:href="https://www.freebsd.org/security/errata-template.txt">Errata Notice template</link>, in particular the <literal>Background</literal>, <literal>Problem Description</literal>, <literal>Impact</literal>, and if applicable, <literal>Workaround</literal> sections.
381/3740
Context English Portuguese (Brazil) State
Once all builds have finished, <filename class="directory">/snap/ftp/snapshots</filename>, or <filename class="directory">/snap/ftp/releases</filename> for a release, is polled by <systemitem>ftp-master</systemitem> using <application>rsync</application> to <filename class="directory">/archive/tmp/snapshots</filename> or <filename class="directory">/archive/tmp/releases</filename>, respectively. Uma vez que todas as compilações terminarem, <filename class="directory">/snap/ftp/snapshots</filename>, ou <filename class="directory">/snap/ftp/releases</filename> para uma versão, é pesquisado pelo <systemitem>ftp-master</systemitem> usando <application>rsync</application> para <filename class="directory">/archive/tmp/snapshots</filename> ou <filename class="directory">/archive/tmp/releases</filename>, respectivamente.
On <systemitem>ftp-master</systemitem> in the FreeBSD Project infrastructure, this step requires <literal>root</literal> level access, as this step must be executed as the <literal>archive</literal> user. No <systemitem>ftp-master</systemitem> na infraestrutura do Projeto FreeBSD, esta etapa requer acesso ao nível de <literal>root</literal>, já que esta etapa deve ser executada como o usuário <literal>archive</literal>.
Publishing FreeBSD Installation Media Publicando a Mídia de Instalação do FreeBSD
Once the images are staged in <filename class="directory">/archive/tmp/</filename>, they are ready to be made public by putting them in <filename class="directory">/archive/pub/FreeBSD</filename>. In order to reduce propagation time, <citerefentry><refentrytitle>pax</refentrytitle><manvolnum>1</manvolnum></citerefentry> is used to create hard links from <filename class="directory">/archive/tmp</filename> to <filename class="directory">/archive/pub/FreeBSD</filename>. Uma vez que as imagens são colocadas em <filename class="directory">/archive/tmp/</filename>, elas estão prontas para serem publicadas colocando-as em <filename class="directory">/archive/pub/FreeBSD</filename>. Para reduzir o tempo de propagação, o <citerefentry><refentrytitle>pax</refentrytitle><manvolnum>1</manvolnum></citerefentry> é usado para criar links físicos a partir de <filename class="directory">/archive/tmp</filename> para <filename class="directory">/archive/pub/FreeBSD</filename>.
In order for this to be effective, both <filename class="directory">/archive/tmp</filename> and <filename class="directory">/archive/pub</filename> must reside on the same logical filesystem. Para que isto seja efetivo, tanto o <filename class="directory">/archive/tmp</filename> quanto o <filename class="directory">/archive/pub</filename> devem residir no mesmo sistema de arquivos lógico.
There is a caveat, however, where <application>rsync</application> must be used after <citerefentry><refentrytitle>pax</refentrytitle><manvolnum>1</manvolnum></citerefentry> in order to correct the symbolic links in <filename class="directory">pub/FreeBSD/<replaceable>snapshots</replaceable>/ISO-IMAGES</filename> which <citerefentry><refentrytitle>pax</refentrytitle><manvolnum>1</manvolnum></citerefentry> will replace with a hard link, increasing the propagation time. Há uma ressalva, no entanto, em que o <application>rsync</application> deve ser usado após o <citerefentry><refentrytitle>pax</refentrytitle><manvolnum>1</manvolnum></citerefentry> para corrigir os links simbólicos no <filename class="directory">pub/FreeBSD/<replaceable>snapshots</replaceable>/ISO-IMAGES</filename> que o <citerefentry><refentrytitle>pax</refentrytitle><manvolnum>1</manvolnum></citerefentry> irá substituir por um hard link, aumentando o tempo de propagação.
As with the staging steps, this requires <literal>root</literal> level access, as this step must be executed as the <literal>archive</literal> user. Assim como nas etapas de preparação, isto requer acesso em nível de <literal>root</literal>, já que essa etapa deve ser executada como o usuário <literal>archive</literal>.
As the <literal>archive</literal> user: Como o usuário <literal>archive</literal>:
<prompt>%</prompt> <userinput>cd /archive/tmp/<replaceable>snapshots</replaceable></userinput>
<prompt>%</prompt> <userinput>pax -r -w -l . /archive/pub/FreeBSD/<replaceable>snapshots</replaceable></userinput>
<prompt>%</prompt> <userinput>/usr/local/bin/rsync -avH /archive/tmp/<replaceable>snapshots</replaceable>/* /archive/pub/FreeBSD/<replaceable>snapshots</replaceable>/</userinput> 		<prompt>%</prompt> <userinput>cd /archive/tmp/<replaceable>snapshots</replaceable></userinput>
<prompt>%</prompt> <userinput>pax -r -w -l . /archive/pub/FreeBSD/<replaceable>snapshots</replaceable></userinput>
<prompt>%</prompt> <userinput>/usr/local/bin/rsync -avH /archive/tmp/<replaceable>snapshots</replaceable>/* /archive/pub/FreeBSD/<replaceable>snapshots</replaceable>/</userinput>
Replace <replaceable>snapshots</replaceable> with <replaceable>releases</replaceable> as appropriate. Substitua os <replaceable>snapshots</replaceable> por <replaceable>releases</replaceable> conforme apropriado.
Wrapping up the Release Cycle Encerrando o Ciclo de Release
This section describes general post-release tasks. Esta seção descreve as tarefas gerais de pós-release.
Post-Release Errata Notices Avisos de Erratas de Pós-Release
As the release cycle approaches conclusion, it is common to have several <acronym>EN</acronym> (Errata Notice) candidates to address issues that were discovered late in the cycle. Following the release, the FreeBSD Release Engineering Team and the FreeBSD Security Team revisit changes that were not approved prior to the final release, and depending on the scope of the change in question, may issue an <acronym>EN</acronym>. A medida que o ciclo de release se aproxima da conclusão, é comum ter vários candidatos a <acronym>EN</acronym> (Aviso de Erratas) para abordar os problemas que foram descobertos ao final do ciclo. Após o lançamento, a Equipe de Engenharia de Release do FreeBSD e a Equipe de Segurança do FreeBSD reveem mudanças que não foram aprovadas antes da versão final, e dependendo do escopo da mudança em questão, podem emitir um <acronym>EN</acronym>.
The actual process of issuing <acronym>EN</acronym>s is handled by the FreeBSD Security Team. O processo atual de emissão de <acronym>EN</acronym>s é tratado pela Equipe de Segurança do FreeBSD.
To request an Errata Notice after a release cycle has completed, a developer should fill out the <link xlink:href="https://www.freebsd.org/security/errata-template.txt">Errata Notice template</link>, in particular the <literal>Background</literal>, <literal>Problem Description</literal>, <literal>Impact</literal>, and if applicable, <literal>Workaround</literal> sections. Para solicitar uma Errata após a conclusão de um ciclo de lançamento, o desenvolvedor deve preencher o <link xlink:href="https://www.freebsd.org/security/errata-template.txt">Template de Errata</link>>, em particular as seções <literal>Background</literal>, <literal>Problem Description</literal>, <literal>Impact</literal> e, se aplicável, as seções <literal>Workaround</literal>.
The completed Errata Notice template should be emailed together with either a patch against the <literal>releng/</literal> branch or a list of revisions from the <literal>stable/</literal> branch. O modelo de Errata preenchido deve ser enviado por e-mail juntamente com um patch na branch <literal>releng/</literal> ou uma lista de revisões da branch <literal>stable/</literal>.
For Errata Notice requests immediately following the release, the request should be emailed to both the FreeBSD Release Engineering Team and the FreeBSD Security Team. Once the <literal>releng/</literal> branch has been handed over to the FreeBSD Security Team as described in <xref linkend="releng-wrapup-handoff"/>, Errata Notice requests should be sent to the FreeBSD Security Team. Para pedidos de Errata imediatamente após o lançamento, o pedido deve ser enviado por e-mail à Equipe de Engenharia de Releases do FreeBSD e à Equipe de Segurança do FreeBSD. Depois que a branch <literal>releng/</literal> foi entregue à equipe de Segurança do FreeBSD, conforme descrito em <xref linkend="releng-wrapup-handoff"/>, as solicitações de Errata devem ser enviadas à equipe de Segurança do FreeBSD.
Handoff to the FreeBSD Security Team Entrega para a Equipe de Segurança do FreeBSD
Roughly two weeks following the release, the Release Engineer updates <filename>svnadmin/conf/approvers</filename> changing the approver column from <literal>re</literal> to <literal>(so|security-officer)</literal> for the <literal>releng/<replaceable>12.0</replaceable>/</literal> branch. Aproximadamente duas semanas após o lançamento, o Engenheiro de Release atualiza o <filename>svnadmin/conf/approvers</filename> alterando a coluna do aprovador de <literal>re</literal> para <literal>(so|security-officer)</literal> para a branch <literal>releng/<replaceable>12.0</replaceable>/</literal>.
Release End-of-Life Fim de Vida (End-of-Life) de Releases
This section describes the website-related files to update when a release reaches <acronym>EoL</acronym> (End-of-Life). Esta seção descreve os arquivos relacionados ao website que precisam ser atualizados quando uma release atingir o <acronym>EoL</acronym> (End-of-Life).
Website Updates for End-of-Life Atualizações do Website para End-of-Life
When a release reaches End-of-Life, references to that release should be removed and/or updated on the website: Quando uma release atinge o End-of-Life, as referências para essa release precisam ser removidas ou atualizadas no website:
File Arquivo
<filename>head/en_US.ISO8859-1/htdocs/index.xsl</filename> <filename>head/en_US.ISO8859-1/htdocs/index.xsl</filename>
Remove <literal>&amp;u.relXXX.announce;</literal> and <literal>&amp;u.relXXX.current;</literal> references. Remover referências <literal>&amp;u.relXXX.announce;</literal> e <literal>&amp;u.relXXX.current;</literal>.
<filename>head/en_US.ISO8859-1/htdocs/releases/index.xml</filename> <filename>head/en_US.ISO8859-1/htdocs/releases/index.xml</filename>
Move the &amp;u.relXXX.*; macros from the supported release list to the Legacy Releases list. Mova as macros &amp;u.relXXX.*; da lista de releases suportadas para a lista de Releases Legadas.
<filename>head/en_US.ISO8859-1/htdocs/releng/index.xml</filename> <filename>head/en_US.ISO8859-1/htdocs/releng/index.xml</filename>
Update the appropriate releng branch to refelect the branch is no longer supported. Atualizar a branch releng em questão para refletir que a branch não é mais suportada.

Loading…

User avatar dbaio

New translation

FreeBSD Doc / articles_freebsd-releng — Portuguese (Brazil)

To request an Errata Notice after a release cycle has completed, a developer should fill out the <link xlink:href="https://www.freebsd.org/security/errata-template.txt">Errata Notice template</link>, in particular the <literal>Background</literal>, <literal>Problem Description</literal>, <literal>Impact</literal>, and if applicable, <literal>Workaround</literal> sections.
Para solicitar uma Errata após a conclusão de um ciclo de lançamento, o desenvolvedor deve preencher o <link xlink:href="https://www.freebsd.org/security/errata-template.txt">Template de Errata</link>>, em particular as seções <literal>Background</literal>, <literal>Problem Description</literal>, <literal>Impact</literal> e, se aplicável, as seções <literal>Workaround</literal>.
a year 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:1546
String age
a year ago
Source string age
a year ago
Translation file
articles/pt_BR/freebsd-releng.po, string 298