From f529033f11f5b3b5459b4ff53611f5df2df5d6ee Mon Sep 17 00:00:00 2001
From: vivekv <>
Date: Thu, 12 Jun 2003 18:16:43 +0000
Subject: [PATCH] Fixed some dead links. Please publish this version
---
.../CVS-BestPractices/cvs-bestpractices.xml | 42 +++++++++++--------
1 file changed, 24 insertions(+), 18 deletions(-)
diff --git a/LDP/ref/docbook/CVS-BestPractices/cvs-bestpractices.xml b/LDP/ref/docbook/CVS-BestPractices/cvs-bestpractices.xml
index b6f5a709..b0425d3b 100644
--- a/LDP/ref/docbook/CVS-BestPractices/cvs-bestpractices.xml
+++ b/LDP/ref/docbook/CVS-BestPractices/cvs-bestpractices.xml
@@ -72,7 +72,8 @@
2002-09-10
vv
Added content related to tagging and daily builds. Changed
-Linuxdoc URLs to tldp
+Linuxdoc URLs to tldp. Fixed stale links and added other corrections
+suggested by readers.
@@ -152,12 +153,16 @@ verbally as a bunch of gotchas
on &CVSAB;, it was time to put
down on paper some of the best practices that will work well for
&CVSAB; based projects.
-
-This paper is not an introduction to &CVSAB; and its usage. There are
+ This paper assumes that the reader is familiar with the
+fundamentals of software version control. Including features like
+branching, merging, tagging (labelling) etc., offered by modern version
+control tools such as &CVSAB;
+
+Further, This paper is not an introduction to &CVSAB; and its usage. There are
excellent articles available on the net for the same. This paper assumes
that the reader is familiar with &CVSAB; commands and is looking at
-deploying &CVSAB; in his or her organization. Some of the popular
-&CVSAB; related links that can provide &CVSAB; education are.
+deploying &CVSAB; in his or her organization. Some of the popular
+&CVSAB; related links that can provide &CVSAB; education are.
@@ -172,10 +177,6 @@ CVS has GPL'd sections avail
-
-
-
-
@@ -257,17 +258,16 @@ major installation and backups at regular intervals.
Credits
-The list of people who have provided inputs and information for this
+The list of people who have provided information and correction for this
paper in no particular order are.
Jens-Uwe Mager
-
Jorgen Grahn
-
Thomas S. Urban
Cam Mayor
Sally Miller
+ Niels Jakob Darger
@@ -457,11 +457,11 @@ find the &CVSAB; command-line interface daunting. The adoption and usage of
&CVSAB; can be improved by using GUI tools for &CVSAB; clients.
GUI tools for &CVSAB; are available at http://cvsgui.sourceforge.net/. GUI interfaces
-are available for most of the popular platforms (Windows, Mac and Linux).
-In addition, on the Windows platform there is an SCC
-extension that allows integration of &CVSAB; as the configuration control
-tool with popular IDE.
+url="http://cvsgui.sourceforge.net/">http://cvsgui.sourceforge.net/.
+GUI interfaces are available for most of the popular platforms (Windows, Mac
+and Linux). In addition, on the Windows platform there is an
+SCC extension that allows integration of &CVSAB; as the
+configuration control tool with popular IDE.
@@ -713,7 +713,7 @@ in time.
§ion2-tagrelease;
-After each release, the entire code base must be tagged with an
+As part of the release process, the entire code base must be tagged with an
identifier that can help in uniquely identifying the release. A tag gives a
label to the collection of revisions represented by one developer's working
copy (usually, that working copy is completely up to date so the tag name is
@@ -728,6 +728,12 @@ identifier is of the form.
release_{major version #}_{minor version #}
+ As one reader pointed out to me, a good practice here is to tag
+the release first. Checkout the entire codebase using the tag, and then
+proceed to go through a build / deploy / test process before making the
+actual release. This will absolutely ensure that what leaves the
+door
is a verified and tested codebase.
+