Difference between revisions of "Version Control System"

From Freeside
Jump to: navigation, search
(New page: We need to move off of CVS eventually. Choice #1: Move to subversion, it's CVS 2.0 anyway. Choice #2: Move to a distributed VCS. * Subversion - CVS 2.0. Who needs a distributed VCS any...)
 
(Synopsis)
 
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
We need to move off of CVS eventually.
+
= Synopsis =
  
Choice #1: Move to subversion, it's CVS 2.0 anyway.
+
We moved to git.
  
Choice #2: Move to a distributed VCS.
+
The rest of the information here is of historical interest.
  
* Subversion - CVS 2.0.  Who needs a distributed VCS anyway? (C)
+
= Systems =
 +
 
 +
== The big three ==
 
* Git - all the cool kids are using it these days (C)
 
* Git - all the cool kids are using it these days (C)
* monotone (C++)
 
* svk - disribution based on subversion, best practical sponsors it, RT uses it (perl)
 
 
* Mercurial/Hg (python)
 
* Mercurial/Hg (python)
 
* Bazaar - Canoical/Ubuntu/Launchpad  (python)
 
* Bazaar - Canoical/Ubuntu/Launchpad  (python)
 +
 +
== The dark horses ==
 +
* monotone (C++)
 
* Darcs (haskell)
 
* Darcs (haskell)
  
Not considering
+
== Not considering ==
 
+
* Subversion, if we're going to migrate, it might as well be to something better enough to bother
 
* Codeville, its dead jim
 
* Codeville, its dead jim
 
* Vesta, commercial abandonware, not distributed
 
* Vesta, commercial abandonware, not distributed
 +
* Aegis - a strange beast.  Probably not for us.
 +
 +
= Requirements =
  
Random others
+
* Import from CVS, preserving history (not just tips of our three branches)
 +
* Web interface not completely unlike viewvc.cgi
 +
* Good support for moving/renaming files and whole directories (i.e. preserving history)
 +
* Useful versions (incl. viewvc.cgi-alike) utility in Debian stable or backports  (bzr: no)
 +
* What else?
  
* Aegis - a strange beast.  Probably not for us.
+
= References =
  
References
+
* Zooko [http://zooko.com/revision_control_quick_ref.html]
 +
* Version control blog [http://74.125.155.132/search?q=cache:hRNkMrsxMfgJ:versioncontrolblog.com/comparison/Arch/Bazaar/Darcs/Git/Mercurial/Monotone/index.html+git,monotone,mercurial,bazaar,darcs&cd=1&hl=en&ct=clnk&gl=us]
  
Zooko [http://zooko.com/revision_control_quick_ref.html]
+
* Smashing magazine [http://www.smashingmagazine.com/2008/09/18/the-top-7-open-source-version-control-systems/]
 +
* Wikipedia [http://en.wikipedia.org/wiki/Comparison_of_revision_control_software]
 +
* DCVS round up [http://ldn.linuxfoundation.org/article/dvcs-round-one-system-rule-them-all-part-1]  [http://ldn.linuxfoundation.org/article/dvcs-roundup-one-system-rule-them-all-part-2] [http://ldn.linuxfoundation.org/article/dvcs-round-one-system-rule-them-all-part-3]

Latest revision as of 19:01, 4 March 2012

Synopsis

We moved to git.

The rest of the information here is of historical interest.

Systems

The big three

  • Git - all the cool kids are using it these days (C)
  • Mercurial/Hg (python)
  • Bazaar - Canoical/Ubuntu/Launchpad (python)

The dark horses

  • monotone (C++)
  • Darcs (haskell)

Not considering

  • Subversion, if we're going to migrate, it might as well be to something better enough to bother
  • Codeville, its dead jim
  • Vesta, commercial abandonware, not distributed
  • Aegis - a strange beast. Probably not for us.

Requirements

  • Import from CVS, preserving history (not just tips of our three branches)
  • Web interface not completely unlike viewvc.cgi
  • Good support for moving/renaming files and whole directories (i.e. preserving history)
  • Useful versions (incl. viewvc.cgi-alike) utility in Debian stable or backports (bzr: no)
  • What else?

References

  • Zooko [1]
  • Version control blog [2]