4 ms·

In an ideal world you'd never deploy on a Friday, but we've probably all done it.

• jeremyjh 8y ago
  Deploying on a Friday is fine for many businesses - but it becomes riskier if you are leaving to a remote location with no internet access.
  • klodolph 8y ago
    Even if your automation is great, there’s often a series of events that goes like this: Error discovered -> Call person responsible -> Roll back It’s not just about whether you have the ability to fix the error, it’s about whether deploying on Friday is likely to disrupt people’s personal lives. Or, put another way, it’s not kind to deploy on Friday, it’s selfish. It looks good if you push out features quickly, and if it blows up someone else has to take time out of their weekend. On my team ops controls releases and if you miss the Thursday build you’re not getting anything in production until Monday.
• RobertRoberts 8y ago
  We have a company policy to never deploy on Friday, and only under ideal circumstances on Thursday. This protects everyone from unneeded overtime and panicking clients during off hours. It's one of the central policies to ensure happy clients and smooth running operations that gets regular review and questions from clients when they are in a hurry. But when it was implemented, stress levels across the board plummeted. And only a small amount of client education was needed before they agreed it was a good policy. There are emergency circumstances that override this rule of course.