Repository Layout
&TCAR; is supported by Subversion, a
version control system which allows you to keep old versions
of files and directories (usually source code), keep a log of
who, when, and why changes occurred, etc., like CVS, RCS or
SCCS.
&TCAR; is made of one source repository
and
many working copies
of that source repository.
The working copies are independent one another, can be
distributed all around the world and provide a local place for
designers, documentors, translators and programmers to perform
their work in a descentralized way. The source repository, on
the other hand, provides a central place for all independent
working copies to interchange data and provides the
information required to permit extracting previous versions of
files at any time.
The first level of directories inside &TCAR; provides
organization through a convenctional trunk/, branches/ and tags/ layout. As proposition we
are assuming that:
The trunk/
directory is where development changes take place.
The branches/
directory is where maintainance changes take place.
The tags/ directory
is where final releases take place.
The second level of directories inside &TCAR; provides
organization for different work lines, as described in . All other subsequent
directory levels from third level on exist to organize
specific concepts related to the work line they belong to.