RE: Tags usage -- comments please

[Eugene Kramer]

I agree. In my previous company build process provided report in a format:

bugID/changeID
bug description
developer, who fixed
developer's CVS comments associated with the fix
list of files modified for the bug

This was a very effective way to communicate source changes, because it
provided the context for the change. It was all an in-house development.
This information is extremely valuable for QA, who can focus their effort
based on the list of modified files.

Eugene.

-----Original Message-----
From: address@hidden [mailto:address@hidden

>--- Forwarded mail from address@hidden

>Let me turn your question around: how often have you had to determine
>exactly which files have been affected by a specific bug fix? (This is an
>open question to anyone reading this message). I cannot recall ever needing
>this information.

It happens often enough when you want to port a specific bug fix to a new
branch.