Re: [Zope] Version Control in Zope / Managing releases
Nils Kassube wrote: The thread at the ZEO list is indeed very interesting. I wanted to write something like this: http://lists.zope.org/pipermail/zope-zeo/2000-September/000131.html Nice to see someone else having the same thoughts. I strongly commit the thoughts described in the letter cited above. For the applications I develop, I use CVS to version control, merge changes, tag important revisions etc. I develop in test environment, create code distributions based on tags and migrate it to production environment. Working in teams I use merge functionality sometimes. I can accept the need to use some other version control tool but it should have the same features. ZCVSMixin does not solve the problems. It is not recursive. There is no way to commit all the changes in the whole folder hierarchy. There is also no way to import a bunch of changes based on a tag (which gathers multiple folders). And the solution (exporting everything to filesystem) is not the natural one. Until the problem is solved, I will never use Zope to implement important web application. This is sad - I like Zope, I use it to back my private webpage and my company information webpage and I like many Zope features. I even considered creating everything as a Python products (their code can be CVS-controlled) but such a method is out of any sense. It seems to me that it would be easier to implement complete version-control mechanisms within Zope (there is Undo, there are versions, there is export/import) than to build better integration with external VC tools, but this is just an opinion. Regards Marcin -- http://www.mk.w.pl / Marcin.Kasperski | Moje prywatne strony: http://www.kasperski.prv.pl @softax.com.pl | @bigfoot.com \ ___ Zope maillist - [EMAIL PROTECTED] 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 )
Re: [Zope] Version Control in Zope / Managing releases
Marcin Kasperski wrote: It seems to me that it would be easier to implement complete version-control mechanisms within Zope (there is Undo, there are versions, there is export/import) than to build better integration with external VC tools, but this is just an opinion. I think that's right, and I'm sure all the hard work has been done. Just needs someone to string it all together into a decent revision control system... cheers, Chris ___ Zope maillist - [EMAIL PROTECTED] 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 )
Re: [Zope] Version Control in Zope / Managing releases
That's not to say that Greg's difficulties are unique. I just don't think his solution is appropriate for most. Synchronization is a major need for Zope. In fact, I have some working code! But *I need feedback*. http://dev.zope.org/Wikis/DevSite/Proposals/SynchronizationTab The ideas presented on this page are very interesting. The main things which can cause problems: - how can one diff zope objects (diff on XML exports?); - what about the scenario, in which CVS (or sth. else) repository is not accessible from production server (I would like to export sth from repository via tag and import it to production). I would like to take a look at some working code... Regards -- http://www.mk.w.pl / Marcin.Kasperski | Kcik porad dla programistw: @softax.com.pl | http://www.softax.com.pl/prywatne/marcink/porady @bigfoot.com \ ___ Zope maillist - [EMAIL PROTECTED] 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 )
RE: [Zope] Version Control in Zope / Managing releases
snip 1) "Code Collisions." - Developers overwriting each other's work. 2) Partial updates - Right now, we have new pages for marketing content that are held up because we don't have our new features for the application done yet. So we can't update marketing pages without updating the app at the same time, (one ZODB) unless we directly update the production servers. (Eeek!) snip Forgive me if this is overly simplistic, but these problems can both be addressed or at least worked around by using versions, no? Each developer should have his/her own version object. To lock the object (and solve #1), a developer just needs to open it and click change. Then to unlock whatever was worked on and commit it, save the changes to the version. Granted this means only one person can work on an object at one time. This can be worked around by proper modularization of your app. Also, developers need to remember to save their version changes so that others can work on those objects too. This also has a side benefit of letting you document your changes in a more meaningful way. Also, an entire set of changes can be rolled back if it breaks something. #2 is more about what versions were designed for. Just work on the app code in a version and don't commit it until it's ready. Granted this assumes that you have sufficiently separated the data, layout and code and aren't using a lot of external methods. If this isn't a possible solution, I would just create a production version of the feature in one folder that might not be complete but can be updated, and work on a second copy in another folder that isn't accessible to everyone yet. If this won't work please elaborate on your design and maybe someone will have better idea. Good Luck! -Casey Duncan ___ Zope maillist - [EMAIL PROTECTED] 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 )
Re: [Zope] Version Control in Zope / Managing releases
Shane Hathaway wrote: I would say there are simply too many developments happening for anyone to keep up. I can understand why my little proposal has been overlooked--it doesn't seem very exciting. :-) There *is* too much going on, but I'm *very* excited by this proposal. Using versions to isolate development from current users is useful but only in a limited fashion. Most environments don't allow development on production servers, and if you're doing serious development you're probably working on the filesystem (at least partially) anyway. We're facing this challenge at ZapMedia, and I had the same problem at WebMD. The solution there was a bit easier because we had fewer developers working on more isolated projects. We have some tools in place for doing releases at ZapMedia, but there's still an uncomfortable feeling because we're all using the same development server. Doug ___ Zope maillist - [EMAIL PROTECTED] 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 )
