Re: Tagging changesets

Thank you all for your replies.

I guess that the "2 working copies" scheme is the way to go, but is
this really practical when the software project is really big? Our
software contains about 3000 files. What do you think about your
solution in this case?

To answer the question "How are we currently doing this today in my
company?", we are doing it using a very simple method:

1) Work on FunctionalityA and BugB in the order you want, switching
from one task to the other as you wish

2) Before "committing" our changes (it is not really a commit since
we are not using version control software but it is equivalent) we use
a "differencing" software like Beyond Compare: it shows all the
changes made for both tasks and allows in place editing - we then use
the in place editing feature to add a little tag written like a
comment like /* FCT_A */ or /* BUG_B*/ at each block of code which was
added or modified. And usually at the top of the file where the most
changes have been made we add a longer description of the feature,
like
/* FCT_A: Developer DDD - mm/dd/yy - Implemented functionality A */

Does that make sense? Does that bring more comments?
Thanks.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 24 15:50:53 2006