Re: Revision control + bug tracking
between bits of data between systems. I.e., someone reviewing the change
logs should be able to get a pointer to the bug report that caused a
developer to implement this change (if any), and someone viewing a bug
report (open or closed) should be able to find the sections of code it's
related to, or changes made in its name. Those pointers should be created
with as little effort on the part of the developer as possible.
I agree with Jonathan that a code change should not imply a bug is closed;
if someone desires that kind of logic, they can implement it with some
form of automation script triggered through a customer-specific event.
Received on Sat Oct 21 14:36:05 2006
This is an archived mail posted to the Subversion Dev