Features to track refactoring.

[Andrew Cowie]

On Thu, 2008-05-22 at 00:10 +0200, Alexey Balmashnov wrote:
> Are there any features to track code refactoring? 

In general, distributed version control systems will handle this sort of
thing. Bazaar in particular will handle it very well indeed since it
tracks file renames properly.

This assumes that that your second person, "Dimitri", is working on a
branch that was taken from a point prior to refactoring. As far as he
can see, the code is exactly as it was before. He applies his fixes, and
tests. No problem.

Then, later, it will come time to merge into the mainline branch that
Jane is working on (or vice versa). Probably no conflicts will occur,
but if they do, you resolve them, no huge deal. Either way you'll still
run the tests, and assuming all is ok, commit the merge.

_yes_, Dimitri will probably need to track down what the new name of the
file is so he knows where to look to double check his work is still ok,
but he'd have to learn about the refactoring sooner or later anyway. But
_no_, he doesn't have to read the log comment for any of this to work.

AfC
Sydney

-- 
Andrew Frederick Cowie

Operational Dynamics is an operations and engineering consultancy
focusing on IT strategy, organizational architecture, systems
review, and effective procedures for change management. We actively
carry out research and development in these areas on behalf of our
clients, and enable successful use of open source in their mission
critical enterprises, worldwide.

http://www.operationaldynamics.com/

Sydney   New York   Toronto   London
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20080522/30528e30/attachment.pgp