I will be starting the CVS conversion to SVN (subversion) early tomorrow morning -- 0800 EDT on the morning of Wednesday the 25th of May.
The conversion will take approximately 2 hours with testing afterwords and will follow this general outline:
1. Existing CVS Repository switched to read-only (both by changing priv's and also by renaming the password file)
2. A backup of the existing CVS data will be made 3. cvs2svn script will be run using the following command lines:./cvs2svn --dump-only --use-cvs --force-branch=rel-0_1-maint --dumpfile=Attic.dump /usr/local/cvsrep/Attic ./cvs2svn --dump-only --use-cvs --force-branch=rel-0_1-maint --dumpfile=chandler.dump /usr/local/cvsrep/chandler ./cvs2svn --dump-only --use-cvs --force-branch=rel-0_1-maint --dumpfile=external.dump /usr/local/cvsrep/external ./cvs2svn --dump-only --use-cvs --force-branch=rel-0_1-maint --dumpfile=hardhat.dump /usr/local/cvsrep/hardhat ./cvs2svn --dump-only --use-cvs --force-branch=rel-0_1-maint --dumpfile=internal.dump /usr/local/cvsrep/internal ./cvs2svn --dump-only --use-cvs --force-branch=rel-0_1-maint --dumpfile=docs.dump /usr/local/cvsrep/docs ./cvs2svn --dump-only --use-cvs --force-branch=rel-0_1-maint --dumpfile=cosmo.dump /usr/local/cvsrep/cosmo ./cvs2svn --dump-only --use-cvs --force-branch=rel-0_1-maint --dumpfile=server.dump /usr/local/cvsrep/server ./cvs2svn --dump-only --use-cvs --force-branch=rel-0_1-maint --dumpfile=commons.dump /usr/local/cvsrep/commons ./cvs2svn --dump-only --use-cvs --force-branch=rel-0_1-maint --dumpfile=chandler-python.dump /usr/local/cvsrep/chandler-python ./cvs2svn --dump-only --use-cvs --force-branch=rel-0_1-maint --dumpfile=demo2.dump /usr/local/cvsrep/demo2 ./cvs2svn --dump-only --use-cvs --force-branch=rel-0_1-maint --dumpfile=old.dump /usr/local/cvsrep/old
for the curious:
--dump-only generates the dumpfile without doing any svn repository
creation,
--use-cvs tells it to use the cvs command instead of rcs
--force tells it to force the rel-0_1-maint tag to be a branch when
found
--dumpfile is, of course, the file to create
and finally the path to the cvs tree to convert
4. new SVN repositories will be created:
svnadmin create --fs-type fsfs repository_name
Chandler: chandler, internal, external and hardhat
Docs: docs
Server: server, cosmo and commons
Archive: Attic, chandler-python, demo2 and old
Each of the CVS modules will be loaded into the appropriate
repository using this command:
svnadmin load /path/to/repository < dump_file
Each dump file is loaded into the repository in the order that the
were created under CVS so all history is preserved.
5. A pass will be made thru each of the new repositories to add appropriate svn propset calls for $Id keyword replacement
6. Hook scripts will be added for email notification and file checks.Each of the repositories will have a new structure - one that follows the Subversion recommended layout:
Chandler/
trunk/
chandler/
internal/
external/
hardhat/
branches/
CHANDLER_0_4_BRANCH/
CHANDLER_0_5_BRANCH/
...
tags/
If you had an existing svn+ssh account, you will be able to continue to
use it. If not, then I will be setting up new password entries for
each developer. You will need to coordinate with me what you want your
password to be as I will not be able to transfer the existing CVS entry
to the SVN password file. Anonymous access will still be possible thru
the existing http:// url
Once the final paths are known, I will post them to this list. --- Bear http://code-bear.com Open Source Applications Foundation (OSAF) http://www.osafoundation.org PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29
PGP.sig
Description: This is a digitally signed message part
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
