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

Remove CVSup and CVS references from the dev model as they are no longer relevent.

Browse source 
Discussed with:	rpaulo
This commit is contained in:
Eitan Adler 2013-09-25 04:15:31 +00:00
parent 0c71b71a09
commit 1f33dc7287
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=42703
1 changed files with 10 additions and 134 deletions

144
en_US.ISO8859-1/books/dev-model/book.xml
View file

@ -45,6 +45,12 @@
<holder>Niklas Saers</holder>
</copyright>
<revhistory>
<revision>
<revnumber>1.4</revnumber>
<date>September, 2013</date>
<revremark>Remove mention of CVS and CVSup which are no
longer used by the project.</revremark>
</revision>
<revision>
<revnumber>1.3</revnumber>
<date>October, 2012</date>
@ -896,22 +902,6 @@
</para>
</section>
<section id="role-cvsup-coordinator" xreflabel="CVSup Mirror Site Coordinator">
<title>CVSup Mirror Site Coordinator</title>
<para>
The CVSup Mirror Site Coordinator coordinates all the
<xref linkend="role-cvsup-sitemaint"/>s to ensure that they
are distributing current versions of the software, that they
have the capacity to update themselves when major updates
are in progress, and making it easy for the general public
to find their closest CVSup mirror.
</para>
<para>
Hat currently held by:
The CVSup-master team <email>cvsup-master@FreeBSD.org</email>.
</para>
</section>
<section id="role-postmaster" xreflabel="Postmaster">
<title>Postmaster</title>
<para>
@ -1030,11 +1020,11 @@
responsibility to ensure that technical problems that arise in the
repository are resolved quickly. The source repository
manager has the authority to back out commits if this is
necessary to resolve a CVS technical problem.
necessary to resolve a SVN technical problem.
</para>
<para>
Hat held by:
the Source Repository Manager <email>cvs@FreeBSD.org</email>.
the Source Repository Manager <email>clusteradm@FreeBSD.org</email>.
</para>
</section>
@ -1240,20 +1230,6 @@
for review is posted.
</para>
</section>
<section id="role-cvsup-sitemaint" xreflabel="CVSup Mirror Site
Admin">
<title>CVSup Mirror Site Admin</title>
<para>
A CVSup Mirror Site Admin has accesses to a server that he/she
uses to mirror the CVS repository. The admin works with the
<xref linkend="role-cvsup-coordinator"/> to ensure the site
remains up-to-date and is following the general policy of
official mirror sites.
</para>
</section>
</section>
@ -1402,93 +1378,6 @@
</section>
<section id="process-cvsupmirror" xreflabel="Adding an official
CVSup Mirror">
<title>Adding/Removing an official CVSup Mirror</title>
<para>
A <xref linkend="tool-cvsup"/> mirror is a replica of the
official CVSup master that contains all the up-to-date source
code for all the branches in the FreeBSD project, ports and
documentation.
</para>
<para>
Adding an official CVSup mirror starts with the potential
<xref linkend="role-cvsup-sitemaint"/> installing the
<quote>cvsup-mirror</quote> package. Having done this and
updated the source code with a mirror site, he now runs a
fairly recent unofficial CVSup mirror.
</para>
<para>
Deciding he has a stable environment, the processing
power, the network capacity and the
storage capacity to run an official mirror, he mails the
<xref linkend="role-cvsup-coordinator"/> who decides whether
the mirror should become an official mirror or not.
</para>
<para>
In making this decision, the <xref linkend="role-cvsup-coordinator"/>
has to determine whether that geographical area needs
another mirror site, if the mirror administrator has the
skills to run it reliably, if the network bandwidth is
adequate and if the master server has the capacity to server
another mirror.
</para>
<para>
If <xref linkend="role-cvsup-coordinator"/> decides that the
mirror should become an official mirror, he obtains an
authentication key from the mirror admin that he installs so
the mirror admin can update the mirror from the master server.
</para>
<para>
<figure>
<title>Process summary: adding a CVSup mirror</title>
<graphic fileref="proc-add-cvsup"/>
</figure>
</para>
<para>
When a CVSup mirror administrator of an unofficial mirror
offers to become an official mirror site, the CVSup
coordinator decides if another mirror is needed and if
there is sufficient capacity to accommodate it. If so,
an authorisation key is requested and the mirror is given
access to the main distribution site and added to the
list of official mirrors.
</para>
<para>
Tools used in this process:
<itemizedlist>
<listitem><para>
<xref linkend="tool-cvsup"/>
</para></listitem>
<listitem><para>
<xref linkend="tool-ssh2"/>
</para></listitem>
</itemizedlist>
</para>
<para>
Hats involved in this process:
<itemizedlist>
<listitem><para>
<xref linkend="role-cvsup-coordinator"/>
</para></listitem>
<listitem><para>
<xref linkend="role-cvsup-sitemaint"/>
</para></listitem>
</itemizedlist>
</para>
</section>
<section id="committing">
<title>Committing code</title>
@ -2183,9 +2072,8 @@
<para>
The major support tools for supporting the development process are
CVS, CVSup, Perforce, GNATS, Mailman and OpenSSH. Except for
CVSup, these are externally
developed tools. These tools are commonly used in the open source world.
Perforce, GNATS, Mailman and OpenSSH. These are externally
developed tools and are commonly used in the open source world.
</para>
<section id="tool-svn" xreflabel="SVN">
@ -2198,18 +2086,6 @@
</para>
</section>
<section id="tool-cvsup" xreflabel="CVSup">
<title>CVSup</title>
<para>
CVSup is a software package for distributing and updating
collections of files across a network. It consists of a
client program, cvsup, and a server program, cvsupd. The
package is tailored specifically for distributing CVS
repositories, and by taking advantage of CVS' properties, it
performs updates much faster than traditional systems.
</para>
</section>
<section id="tool-gnats" xreflabel="GNATS">
<title>GNATS</title>
<para>