DenkzeitWiki

Version Control

VersionControlBestPractices
DistributedVersionControl

SoftwareEngineering

VersionYourLife

Diff

• cool
  • Subversion (SVN)
  • Bazaar (BZR)
  • Mercurial
  • Git
• well...
  • ConcurrentVersionsSystem? (CVS)
  • SourceSafe (VSS)
  • TeamFoundationVersionControl
  • Monotone
    
  
  
• http://blog.ianbicking.org/towards-a-more-perfect-version-control.html --Towards a More Perfect Version Control
• Using source control tools on huge projects
  • Use branches and sub-branches, maybe even per-developer branches. QA gets in before any merge 'up' towards the trunk...
    
  
  
• http://betterexplained.com/articles/a-visual-guide-to-version-control/

Comparisons

• http://better-scm.berlios.de/comparison/comparison.html --Version Control System Comparison
• http://www.dynamicobjects.com/d2r/archives/001863.html --version control systems: a short review
• also see Subversion#compare
  
  
• http://martinfowler.com/bliki/VersionControlTools.html
• http://martinfowler.com/bliki/VcsSurvey.html
  
  
• http://www.lucasward.net/2010/02/maturity-model-for-source-control-scmm.html
  • Seamless merge through rename is the high bar

Distributed and Centralized (DVCS)

• Distributed vs. Centralized Version Control
  • There's nothing wrong with the centralized model. There is something wrong with the way we are using Subversion (and CVS before it). The wrongness isn't that you need a server, or a network connection, or disk space. It's that you need commit privileges.

Methodology

• Branching
• Merging