Jim Fulton wrote:

I'm working on the cvs to subversion conversion for the ZODB, Zope 2, and
Zope 3 projects. I'm currently doing the conversion of the full history with
tags and branches. This is taking a long time and creating a huge
repository, which is OK, but, do we really need that much history?

I see 3 options:

1. Convert the full history with branches. This will create
   a rather large and complex repository.

2. Convert the mainline history, but leave off the branches.

3. Start with a clean slate and simply import the current head.

Note that, for Zope 2 and ZODB, current maintenance branches will
remain in CVS.

I think that option 2 provides a nice compromise.  The main disadvantage
of it is that it will leave current development branches high and dry.
I'm not sure how big an issue this is.  In theory, these could be committed
to the subversion heav via patch files.


I'm going to go with option 2. We won't lose anything, as we'll still have the existing tag and branch data in CVS as a permanent record.

Just before conversion, I'll also tag the head.  This will be useful for
computing patch sets for open CVS workspaces and development branches.


Jim Fulton           mailto:[EMAIL PROTECTED]       Python Powered!
CTO                  (540) 361-1714            http://www.python.org
Zope Corporation     http://www.zope.com       http://www.zope.org

Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )

Reply via email to