old-www/REF/CVS-BestPractices/html/section1-intro.html

433 lines
8.1 KiB
HTML
Raw Permalink Blame History

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML
><HEAD
><TITLE
>Introduction</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="CVS Best Practices"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="CVS Best Practices"
HREF="index.html"><LINK
REL="NEXT"
TITLE="Focus Areas"
HREF="section1-focusareas.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>CVS Best Practices</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="index.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="section1-focusareas.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="section1-intro"
></A
>1. Introduction</H1
><A
NAME="AEN52"
></A
><TABLE
BORDER="0"
WIDTH="100%"
CELLSPACING="0"
CELLPADDING="0"
CLASS="BLOCKQUOTE"
><TR
><TD
WIDTH="10%"
VALIGN="TOP"
>&nbsp;</TD
><TD
WIDTH="80%"
VALIGN="TOP"
><P
CLASS="literallayout"
>Men&nbsp;have&nbsp;become&nbsp;the&nbsp;tools&nbsp;of&nbsp;their&nbsp;tools.&nbsp;<br>
</P
></TD
><TD
WIDTH="10%"
VALIGN="TOP"
>&nbsp;</TD
></TR
><TR
><TD
COLSPAN="2"
ALIGN="RIGHT"
VALIGN="TOP"
>--<SPAN
CLASS="attribution"
>Henry David Thoreau (1817-1862)
</SPAN
></TD
><TD
WIDTH="10%"
>&nbsp;</TD
></TR
></TABLE
><P
>This article outlines some of the best practices that can be adopted
when Concurrent Versions System is used as the configuration management tool in your software
project. </P
><P
>Concurrent Versions System (CVS) is an <A
HREF="http://www.opensource.org"
TARGET="_top"
>Open Source</A
> configuration management
tool that is now being looked at seriously by many commercial organizations as
a viable alternative to other commercial Software configuration management tools. </P
><P
>This spotlight on CVS has led to the inevitable question of best
practices for deploying CVS as the backbone SCM tool for large
software development projects. Having answered this question many times
verbally as a bunch of <SPAN
CLASS="QUOTE"
>"gotchas"</SPAN
> on CVS, it was time to put
down on paper some of the best practices that will work well for
CVS based projects. </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>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 CVS </P
><P
>Further, This paper is not an introduction to CVS and its usage. There are
excellent articles available on the net for the same. This paper assumes
that the reader is familiar with CVS commands and is looking at
deploying CVS in his or her organization. Some of the popular
CVS related links that can provide CVS education are. </P
><P
></P
><OL
TYPE="1"
><LI
><P
>The <A
HREF="http://ximbiot.com/cvs/wiki/index.php?title=Main_Page"
TARGET="_top"
>Concurrent Versions System site</A
> where
current informaton about CVS is available. Including the <A
HREF="http://ximbiot.com/cvs/wiki/index.php?title=Cederqvist"
TARGET="_top"
>CVS manual</A
>.
</P
></LI
><LI
><P
>Karl Fogel's book, <A
HREF="http://cvsbook.red-bean.com"
TARGET="_top"
>Open Source Development with
CVS</A
> is available online.
</P
></LI
></OL
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="copyright"
></A
>1.1. Copyright Information</H2
><P
> This document is Copyright <20> 2001 Vivek Venugopalan. Permission
is granted to copy, distribute and/or modify this document under the terms of
the <A
HREF="gfdl.html"
><I
CLASS="citetitle"
>GNU Free Documentation
License</I
></A
>, Version 1.1 or any later version published by the
Free Software Foundation with no Invariant Sections, no Front-Cover Texts, and
no Back-Cover Texts. A copy of the license can be found in <A
HREF="gfdl.html"
>Appendix A</A
>. </P
><P
> This document may be reproduced and distributed in whole or in part, in
any medium physical or electronic, as long as this copyright notice is
retained on all copies. Commercial redistribution is allowed and encouraged;
however, the author would like to be notified of any such distributions.
</P
><P
> All translations, derivative works, or aggregate works incorporating
this document must be covered under this copyright notice. That is, you may
not produce a derivative work from this document and impose additional
restrictions on its distribution. Exceptions to these rules may be granted
under certain conditions; please contact the author at the address given
below. </P
><P
> In short, we wish to promote dissemination of this information through
as many channels as possible. However, we do wish to retain copyright on the
document, and would like to be notified of any plans to redistribute the same.
</P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="disclaimer"
></A
>1.2. Disclaimer</H2
><P
> No liability for the contents of this document can be accepted. Use
the concepts, examples and other content at your own risk. As this is a new
edition of this document, there may be errors and inaccuracies that may of
course be damaging to your system. Proceed with caution, and although this is
highly unlikely, the author(s) do not take any responsibility whatsoever.
</P
><P
> All copyrights are held by their respective owners, unless specifically
noted otherwise. Use of a term in this document should not be regarded as
affecting the validity of any trademark or service mark. </P
><P
> Naming of particular products or brands should not be seen as
endorsements. </P
><P
> You are strongly recommended to take a backup of your system before
major installation and backups at regular intervals. </P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="newversions"
></A
>1.3. New Versions</H2
><P
> This document is Version : 0.7. </P
><P
> The latest version of this document can be obtained from (In the order of latest version availability) </P
><P
></P
><OL
TYPE="1"
><LI
><P
>&#13;<A
HREF="http://www.sanchivi.com/cm/cvs-bestpractices/index.html"
TARGET="_top"
>My website</A
>
</P
></LI
><LI
><P
>&#13;<A
HREF="http://tldp.org/REF/CVS-BestPractices/html/index.html"
TARGET="_top"
>The linux documentation project</A
>
</P
></LI
></OL
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="credits"
></A
>1.4. Credits</H2
><P
>The list of people who have provided information and correction for this
paper in no particular order are.
<P
></P
><OL
TYPE="1"
><LI
><P
>Jens-Uwe Mager </P
></LI
><LI
><P
>Jorgen Grahn </P
></LI
><LI
><P
>Thomas S. Urban </P
></LI
><LI
><P
>Cam Mayor </P
></LI
><LI
><P
>Sally Miller</P
></LI
><LI
><P
>Niels Jakob Darger</P
></LI
></OL
>
</P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="feedback"
></A
>1.5. Feedback</H2
><P
> Feedback is most certainly welcome for this document. Without your
submissions and input, this document wouldn't exist. Please send your
additions, comments and criticisms to the following email address :
<TT
CLASS="email"
>&#60;<A
HREF="mailto:vivekv at yahoo dot com"
>vivekv at yahoo dot com</A
>&#62;</TT
>. </P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="section1-focusareas.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>CVS Best Practices</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Focus Areas</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>