Hello, Marco's recommendations are very good, I would just add the following: - each developer works on his own instance, and commits his work in SVN or CVS, then everything must be regularly delivered in an integration instance where the latest current versions of all the developers can be tested together - each developer writes unit tests when working on his instance, then he must run them on the integration instance once he has delivered his changes.
Eric BREHAULT On 3/25/07, Marco Bizzarri <[EMAIL PROTECTED]> wrote:
On 3/25/07, Roberto Scelzo <[EMAIL PROTECTED]> wrote: > > Hi all, > we are developing a couple of zope apps which now > are becoming pretty complex and, unfortunately, > up to now we're developing TTW since we > haven't yet find > a smart & fast way to do our job avoiding the ZMI. > We've searched a lot around but never found a nice guidence or howto... > > It'll be nice to develop by eclipse... > Anyways, since the last upgrade (zope 2.9) even the external editor > doesn't work anymore. (sob...) > > Someone suggested us to use a FS dump product, another one instead pointed > us > to zope FS products, but, is there any > article/howto on how to make group development/debugging of middle/large > sized zope apps > a nice and confortable experience? > > Thank you! > Roberto > It depends a lot on what you're looking for. You have a number of different challenges, when you have a team working on a medium to complex Zope application. I can provide some suggestions based on our experience with PAFlow, which is the largest application we've developed so far. 1) develop your application as one or more file system based product; 2) once your application is a file system based product, set up an svn/cvs for your team; 3) give one or more instance to each of your developer, where he/she can deploy the application and test it without interfering with the work of the others; deploy your products inside the Products directory of the instance, not inside the general Products directory; 4) use Eclipse + PyDev as a development environment; 5) keep in mind that while you're developing your application it will happen that you will have to test with different releases of Zope, and you should be able to do so in a simple way. Hope this can help. I can provide more details on our working enviroment, if you're interested. Regards Marco -- Marco Bizzarri http://iliveinpisa.blogspot.com/ _______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )