Re: Upgrade as Change in Meta-state

From: Laconic2 <laconic2_at_comcast.net>
Date: Fri, 22 Oct 2004 11:54:48 -0400
Message-ID: <C6Odnduwp-fMsOTcRVn-2w_at_comcast.com>


"Kenneth Downs" <firstinit.lastname_at_lastnameplusfam.net> wrote in message news:k78blc.so1.ln_at_mercury.downsfam.net...
> Laconic2 wrote:
>
> <snip>
>
> > If the problem can be recreated, then this problem is turned over to
> > development to repair. And they may have to pull people off their
regular
> > duties to get that done.
> >
> > If the problem CANNOT be recreated on a standard database, then it's
> > production's problem to solve.
> >
> > This is not perfect, but it works.
> >
> > And I think it means we can move on without further debate on this
point.
>
> I will add only that we formalized a general case of test-production
> development with the concept of the "promotion sequence". A promotion
> sequence system provides a framework for moving changes through n stages
of
> testing. For an IDS that might be two stage, from test to live, while a
> promotion sequence for an EDS is considerably longer:
>
> 1) Vendor: Development and reality checks on a developer's box
> 2) Vendor: Testing in a smoke-test system
> 3) Vendor: More thorough testing in a qa system
> 4) Vendor: Into the release
> ----------
> 5) Customer: test system
> 6) Customer: live system

Sure! Received on Fri Oct 22 2004 - 17:54:48 CEST

Original text of this message