Re: CVS and tracability

[Mark D. Baushke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Familie Mo�ner <address@hidden> writes:

> I'm faced with the requirement to trace changes due to certain bugfixes, 
> i.e. to answer questions like "which files have been affected by change 
> request 1234".
> 
> Currently, the only way I can think of to answre question like this is using 
> the taginfo mechanism.
>
> Are there any examples I could use? Other approaches?

You could alter your CVSROOT/rcsinfo to provide a log message template
with something like a 'request:' field and enforce good values via the
CVSROOT/verifymsg trigger and have your loginfo trigger send e-mail or
otherwise attach the desired information of the request found in the log
message into your defect tracking system that attached the list of
modified files to the request-id.

This would let you query your defect tracking system for entry '1234'
to obtain a list of files that were impacted on a particular date.

Another approach would be to use something like the cvs2cl package to
generate xml for all of the changes in a given release and collect the
list of files needed from the entries with log messages that reference
the interesting bugfix identifiers in a useful way to your own
applications.

        Good luck,
        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFCKyEb3x41pRYZE/gRAqHgAJ401IbLhaxuvmhAu49ftt7zuYd9QQCggYUp
08L2n1P3Qe686QoQ/ZxlJbo=
=pUS6
-----END PGP SIGNATURE-----