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

Whitespace-only fixups from the e-mail to SGML entities conversion.

Browse source
This commit is contained in:
Peter Pentchev 2002-03-15 08:28:14 +00:00
parent 81f0937cee
commit 6e99166b51
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=12474
8 changed files with 39 additions and 59 deletions
Download patch file Download diff file Expand all files Collapse all files

18
en_US.ISO8859-1/articles/releng/article.sgml
View file

@ -122,8 +122,7 @@
interface provided at <ulink
url="http://www.FreeBSD.org/send-pr.html"></ulink>
In addition to the multitude of different technical mailing lists
about FreeBSD, the &a.qa;
provides a forum for discussing the finer
about FreeBSD, the &a.qa; provides a forum for discussing the finer
points of <quote>release-polishing</quote>.</para>
<para>To service our most conservative users, individual release
@ -169,8 +168,8 @@
<para>Thirty days before the anticipated release, the source
repository enters a <quote>code slush</quote>. During this
time, all commits to the -STABLE branch must be approved by the
&a.re;. The kinds of changes that
are allowed during this 15 day period include:</para>
&a.re;. The kinds of changes that are allowed during this 15 day
period include:</para>
<itemizedlist>
<listitem>
@ -580,9 +579,9 @@
<para>The <ulink url="http://www.FreeBSD.org/ports">FreeBSD Ports
collection</ulink> is a collection of over &os.numports;
third-party software packages available for FreeBSD. The &a.portmgr;
is responsible for maintaining a
consistent ports tree that can be used to create the binary
packages that accompany official FreeBSD releases.</para>
is responsible for maintaining a consistent ports tree that can be used
to create the binary packages that accompany official FreeBSD
releases.</para>
<para>The release engineering activities for our collection of
third-party packages is beyond the scope of this document. A
@ -828,9 +827,8 @@
throughout the years making FreeBSD what it is today. Of course
the release wouldn't have been possible without all of the
release-related work done by &a.asami;, &a.steve;, &a.bmah;, &a.nik;,
&a.obrien;, &a.kris;, &a.jhb; and the rest of
the FreeBSD development community. I would also like to thank
&a.rgrimes;, &a.phk;, and others
&a.obrien;, &a.kris;, &a.jhb; and the rest of the FreeBSD development
community. I would also like to thank &a.rgrimes;, &a.phk;, and others
who worked on the release engineering tools in the very early days
of FreeBSD. This article was influenced by release engineering
documents from the CSRG[14], the NetBSD Project[11], and John