Source string Read only

(itstool) path: sect2/para
289/2890
Context English 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.
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.
As with the staging steps, this requires <literal>root</literal> level access, as this step must be executed as the <literal>archive</literal> user.
As the <literal>archive</literal> user:
<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.
Wrapping up the Release Cycle
This section describes general post-release tasks.
Post-Release Errata Notices
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>.
The actual process of issuing <acronym>EN</acronym>s is handled by the FreeBSD Security Team.
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.
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.
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.
Handoff to the FreeBSD Security Team
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.

Loading…

No matching activity found.

Browse all component changes

Glossary

English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: sect2/para
Labels
No labels currently set.
Flags
read-only
Source string location
article.translate.xml:1568
Source string age
11 months ago
Translation file
string