Infrastructure for Mozart development

[Kevin Glynn]

Guido Tack writes:
 > Hi Boriss.
 > 
 > > Kevin was looking at Sourceforge and Savannah sometime in the past, but
 > > I just remember that his conclusion was that we were going to lose the
 > > history of CVS. I don't know if that is the case if we first port the

That was when I was looking at using sourceforge to host the *MozartDSS*
source repository to test out how well sourceforge worked in
practice. We would have lost the MozartDSS history when we merged it
back into mozart.

Someone should move a copy of the Mozart repository to one of these
providers and then we can see how long commits, checkouts, diffs,
etc. take.  I suppose there are large projects using sourceforge
successfully but I don't have any experience myself.

 > > repository to SVN, and then we put it at Sourceforge. Savannah does not
 > > support SVN yet. I haven't used SVN very much yet, but according to the
 > > basic advantages that it presents, I also think we should switch to that.
 > 
 > Sourceforge supports importing complete svn dumps. It is possible to convert
 > the Mozart CVS to svn, including complete history (we've done that for
 > Gecode), and then import the svn in sourceforge.
 > 
 > I can tell you from our experience with Gecode that svn is so much better
 > than CVS. E.g. some weeks ago we had to move complete directories around,
 > which is a nightmare with CVS and worked perfectly with svn. Updating my
 > local copy that contained changes to files that were moved in the
 > repository worked perfectly.
 > 

Yay,  switch to subversion.

k