[Zope] Version Control Question

[Meilicke, Scott]

The way we manage our non-zope internet site is to have three environments:
dev, staging (quality) and production.  Developers do unit development and
testing on their own work stations, and migrate that to the development
server to ensure everyone's code plays nice.  Then a migration engineer
moves that to staging at planned intervals. Staging is tested, and when all
is good, staging is moved to production.

That said, for our Intranet we'll probably just have developer workstations,
an integration/staging/quality server, and production.  The plan is when we
go for a release, we'll freeze staging, have our developers work on their
own boxes, then migrate to production.  The reason is zope's versioning and
ability to import/export portions of a site makes recovering from errors and
duplicating environments (or just portions) really easy.

Scott

ps - this is a non HTML mail formatted list.

-----Original Message-----
From: ken bolton [mailto:kbolton@sputnik7.com]
Sent: Thursday, August 30, 2001 8:16 AM
To: zope@zope.org
Subject: [Zope] Version Control Question


Hi guys,

I posed this question to the fellows at NYZUG yesterday evening, and they
suggested that I post it here, point blank.

We want to use version control on our site. Without sparking a religious
war, what do you recommend for syncing a development environment, a quality
assurance environment, and a production environment? Is the built-in Zope
Version package enough? Should we use that in conjunction with ZEO? Is ZEO
on its own enough? Should we use CVS for Product maintainance? ZSyncer? 

Initially, I thought the Zope Version would be enough, do your work in a
version, have the tester start working in the version when the developer was
done, and then the tester saves the work when everything is good to go. I've
been told (by non-Zopistas, and even anti-Zopers) that we need to have three
environments. How would you go about implementing a system to please nervous
project managers?

cheers,
ken