4 ms·
Two big companies I've worked have generally followed the same progression of deployment times: Stage One: Right after work on Friday (until some big client th
by jtbigwoo 13y ago
Two big companies I've worked have generally followed the same progression of deployment times:
Stage One: Right after work on Friday (until some big client that files all their payments on Friday afternoon complains.)
Stage Two: Late on Friday night (until problems arise and all but one of the mainframe admins have gone camping for the weekend.)
Stage Three: Late on Thursday night (until problems arise the next morning and half of the DBA's are on vacation and the other half are "working from home")
Stage Four: Late on Wednesday night (until problems arise that take the system down for 18 hours and impact clients on Thursday morning.)
Stage Five: Right after work on Friday.
- kirillzubovsky 13y agoSo basically, they got to the point where everyone knew that Friday after work was _the_ time, and it was your job as a user to avoid that timeframe? Not ideal, but I see it working well, especially for banks.
- danudey 13y agoI worked at a company that had a policy of no changes to production on Fridays, unless our service was completely down and we were losing people's money. Given that it was the sort of place where one developer didn't have access to deploy code and had to go walk a senior developer through making the changes by hand (and we didn't use a revision control system), that was probably an optimal circumstance.