History for Version Control

changed:
-
Subversion?

  I think I've asked before, but has anyone looked at "subversion" as a (better) replacement for CVS?  Advantages I can see are:

  1 Directory structures are tracked

  2 Can attach metadata

  3 Files accessible over http(s), ssh etc

  One downside (change) is that revisions are over the whole tree, not on a per-file basis.

  Have a look at http://subversion.tigris.org and there's a 'book' describing usage and changes at http://svnbook.red-bean.com/book/book.html

The public cmiss subversion repository is at https://svn.physiomeproject.org/svn/cmiss/


From andre Tue Jun 15 12:12:20 +1200 2004
From: andre
Date: Tue, 15 Jun 2004 12:12:20 +1200
Subject: 4. User access not required
Message-ID: <20040615121220+1200@bioeng2.bioeng.auckland.ac.nz:9080>

Using subversion committers no longer require read/write access to the code repository. This is seen as a huge security advantage. Could be good if more people will be accessing cmiss code more from outside the university firewall.

From andre Tue Jun 15 12:15:09 +1200 2004
From: andre
Date: Tue, 15 Jun 2004 12:15:09 +1200
Subject: Use by Apache Software Foundation
Message-ID: <20040615121509+1200@bioeng2.bioeng.auckland.ac.nz:9080>

The ASF has recently begun recommending all its projects look at changing over to subversion from CVS. While it is still a gentle recommendation, they also state that the change will probably be enforced in the not too distant future (two/three year time frame).