[crossfire] CVS -> SVN conversion

[Mark Wedel]

  Current status:

  CVS data is imported over, and I've renamed the files to be arch/trunk, 
client/trunk, etc.

  I've also made 1.x branches of the arch, client, maps, and server (at such 
time it becomes relevant, it could be done for jxclient and sounds).  There are 
as arch/branches/1.x, client/branches/1.x, etc.

  Things that I still have yet to do, and will do tomorrow night:

  Use svn propset to make some virtual entries (link to gridarta for the edit, a 
link in server/lib/arch to link to archetypes), support for $Id$ in files.

  Also, should make some 'virtual' directories with links to all he relevant 
pieces.  Eg, have a 'complete' or 'latest' directory which can get all the 
*/trunk entries, so easy to get all those.

  Likewise, probably have a stable directory which links to the 1.x entries.

  That said, there is nothing preventing developers from checking out the SVN 
and actively using it - the things left to do above should not affect that.




Mark Wedel wrote:
>   Just a note/reminder of this change:
> 
>   Crossfire will switch from CVS to SVN this onday, Sept 18.
> 
> What will happen:
> - Current CVS repository will remain available for read-only access, but no 
> future changes will be made to that repository.  The CVS repository will purely 
> be for historical reasons (want to see what 1.6 looked like, etc.)  Developer 
> permissions will be updated to remove CVS write permissions.  The crossfire page 
> on sourceforge will also be updated so that CVS info will not appear.
> 
> - The SVN repository will only import the head trunk, and not the tags or 
> branches of the CVS repository.  Future tags and branches will be made of course.
> 
> - Only actively developed portions from CVS will be moved over.
> 
> - Instead of having a copy of the editor in crossfire, we will link to the 
> Gridarta project.
> 
> - Some amount of cleanup in the repositories will be done - mainly, this means 
> that some automatically generated files will not be included (flex files, 
> collected archetypes/images/etc).  The autoconf/automake files will stay in the 
> repository, as it is general practice that code can be downloaded and then a 
> simple configure run.
> 
> - The server portion will be renamed from 'crossfire' to 'server' to more 
> accurately describe what portion it is.
> 
> - The organization will be server/trunk, client/trunk, client/branches, etc.
> 
> After the fact:
> 
> - The server and client will need some updating to get the version number so 
> they can print that out as a build revision (instead of showing revision of each 
> file).
> 
> - Branches for 1.x will be made for the different components.
> 
> - Likely some other cleanup will be necessary.
> 
> 
> 
> 
> _______________________________________________
> crossfire mailing list
> crossfire at metalforge.org
> http://mailman.metalforge.org/mailman/listinfo/crossfire