From c4b660e96384e351ee30a665f2e94661479c6ab5 Mon Sep 17 00:00:00 2001
From: vivekv <>
Date: Sun, 1 Dec 2002 18:29:02 +0000
Subject: [PATCH] Removed references to linuxdoc. Please publish this version

---
 .../CVS-BestPractices/cvs-bestpractices.xml   | 37 ++++++++++++++++---
 1 file changed, 31 insertions(+), 6 deletions(-)

diff --git a/LDP/ref/docbook/CVS-BestPractices/cvs-bestpractices.xml b/LDP/ref/docbook/CVS-BestPractices/cvs-bestpractices.xml
index 526f91a3..b6f5a709 100644
--- a/LDP/ref/docbook/CVS-BestPractices/cvs-bestpractices.xml
+++ b/LDP/ref/docbook/CVS-BestPractices/cvs-bestpractices.xml
@@ -6,7 +6,7 @@
 "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
 
 <!-- Document version -->
-<!ENTITY DOCVERSION "0.5">
+<!ENTITY DOCVERSION "0.6">
 
 <!-- File Includes -->
 <!ENTITY GFDL-FILE SYSTEM "gfdl.xml">
@@ -67,6 +67,14 @@
 
 <revhistory>
 
+<revision>
+<revnumber>0.6</revnumber>
+<date>2002-09-10</date>
+<authorinitials>vv</authorinitials>
+<revremark>Added content related to tagging and daily builds. Changed 
+Linuxdoc URLs to tldp</revremark>
+</revision>
+
 <revision>
 <revnumber>0.5</revnumber>
 <date>2002-08-25</date>
@@ -449,7 +457,7 @@ find the &CVSAB; command-line interface daunting.  The adoption and usage of
 &CVSAB; can be improved by using GUI tools for &CVSAB; clients.  </para>
 
 <para> GUI tools for &CVSAB; are available at <ulink
-url="http://www.cvsgui.org">http://www.cvsgui.org</ulink>.  GUI interfaces
+url="http://cvsgui.sourceforge.net/"/>http://cvsgui.sourceforge.net/</ulink>.  GUI interfaces
 are available for most of the popular platforms (Windows, Mac and Linux).
 In addition, on the Windows platform there is an <acronym>SCC</acronym>
 extension that allows integration of &CVSAB; as the configuration control
@@ -843,6 +851,10 @@ The project team should ensure that successful builds are top priority on
 their agenda.  The seriousness can be emphasised by setting up a penalty for
 breaking the build.  </para>
 
+<para>Each build can be tagged in CVS using a standard naming convention.
+This can help developers checkout a working version of the entire system
+from daily builds for local development.  </para>
+
 </sect2>
 
 <sect2 id="section2-automate" xreflabel="&section2-automate;">
@@ -1024,6 +1036,7 @@ The bug fix team will check out using the command line
 </listitem>
 </orderedlist>
 
+
 <para> As soon as the bug fix team completes the two top priority bugs, they
 will update, verify a successful build and commit their changes to the bug
 fix branch using the command line
@@ -1040,10 +1053,22 @@ the branch should be committed back into the repository.  </para>
 cvs commit -R -r release_1_0_patches {module name}
 </command>
 
-<para>Now, the regular process of build-test-build is followed to make a
-	version ready for delivery.  The final version of the source code is
-	committed into &CVSAB;.  Now, two practices have to be followed.
-</para>
+<para><xref linkend="section2-bebo" /> : On a daily basis, each developer
+will check in code to &CVSAB; and to ensure sanity of code, daily builds on
+the bug fixed branch will be undertaken by checking out from
+&CVSAB; on a clean environment and completely rebuilt.  These daily builds
+can be tagged in  &CVSAB; using the following naming convention </para>
+<literallayout>
+<literal>build_1_1_yyyymmdd : for the branch</literal>
+<literal>build_2_0_yyyymmdd : for the trunk</literal>
+</literallayout>
+
+<para>The regular process of build-test-fix is followed to make a version
+ready for delivery.  The tag will help developers checkout a working copy of
+the latest build as and when necessary.  </para>
+
+<para> When the source code is released to the outside world, two practices
+have to be followed.  </para>
 
 <orderedlist>
 <listitem>