[development] Active databases and development/test/productionenvironment
larry at garfieldtech.com
Fri Aug 17 16:35:26 UTC 2007
Well since everyone else is sharing their dev environments, I figured I'd throw ours out there. And because I am physically incapable of doing so briefly :-), I decided to make a blog of it:
Hope that's useful to someone, and feedback welcome. :-)
On Fri, 17 Aug 2007 13:08:15 -0300, "Victor Kane" <victorkane at gmail.com> wrote:
> Right, the test site exists in our case because we (try at least to)
> organize our development around a test driven approach.
> Which involves an iterative approach. The test site is there and is tested
> incrementally with several versions.
> Victor Kane
> On 8/17/07, Earnie Boyd <earnie at users.sourceforge.net> wrote:
>> Quoting Victor Kane <victorkane at gmail.com>:
>> >> Everything ought to go through a test site, of course, but this
>> >> potential point of failure if urgent work is needed and the test site
>> >> underused
>> > The only solution is that someone (usually me where I am) has to serve
>> > "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
>> > with old version...
>> But manageable none the less.
More information about the development