Using the CVS Client189
that have not been updated with the repository, CVS will inform you and give you the option of
releasing the working directory.
# cd /home/lcp
# cvs release fuzion
A banner.jpg
M fuzion.pl
You have [2] altered files in this repository.
Are you sure you want to release directory `fuzion': Y
# rm –r fuzion
6.4.12Tags and Releases
One of the strengths of CVS is its ability to create a release of a particular project. A
release is a snapshot of a project at a specific point in time and is generally referred to by a
numeric designation. When we refer to CVS version 1.1.11p1, we are talking about a specific
release of the application that will always remain the same. If changes are made to that version
of the software, the version number will change by indicating either a patch level or an incre-
ment in the major or minor version number.
This designation can be accomplished with CVS by assigning a
tag
to a project. Tags
may be named in any fashion, symbolically with a numerical system as mentioned, or by code
names, etc. It is important, however, that once a methodology for naming releases is established
that it be abided by in order to prevent confusion in the future.
To apply a tag to a project, issue the following command from within the project directory:
# cvs tag Release_1_1 .
cvs server: Tagging .
T 1.0.fuzion.pl
T banner.jpg
T em.dat
T fuzion.pl
T index.html
T newfile
T sk.dat
T tal.dat
T test.dat
This does not change any information in the files; it simply places symbolic tags in the
CVS repository so that when Release_1_1 of the Fuzion project is requested, these versions of
the files will be retrieved from the repository.
To check a specific release back out of the repository, issue the
checkout
command
with the –
r
option and the name of the release.
# cvs checkout –r Release_1_1 fuzion