Ours are 8 weeks, with interim drops in between. Mainly this is to match our clients' cycles; we used to go more often but the clients found that to be too disruptive.
I suspect that retail sites like yours and Todd's have different concerns.
The less there is in a push, the easier it is to get it out the door and the smaller likelyhood of serious problems. Let stuff pile up and potential bugs start interacting with each other. Plus if you have to back something out, then you have a mess of figuring out what depends on what.
Cheers, Ben
I have come to believe that idealism without discipline is a quick road to disaster, while discipline without idealism is pointless. -- Aaron Ward (my brother)
Everybody is on their own cycle and getting a release out isn't a big deal. App servers (written in C++) go out monthly. Other stuff ships as completed. To ship something, push it to staging, QA will do full regressions every other day of what is there and push it to production if it passes muster.
Deployments are pushbutton automated and can be rolled back with another button.
Working with mature infrastructure is such a joy.
"Whenever you find you are on the side of the majority, it is time to pause and reflect" --Mark Twain
"The significant problems we face cannot be solved at the same level of thinking we were at when we created them." --Albert Einstein
"This is still a dangerous world. It's a world of madmen and uncertainty and potential mental losses." --George W. Bush
Edited by tuberculosis
Aug. 21, 2007, 12:44:16 PM EDT