Herman Radtke wrote:
The DVCS migration path would not have to be as radical as the path
from cvs to svn. A single section of the overall svn repoistory can
be migrated to a DVCS. This pilot repo would serve two purposes:
determine if that DVCS is the correct choice and allow for a more
gradual learning curve.
Python is in the process of doing this with Mercurial:
http://www.python.org/dev/peps/pep-0374/ - PEP 374: On switching to a DVCS
http://www.python.org/dev/peps/pep-0385/ - PEP 385: Migrating from svn
to Mercurial
There was talk of other alternatives to a DVCS too. Those should be
considered fully as well.
While part of the reasoning behind going with Hg there was to do with the fact
that Hg is heavily python based, it is useful to note that the secondary reason
was the poor windows support, and apparent LACK of interest in git that swung
the decision hg's way.
At the end of the day however it probably has nothing to do with which DVCS is
used for master copies. The interoperability now available does mean that we can
safely ignore any 'choice' and simply use our own preference locally :) It will
be the management of processes which are the main problem, something that is
still outstanding anyway currently ...
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
