Jason Lee wrote:
On 5/24/07, Michael Phoenix
<michaelandrewphoenix@gmail.com>
wrote:
Only
if you can update the documentation on the check-uot check-in procedure
documentation before doing the conversion. I'm very sceptical about
this unless someone knows that it a) won't disrupt current projects
people are working on, b) can be done easily by someone in the group,
and c) won't make the checkout/check-in processes more complicated.
a) It *will* disrupt "current projects people are working on"
(assuming you mean your currently checked out working copy). The CVS
and SVN control files are *completely* different, so you'll have to
re-check out the whole tree. No nice way around that.
b) I think collab.net will take care
of the conversion. We just have to do (a).
c) It should be about the same if not slightly easier, as proxies are
actually supported by the SVN client.
I think there might be a small measure of pain involved, but mainly for
those who have local changes that they might not be ready to commit yet.
Which mostly means me. :) It's not hard, though to safely port these
changes over, though.
One thing that will be lost is the cvs history of all the files. :(
But that may be a price we have to pay to move to a better system.
I haven't heard anyone say we shouldn't move... so we probably will.
Let's talk about this in the next developer meeting.
Ken
--
Jason Lee, SCJP
JSF RI Dev Team
http://blogs.steeplesoft.com