Translation

(itstool) path: sect2/para
English
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.
311/2890
Context English Spanish State
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 esto sea efectivo, tanto <filename class="directory">/archive/tmp</filename> como <filename class="directory">/archive/pub</filename> deben residir en el mismo sistema lógico de archivos.
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. Sin embargo, hay una advertencia, donde <application>rsync</application> debe ser usada después de <citerefentry><refentrytitle>pax</refentrytitle><manvolnum>1</manvolnum></citerefentry> para corregir los enlaces simbólicos en <filename class="directory">pub/FreeBSD/<replaceable>snapshots</replaceable>/ISO-IMAGES</filename> que <citerefentry><refentrytitle>pax</refentrytitle><manvolnum>1</manvolnum></citerefentry> reemplazará con un enlace duradero, aumentando el tiempo de propagación.
As with the staging steps, this requires <literal>root</literal> level access, as this step must be executed as the <literal>archive</literal> user. Al igual que con los pasos de la preparación, esto requiere un acceso de nivel <literal>root</literal>, ya que este paso debe ser ejecutado como el usuario <literal>archive</literal>.
As the <literal>archive</literal> user: Como el usuario del <literal>archivo</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. Reemplazar las <replaceable>instantáneas</replaceable> con las <replaceable>liberaciones</replaceable> según corresponda.
Wrapping up the Release Cycle Cerrando el ciclo de liberación
This section describes general post-release tasks. En esta sección se describen las tareas generales posteriores a la liberación.
Post-Release Errata Notices Notificaciones de errores posteriores a la liberación
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 el ciclo de liberación se aproxima a su conclusión, es común tener varios <acronym>EN</acronym> (Errata Notice) candidatos para abordar cuestiones que fueron descubiertas al final del ciclo. Tras la liberación, el Equipo de Ingeniería de Liberación de FreeBSD y el Equipo de Seguridad de FreeBSD revisan los cambios que no fueron aprobados antes de la liberación final, y dependiendo del alcance del cambio en cuestión, pueden emitir un <acronym>EN</acronym>.
The actual process of issuing <acronym>EN</acronym>s is handled by the FreeBSD Security Team. El proceso de emisión de <acronym>EN</acronym> es manejado por el Equipo de Seguridad de 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 un Aviso de Errata(EN) después de que un ciclo de lanzamiento se haya completado, un desarrollador debe llenar la plantilla <link xlink:href="https://www.freebsd.org/security/errata-template.txt">Aviso de Errata</link>, en particular las secciones <literal>Fondo</literal>, <literal>Descripción del Problema</literal>, <literal>Impacto</literal>, y si es aplicable, <literal>Trabajo alrededor</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. La plantilla de notificación de errores(Errata Notice) terminada debe ser enviada por correo electrónico junto con un parche contra la rama <literal>releng/</literal> o una lista de revisiones de la rama <literal>estable/</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 solicitudes de Erratas inmediatamente después de la liberación, la solicitud debe ser enviada por correo electrónico tanto al Equipo de Ingeniería de Liberación de FreeBSD como al Equipo de Seguridad de FreeBSD. Una vez que la rama <literal>releng/</literal> se haya entregado al Equipo de Seguridad de FreeBSD tal y como se describe en <xref linkend="releng-wrapup-handoff"/>, las peticiones de Notificación de Erratas(Errata Notice) deben enviarse al Equipo de Seguridad de FreeBSD.
Handoff to the FreeBSD Security Team Entrega al equipo de seguridad de 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 dos semanas después del lanzamiento, el Ingeniero de Lanzamiento actualiza<filename> svnadmin/conf/approvers</filename> cambiando la columna de aprobadores de <literal>re</literal> a <literal>(so|security-officer)</literal> para la rama <literal>releng/<replaceable>12.0</replaceable></literal>.
Release End-of-Life
This section describes the website-related files to update when a release reaches <acronym>EoL</acronym> (End-of-Life).
Website Updates for End-of-Life
When a release reaches End-of-Life, references to that release should be removed and/or updated on the website: Cuando un lanzamiento llega al final de la vida, las referencias a ese lanzamiento deben ser eliminadas y/o actualizadas en el sitio web:
File Archivo
<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.
<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. Mueve las macros &amp;u.relXXX.*; de la lista de versiones soportadas a la lista de versiones obsoletas
<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. La actualización de la rama de releng apropiado para refelejar la rama ya no es soportada.
<filename>head/en_US.ISO8859-1/htdocs/security/security.xml</filename> <filename>head/en_US.ISO8859-1/htdocs/security/security.xml</filename>
Remove the branch from the supported branch list. Eliminar la rama de la lista de ramas soportadas.
<filename>head/en_US.ISO8859-1/htdocs/where.xml</filename> <filename>en_US.ISO8859-1/htdocs/releases/12.0R/schedule.xml</filename>
Remove the URLs for the release. Elimina los URL para la liberación.

