Zope hacking and products is on the file system where we use source control. CVSMixin is available which allows you to put Zope objects in CVS if you choose. ZSyncer isnt CVS but allows us to seperate dev and production. Cheers. -- Andy McKay. ----- Original Message ----- From: "Richard Wesley" <hawkfish@electricfish.com> To: <zope@zope.org> Sent: Tuesday, October 16, 2001 9:47 AM Subject: [Zope] Concurrent development
Hi Zopers,
I have been looking into Zope of late, partly because I have a web site I'd like to build as a demo, and partly because I felt I should just know some kind of web app tool, and Zope came highly recommended.
After playing with it for a bit, I have become nervous about the revision control aspects. Conflicts are pretty much resolved silently in favor of the last person to make a change. There is some sort of branch scheme, but my initial impression of it was that it was pretty also suffered from the lack of merge capabilities.
Given that CVS is used for the actual development of Zope, this surprises me. Have I missed something? How do teams work with Zope without stepping on each other's toes? Is this a problem in practice?
TIA, Sincerely,
Richard Wesley Co-President, Electric Fish, Inc. <http://www.electricfish.com/> +1-206-634-2926 (v) +1-206-634-2921 (f)
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )