[Zope] Version Control in Zope / Managing releases

[Marcin Kasperski]

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  \