RE: CVS and tracability

[Arthur Barrett]

CVSNT (also GPL, free, Windows, Linux, Unix, Mac etc) has a -B bug switch for 
"cvs edit", "cvs commit" etc etc.  This can be captured by the various triggers 
so that each time a commit is done the information is available.  You can 
either "log" the info there, or integrate it directly with your defect tracking 
system so a log message is applied to it when you commit (this is what we do).  
You can also cvs commit -b bug to "commit by bug number".

You can get cvsnt from www.cvsnt.com and the cvsnt mailing list is here:
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
Or
news://news.cvsnt.org/support.cvsnt

Regards,


Arthur Barrett

> -----Original Message-----
> From: address@hidden 
> [mailto:address@hidden
> ] On Behalf Of Familie Moßner
> Sent: Sunday, 6 March 2005 10:06 PM
> To: address@hidden
> Subject: CVS and tracability
> 
> 
> Hi,
> 
> 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?
> 
> Any hints appreciated,
> wkm
> 
> -- 
> www.mossner-online.de
> 
> 
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/info-cvs
>