[crossfire] Crossfire Release Cycles/Methodology

[Tchize]

Also, about restructurations of code, svn unlike cvs does not 'forget' 
the history of a file when it's moved. I use cvs a lot for work and 
dureing refactoring of our code (which happens from time to time) we 
already lost versions of some files because they were deleted / restored 
/ deleted and as result, you have an unconsistent attic (2 files with 
same name at same directory got deleted, you only have access to latest 
on in Attic)

Nicolas Weeger (Laposte) wrote:
>>   I'm not sure about the other systems out there - once can spend a lot of
>> time looking over all the documentation, etc.  AS with our last discussion,
>> I'm most inclined to stick with CVS since we know what it does and doesn't
>> have any real major shortcomings (it works right now).
>>     
>
> I'm in no way CVS/SVN expert (I use both, but I never really played with 
> branches).
>
> IMO, if SVN isn't too bad for branches, we should switch. SVN has atomic 
> transactions, that's a great feature, specially with upcoming talk about 
> restructuration and such - makes it much easier to revert commits.
>
> Nicolas
>
> _______________________________________________
> crossfire mailing list
> crossfire at metalforge.org
> http://mailman.metalforge.org/mailman/listinfo/crossfire
>
>