On Wed, Aug 4, 2010 at 2:23 AM, Francis J. Lacoste <[email protected]> wrote: > Hi Jono, > > While Robert is sleeping, here's my take at your clarification questions based > on our conversation. > > On August 3, 2010, Jonathan Lange wrote:
>> Is there a facility to roll out just the QAd stuff? > > No. Un-qaed revisions blocks deployment. unqa-ed stuff doesn't get rolled out. If we have 10 revisions in stable and not in production, and the first 5 are QA-ok, we can roll out those 5. >> This depends on fixing a deployment icing issue, right? > > Yes, otherwise this creates problem during the deployment. Its trivial :). >> 3. Get rid of edge. Set up a redirect for legacy edge URLs. Rely on >> feature flags to hide in-development features. >> >> Now at this point, how often will we be rolling out production >> appserver-only changes? > > As often as we can. Once the process is smooth, we'll remove the 'push-button' > aspect of it and deploy automatically when a new stretch of QA-ed revisions is > available. I don't think we want to remove the push button aspect: rather I think we want the end of the QA process to be 'its rolled out'; unattended deployments at 1700UTC sunday just because someone ticked a QA checkbox are a bad idea. Deploying that first thing monday when an engineer is around to participate *if* something is screwy - great. I appreciate that there may be some differences in opinion here, but as its a relatively simple knob to change, lets get to the point where everything-but-this is done and we can revisit :) -Rob _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
