fwiw, i've been able to get good results at migrating the plone repository and branches using the refinecvs migration script http://lev.serebryakov.spb.ru/refinecvs/
the cvs2svn script included with subversion had several issues with branches, although it was a few months ago (prior to svn 1.0) that i last attempted to use it. with a little luck plone will be on svn before the end of the month. i've also setup some one way cvs->svn sync scripts for mirroring zope.org cvs into an svn repository to allow for automated pull of dependencies via svn:externals. -kapil On Mon, 2004-04-12 at 08:44, Sidnei da Silva wrote: > On Mon, Apr 12, 2004 at 08:11:44AM -0400, Tres Seaver wrote: > | Lennart Regebro wrote: > | >From: "Jim Fulton" <[EMAIL PROTECTED]> > | > > | >>Initially, I propose to move just the repository heads. Maintenamce > | >>branches (e.g. Zope 2.6 and Zope 2.7) will remain in CVS. > | > > | >What is the rationale behind not moving it all? > | > | Risk mitigation; we have significant support requirements for deployed > | systems built around CVS for both 2.6- and 2.7-based sites, whereas the > | head and Zope3 have no such inertia. We don't know enough about the > | migration process to have any confidence that existing history / > | branches, etc., won't be somehow messed up, which makes it prudent to > | plan the migration around the already-unstable bits. > > Just FYI, Kapil has been doing a good job at improving the script that > migrates from CVS to SVN, and we are ready to flip the switch to move > Plone, Collective and possibly Archetypes to SVN. _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
