Greetings again,
Many thanks for the people who took the time to responded to my previous email,
regarding
the logging of 'tag', and 'rtag'. I did some follow-up research into the
documentation. The
documentation for 'history' directive in the 'config' file indicates if you use
'LogHistory=TMAR'
all command that modify the ',v' file will be logged. This implies that both 'rtag'
and 'tag'
should write record to the history file.
The documentation for the 'history' file provide detail about the 'rtag' entries, and
is
silent as to the 'tag' command.
Why do we need this logging for 'tag'.
Our group is using tags to indicate the communicate release status of the checked-in
version. Our
developers are placing a 'submit' tag, whenever they feel that a checked-in version is
ready for
release. The integration person is placing a 'release' tag when a code is accepted
into the released
version. It is important to us to track in the history: when (and by whom) files are
being submitted
or released.
In my opinion, having per file history records, that will capture the tagging process
(what
file, version, when and by who) add a lot of accountability to the process of source
code
management. This level of logging is consistent with information that is provided by
other
logging options (checkout, ...).
I will appreciate any feedback.
Yair Lenga
_______________________________________________
Bug-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-cvs