Loading…

User avatar juanda-097

Translation changed

FreeBSD Doc / articles_freebsd-releng — Spanish

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 dos semanas después del lanzamiento, el Ingeniero de Lanzamiento actualiza<filename> svnadmin/conf/approvers</filename> cambiando la columna de aprobadores de <literal>re</literal> a <literal>(so|security-officer)</literal> para la rama <literal>releng/<replaceable>12.0</replaceable></literal>.
5 months ago
User avatar juanda-097

Translation changed

FreeBSD Doc / articles_freebsd-releng — Spanish

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 dos semanas después del lanzamiento, el Ingeniero de Lanzamiento actualiza<filename> svnadmin/conf/approvers</filename> cambiando la columna de aprobadores de <literal>re</literal> a <literal>(so|security-officer)</literal> para la rama <literal>releng/12.0<replaceable>12.0</replaceable>.
5 months ago
User avatar juanda-097

Translation changed

FreeBSD Doc / articles_freebsd-releng — Spanish

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 dos semanas después del lanzamiento, el Ingeniero de Lanzamiento actualiza<filename> svnadmin/conf/approvers</filename> cambiando la columna de aprobadores de <literal>re</literal> a <literal>(so|security-officer)</literal> para la rama <literal>releng/12.0.
5 months ago
User avatar juanda-097

Translation changed

FreeBSD Doc / articles_freebsd-releng — Spanish

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 dos semanas después del lanzamiento, el Ingeniero de Lanzamiento actualiza<filename> svnadmin/conf/approvers</filename> cambiando la columna de aprobadores de <literal>re</literal> a <literal>(so|security-officer)</literal> para la rama <literal>releng12.0.
5 months ago
User avatar juanda-097

Translation changed

FreeBSD Doc / articles_freebsd-releng — Spanish

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 dos semanas después del lanzamiento, el Ingeniero de Lanzamiento actualiza<filename> svnadmin/conf/approvers</filename> cambiando la columna de aprobadores de <literal>re</literal> a <literal>(so|security-officer)</literal> para la rama releng12.0.
5 months ago
User avatar juanda-097

Translation changed

FreeBSD Doc / articles_freebsd-releng — Spanish

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 dos semanas después del lanzamiento, el Ingeniero de Lanzamiento actualiza<filename> svnadmin/conf/approvers</filename> cambiando la columna de aprobadores de <literal>re</literal> a <literal>(so|security-officer) para la rama releng12.0.
5 months ago
User avatar juanda-097

Translation changed

FreeBSD Doc / articles_freebsd-releng — Spanish

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 dos semanas después del lanzamiento, el Ingeniero de Lanzamiento actualiza<filename> svnadmin/conf/approvers</filename> cambiando la columna de aprobadores de <literal>re</literal> a (so|security-officer) para la rama releng12.0.
5 months ago
User avatar juanda-097

Translation changed

FreeBSD Doc / articles_freebsd-releng — Spanish

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 dos semanas después del lanzamiento, el Ingeniero de Lanzamiento actualiza<filename> svnadmin/conf/approvers</filename> cambiando la columna de aprobadores de <literal>re a (so|security-officer) para la rama releng12.0.
5 months ago
User avatar juanda-097

Translation changed

FreeBSD Doc / articles_freebsd-releng — Spanish

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 dos semanas después del lanzamiento, el Ingeniero de Lanzamiento actualiza<filename> svnadmin/conf/approbadorevers cambiando la columna de aprobadores de re a (so|security-officer) para la rama releng12.0.
5 months ago
User avatar juanda-097

New translation

FreeBSD Doc / articles_freebsd-releng — Spanish

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 dos semanas después del lanzamiento, el Ingeniero de Lanzamiento actualiza svnadmin/conf/aprobadores cambiando la columna de aprobadores de re a (so|security-officer) para la rama releng12.0.
5 months ago
Browse all component changes

Glossary

English Spanish
Release Versión FreeBSD Doc

Source information

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