[development] Active databases and development/test/production environment

Earnie Boyd earnie at users.sourceforge.net
Fri Aug 17 14:52:39 UTC 2007

Quoting Victor Kane <victorkane at gmail.com>:

>> Everything ought to go through a test site, of course, but this becomes a
>> potential point of failure if urgent work is needed and the test site is
>> underused
> The only solution is that someone (usually me where I am) has to serve as
> "head cook and bottlewasher" integrator in the test site.

Scheduling testing is a large complication that should not be avoided 
just because a deadline is near or past.  Testing must be planned in 
the schedule.

> The plot also thickens when customer needs to get content up in parrallel
> with old version...

But manageable none the less.


More information about the development mailing list