os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Note how blanket approvals and pending requests for approval are

Browse source 
tracked internally.

Add a note about an internal copy of the CHECKSUM files and the
MANIFEST files stored in the misc/freebsd-release-manifests port.

Suggested by:	marius
Sponsored by:	The FreeBSD Foundation
This commit is contained in:
Glen Barber 2017-04-06 19:23:40 +00:00
parent 3f2fef66ba
commit f2adf216ac
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=50135
2 changed files with 36 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
en_US.ISO8859-1/articles/freebsd-releng/article.xml
View file

@ -336,6 +336,26 @@
blanket approvals from the start of the code slush until the
start of the <acronym>RC</acronym> builds.</para>
<note>
<para>In order to keep track of blanket approvals, the &team.re;
uses an internal repository to keep a running log of such
requests, which defines the area upon which a blanket approval
was granted, the author(s), when the blanket approval expires,
and the reason the approval was granted. One example of this
is granting blanket approval to <filename
class="directory">release/doc/</filename> to all &team.re;
members until the final <literal>RC</literal> to update the
release notes and other release-related documentation.</para>
</note>
<note>
<para>The &team.re; also uses this repository to track pending
approval requests that are received just prior to starting
various builds during the release cycle, which the Release
Engineer specifies the cutoff period with an email to the &os;
developers.</para>
</note>
<para>Depending on the underlying set of code in question, and
the overall impact the set of code has on &os; as a whole, such
requests may be approved or denied by the &team.re;.</para>
@ -399,6 +419,11 @@
&team.secteam; 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>.</para>
<note>
<para>The actual process of issuing <acronym>EN</acronym>s is
handled by the &team.secteam;.</para>
</note>
</sect2>
<sect2 xml:id="releng-wrapup-handoff">

11
en_US.ISO8859-1/articles/freebsd-releng/releng-building.xml
View file

@ -234,6 +234,17 @@ KERNEL="GENERIC64"</programlisting>
to the relevant branch, such as &branch.stablex; or
&branch.relengx;.</para>
<para>During the release cycle, a copy of
<filename>CHECKSUM.SHA512</filename> and
<filename>CHECKSUM.SHA256</filename> for each architecture are
stored in the &team.re; internal repository in addition to being
included in the various announcement emails. Each
<filename>MANIFEST</filename> containing the hashes of
<filename>base.txz</filename>, <filename>kernel.txz</filename>,
etc. are added to
<package>misc/freebsd-release-manifests</package> in the Ports
Collection, as well.</para>
<para>After building the final <literal>RELEASE</literal>, the
&branch.relengx; branch is tagged as &branch.releasex; using the
revision from which the <literal>RELEASE</literal> was built.