On Tue, May 31, 2011 at 2:50 PM, Alex "Mr.Z-man" mrzmanwiki@gmail.comwrote:
On 5/31/11, Trevor Parscal tparscal@wikimedia.org wrote:
There's been tons of discussion about what is an ideal release schedule
for
us (probably literally if you printed it out at 12pt on standard copy paper). At this point I think we are balancing between fighting the bad habits that got us into the 1.17 rut, and trying to give our engineering team enough time to do significant work (rather than spending 1 day a
week
pushing code).
One issue is that "time spent deploying" does not appear to be independent of "time between deployments." If it always took a day to deploy new code, that would be a good argument in favor of more time between deployments. But in practice, the more time that passes without pushing code to the site, the longer it takes to complete the deployment. Spending a week deploying every other month doesn't really save much time over spending a day every week.
I'd actually consider it pretty ideal to spend a day every week deploying updates, gathering feedback, and making fixes. Rather than an argument in favor of longer cycles, I'd consider that an argument in favor of shorter cycles!
-- brion