subversion contra vault



possible duplicate:






i'm now reviewing advantages relocating svn sourcegear vault.
has anyone got recommendation couple footnote comparison between two?
bear mind i have pierce tide source control component opposing works strongly svn's favor



here info i have found out so distant possess investigations.



i have holding tests between twin stable seems perform many operations many faster. tests used same server repository, same workstation client, same project.



time comparisons




  • svn





add/commit
   12:30



get latest revision
   5:35



tagging/labelling
   0:01



branching
   n/a - i don't cruise loyal branching exists svn





  • vault





add/commit
   4:45



get latest revision
   0:51



tagging/labelling
   0:30



branching
   3:23




(can't format correctly)



i also found an online source comparing points. kind information i'm looking for.



usage comparisons




  • subversion edit/merge/commit only. stable allows either
    edit/merge/commit checkout/edit/checkin.


  • vault looks acts only vss, creates training curve
    effectively 0 vss users.


  • vault vs plugin, nonetheless wholly works you're going run in
    checkout-mode.


  • subversion clients graceful many each os imagine;
    vault gui fan windows management line fan mono.


  • both support remote work, given both http their
    transport (subversion uses extended dav, stable uses soap).


  • subversion installation, generally w/ apache, some-more complex.


  • subversion lot third jubilee support. stable only few things.




my question



has anyone got recommendation couple footnote comparison between two?



Comments

Popular posts from this blog

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?

grails record upload problems

unable interpret unicode character