- Use <firstterm> instead of <emphasis> when introducing a new technical
term. - Add missing words to form a complete sentence. - Markup the first instance of STABLE the same as the first instance of CURRENT. PR: docs/30774, docs/30773 Submitted by: Giorgos Keramidas <charon@labs.gr>
This commit is contained in:
parent
0cd240532e
commit
d9c88c41c3
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=10807
1 changed files with 11 additions and 8 deletions
|
@ -1,3 +1,6 @@
|
|||
<!-- $FreeBSD$ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
|
||||
%man;
|
||||
|
@ -253,7 +256,7 @@
|
|||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para><emphasis>Contributors</emphasis> write code or documentation.
|
||||
<para><firstterm>Contributors</firstterm> write code or documentation.
|
||||
They are not permitted to commit (add code) directly to the source
|
||||
tree. In order for their code to be included in the system, it
|
||||
must be reviewed and checked in by a registered developer, known
|
||||
|
@ -261,7 +264,7 @@
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><emphasis>Committers</emphasis> are developers with write
|
||||
<para><firstterm>Committers</firstterm> are developers with write
|
||||
access to the source tree. In order to become a committer, an
|
||||
individual must show ability in the area in which he is
|
||||
active.</para>
|
||||
|
@ -277,14 +280,14 @@
|
|||
their changes for review before committing them. In extreme
|
||||
cases, a core team member with a function such as Principal
|
||||
Architect may order that changes be removed from the tree, a
|
||||
process known as <emphasis>backing out</emphasis>. All committers
|
||||
process known as <firstterm>backing out</firstterm>. All committers
|
||||
receive mail describing each individual commit, so it is not
|
||||
possible to commit secretly.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><emphasis>Core team</emphasis> In addition, FreeBSD
|
||||
and NetBSD each have a core team which manages the project. The
|
||||
<para>The <firstterm>Core team</firstterm>. FreeBSD and
|
||||
NetBSD each have a core team which manages the project. The
|
||||
core teams developed in the course of the projects, and their role
|
||||
is not always well-defined. It is not necessary to be a developer
|
||||
in order to be a core team member, though it is normal. The rules
|
||||
|
@ -340,7 +343,7 @@
|
|||
<orderedlist>
|
||||
<listitem>
|
||||
<para>The development version of the system is called
|
||||
<emphasis>CURRENT</emphasis>. FreeBSD assigns a number to
|
||||
<firstterm>CURRENT</firstterm>. FreeBSD assigns a number to
|
||||
CURRENT, for example FreeBSD 5.0-CURRENT. NetBSD uses a slightly
|
||||
different naming scheme and appends a single-letter suffix which
|
||||
indicates changes in the internal interfaces, for example NetBSD
|
||||
|
@ -350,7 +353,7 @@
|
|||
|
||||
<listitem>
|
||||
<para>At regular intervals, between two and four times a year, the
|
||||
projects bring out a <emphasis>RELEASE</emphasis> version of the
|
||||
projects bring out a <firstterm>RELEASE</firstterm> version of the
|
||||
system, which is available on CD-ROM and for free download from
|
||||
FTP sites, for example OpenBSD 2.6-RELEASE or NetBSD 1.4-RELEASE.
|
||||
The RELEASE version is intended for end users and is the normal
|
||||
|
@ -362,7 +365,7 @@
|
|||
<listitem>
|
||||
<para>As bugs are found in a RELEASE version, they are fixed, and
|
||||
the fixes are added to the CVS tree. In FreeBSD, the resultant
|
||||
version is called the STABLE version, while in NetBSD and OpenBSD
|
||||
version is called the <firstterm>STABLE</firstterm> version, while in NetBSD and OpenBSD
|
||||
it continues to be called the RELEASE version. Smaller new
|
||||
features can also be added to this branch after a period of test
|
||||
in the CURRENT branch.</para>
|
||||
|
|
Loading…
Reference in a new issue