Infrastructure for Mozart development

[Kevin Glynn]

Konstantin Popov writes:
 > 
 > >  > 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.
 > 
 > I'd support it too - but we need some "backups" somewhere (what's
 > e.g. the sourceforge' policy&guarantees on their own
 > failures?). Besides, keeping the CVS history is IMHO not so critical:
 > we can host a read-only CVS server somewhere with the "old stuff". Not
 > to mention, the history has already been a couple of times..
 > 

These sites will make a tarball of the repository for you regularly
(e.g. every night) and you can just download a copy and store it
somewhere else.

cheers
k