Berkeley CSUA MOTD:2011:April:06 Wednesday <Tuesday>
Berkeley CSUA MOTD
2011/4/6-20 [Industry/Startup, Computer/SW/Unix, Computer/SW/Mail] UID:54078 Activity:nil
4/6     My company is evaluating version control systems. Our two candidates
        are Perforce and Subversion. Anyone worked with both and have good
        arguments one way or the other? (These are the only two options we
        have.) We're most interested in client performance, ease of use, and
        reasonable branching.
        \_ I'll be 'that guy'. If perforce and subversion are optins, why isn't
           git? Having not used perforce, I can't say much about it, but svn is
           grossly insufficient for my branching and checkpointing needs. I
           cannot use svn anymore without git-svn.
           \_ svn+trac = nice.  git-svn+trac = OH THE HORROR.
           \_ Corporate standards. (Yes, it's a stupid reason.) -op
           \_ In what way is svn insufficient for your branching needs? All of
              the claims I see about svn not supporting branching well predate
              the merge support added in svn 1.5. I've not used svn and so am
              not able to tell to what extent that merge support works.
        \_ I have used P4win and the mods P4py and what not.  I thought they
           wre great at core focus, but lousy at being customizeable.  You will
           probably go with Perforce tho since the app looks nice on winboxen.
           git for windows is knida amateur looking.
           \_ There is also P4-Emacs at which
              I've used for a few years.  -- yuen
        \_ State your eng size. This will be one of the most decisive factors.
           Perforce for 5 employees? FORGET IT.
           Subversion for 1000 employees? FORGET IT.
           \_ Try bugzilla on 1000 employees.  Ugh. the horror.
           I've used p4, svn, and git. All have advantages and disadvantages.
           Use the wrong tool for the wrong size, you'll be bitching all the way.
           What people don't realize is that there is something else much more
           important than what you use-- a code-review process.
           \_ We are a group of about 50 developers right now, with plans to
              expand in the coming years and to manage more of our internal
              tools through version control.
              We do code reviews, although we're currently re-evaluating our
              tool choices there as well. Our options are Crucible and Code
              Collaborator. -op
              \_ Go with SVN.  You sound like small shop.
Berkeley CSUA MOTD:2011:April:06 Wednesday <Tuesday>