[crossfire] Crossfire Release Cycles/Methodology

[Tchize]

svn does branching and tagging, and according to this faq 
(http://subversion.tigris.org/faq.html#merge-using-tags) it does it 
pretty well.

basically svn does this to handle branching and merging
copy trunk ->  myBranch
copy myBranch -> myBranchMerged
modify myBranch at will
copy the diff between myBranch and myBranchMerged to trunk

CVS on his side does this
tag the main branch
create a branch from given tag (don't forget to give that branch a name 
that must be different than tag)
modify the branch
copy all changes made to branch to main

As a result, same number of operation, and svn is 'supposed' to be 
faster than cvs at this because the operations do not depend on 
repository size but on change size.

I think that because the branch name appear in url, it make it easier 
for user to checkout a given branch or revision from anonymous svn and 
the fact branches appear on http browsing (which  is not the case of 
svn) is also a pro for svn.

Mark Wedel wrote:
>   Some of SVN big advantages appears to be able to work offline (keeps copy of 
> data you checked out around so you can do diffs without needing connection, as 
> well as ungets).  Some of the other features may not make as big a difference to 
> us - ability to use different connection methods (that really is up to the 
> hosting agent) and better binary support.
>
>   But the fact it doesn't do branching as well as CVS is probably a major 
> shortcoming, especially since we are looking at needing to use branches a lot more.
>
>   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).
>
>
>
>
>
> _______________________________________________
> crossfire mailing list
> crossfire at metalforge.org
> http://mailman.metalforge.org/mailman/listinfo/crossfire
>
>