The one issue is that changes made between the time the staging server
was set up and the new site goes live won't have their history
preserved. We will check-in a diff of all changes made on the current
site during this period and the Subversion history will just have a
generic message for that check-in (Subversion does have a complete
history from CVS from before the staging site was set up though).
If having a complete history for your files is important, simply hold
off on checking any changes in until the new site goes live. If you
have any questions about any of this, please feel free to let me know.
David
Isn't there any way that you can use cvs2svn to ensure that the
history is preserved for the commits made during the transition period?
Someone more technical than me can give you a better answer, but I
know that the cvs2svn was used to bring over the history for the files
up to the point the staging site was set up. Maybe you can't reimport
without overwriting the changes we've made on stage?
David
I think you should be able to run something like `cvs2svn update` and
that will pull in the changes from the CVS repository, like a merge or
something. I'm not positive, I'm just speculating, based on my very
little experience with other cross-VCS software. I'd imagine it'd be
worth looking into.
Sure, worth looking into. We can talk to it on the call on Thursday
at 10 pacific.
We'll meet then to discuss the open issues with stage and figure out
what else to do before going live.
We can use this dial-in:
1-800-707-2533
password: 369
conf: 7600
David