forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <>
Subject Re: New Apache XML Site! :-)
Date Sat, 26 Oct 2002 12:39:48 GMT
Robert Koberg wrote:
> This is exactly the problem a staging process is designed to solve.
> You move from dev -> qa -> certified -> live
> dev is what you are are doing now and then you go directly live.
> A better process would be to promote the dev site to qa when you feel it is
> ready.
> qa has other people look at it. If they don't like what they see it goes back to
> dev, if they agree they like what they see it is promoted to certified.
> Some bot can come around and pick up the cert version daily (or whatever
> interval). If nothing has changed perhaps the bot can skip it or just copy it up
> to live because it is still the latest certified version.
> There is plenty of involvement in cocoon's community to support the eyeballs to
> qa (open to all??). Once the communtiy says 'good to go' or is silent then it is
> ready to promote to cert to be picked up by the bot.
> best,
> -Rob

Thanks Rob, your QA ideas are fine. Future versions of the
Forrest build should incorporate them. As Ken said we have
a basic workaround QA system for the moment, by publishing
sites underneath Forrest's wing until they are ready.

View raw message