[development] FAQ: Why is Drupal still using CVS when X is a much better choice?

[mark burdett]

One case study to look at, both to see how painful RCS migration can
be as well as showing that it can be done, would be freebsd's ongoing
migration of their huge and ancient repository from CVS to Subversion.
 For the time being, the CVS repository is still in place along with
all the infrastructure tied to it; commits are made to SVN, constantly
mirrored to CVS, and releases are made from CVS.  Some notes about it
here:
http://people.freebsd.org/~peter/svn_notes.txt
http://lists.freebsd.org/pipermail/freebsd-current/2008-June/086023.html

--mark

On Thu, Jul 31, 2008 at 10:10 AM, Earnie Boyd
<earnie at users.sourceforge.net> wrote:
> Quoting Gerhard Killesreiter <gerhard at killesreiter.de>:
>
>>
>> Well, then we just can stay with CVS. IMO SVN's features aren't that
>> vastly superior to spend much effort on moving.
>>
>
> That is certainly the opinion I hold for projects I maintain elsewhere.  If
> it is already in CVS there is no need to switch to SVN.  The hardship people
> tend to have with CVS is understanding the meaning of branch and release
> tags.  However, Drupal has well defined meanings for those and the release
> tools and documentation handle them well.
>
> Earnie -- http://for-my-kids.com/
> -- http://give-me-an-offer.com/
>
>