in reply to Re: What is YOUR Development Process?
in thread What is YOUR Development Process?

"There is a maintenance window on prod where the client understands installations may be occurring. Unless it is a crash-bug, this should be the only time changes are made to prod. Period."

At my workplace each machine on the farm runs two web servers one with the production code and the other with the final QA code. Come release time once a week we switch the network so the final QA web servers become production then update the old production web servers with the next QA version in the pipeline.

No maintenance downtime and the final QA code is checked on the exact same production machines.
  • Comment on Re^2: What is YOUR Development Process?

Replies are listed 'Best First'.
Re^3: What is YOUR Development Process?
by dragonchild (Archbishop) on Nov 08, 2005 at 12:59 UTC
    Do you also mount /usr/local so that both servers mount from the same physical location? That way, you guarantee that the perl installs are identical ...
    My criteria for good software:
    1. Does it work?
    2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
[reply]
      No idea! After peer review I just commit my code and submit a ticket to QA with a description of the change. Beyond that it's kinda blurry as Operations don't let you peek over the fence much and I'm no server side guy :)
[reply]
        I'd peek over the wall, my friend. This is kinda important stuff.
        My criteria for good software:
        1. Does it work?
        2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
[reply]

In Section Meditations