The most important part about version control within a team structure is communication. Whether it's SCCS, RCS, CVS, SVN, ClearCase, or even dated text files, it's important to communicate with your fellow team member regarding which files you're going to edit, and what those changes might be. With concurrant systems, this becomes imperative so you don't collide and have to spend an inordinate amount of time merging the code.

Another thing to consider is which system will best suit your development style and your release management strategy. Some tools are better for a strict Develop-QA-Release cycle, whereas others support a more dynamic method, in which the cycle might be altered to suit various business imperatives.

Take a look at release strategies, and look at your developers styles. Maybe you can use one of these tools to help promote a greater sense of teamwork among the various development groups.

You may also wish to look at entire programming environments, such as Eclipse, which have the ability to embed CVS and SVN as part of their internal project management.

Hope this helped,
-v.

"Perl. There is no substitute."

In reply to Re: Tracking code changes by Velaki
in thread Tracking code changes by xorl

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.