In short, what makes a good version control system "good?" What are some of the things you look for when evaluating a new version control system?

#1 for me is reliability. Version control is often my only backup and the code I store there is my most valuable product. I took a long time to switch from CVS to Subversion because I didn't want to deal with any instability in my version control.

Flexiblity is important - being able to add scripts that run when various events happen is very useful. I like to have a commit mailing-list, for example.

Speed is an attractive quality, particularly since I spend my days using Subversion on a very large codebase. I wish it was a lot faster.

I also like the idea of a distributed system like SVK. Unfortunately SVK failed hard for me and one time losing work was enough for me.

Frankly though, all this is icing on the cake. Using version control - any version control - is so much better than not using any that it doesn't make a lot of difference to me. I'd grumble a bit if I had to go back to CVS, but life would go on. Going without any version control though, now that's unthinkable!

-sam

In reply to Re: Evaluating version control systems by samtregar
in thread Evaluating version control systems by Nkuvu

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.