[Zope] Zope stability

[Alexander Limi]

> so my advice is: use a separate computer as a webserver on which you only
> store 'things' that have been tested very well and you won't have much
> trouble. but: never, never, never use the production server for
> daily work
> as it seems to become more unstable with every call to
> standard_error_message...

This is indeed a very scary thought - we initially chose to go for Zope for
exactly those reasons, that we could manipulate it "live" and work in
versions which are then committed. It is thus critical the we shouldn't be
able to bring the site down by doing things in Zope at the same time as it
is online. Comments?

Also, on a side note, is there a way to do offline development of Zope, and
commit those changes to the main site at a later date? I know this raises
important concurrency concerns, but has it ever been considered as a part
of Zope's feature set? A CVS of sorts, where you check out and in files?


Regards,

Alexander Limi
http://mp3.no