3 ms·

Nobody would deploy such a change on a Friday afternoon though

• xeonmc 3y ago
  #famouslastwords
• alfanick 3y ago
  It kinda makes sense though to do it on Friday afternoon, as on the weekend enterprises and most people just go skiing or do other things so less of customer base is affected in case of (unfortunate) outage.
  • ta1243 3y ago
    Even if that were a fact, then that's the one time github should not be updating. Their customers will be doing deployments on a Friday afternoon, thus require their repositories for their internal processes to work
• paulddraper 3y ago
  What day is the best day to have downtime?
  • ta1243 3y ago
    Depends on your business. For my workflow we are happiest with risk for weekdays 0930-1130 and 1400-1600, and Saturday from 0500-1100, but it varies depending on the affected systems and workflows. If I'm doing work on one systems used by Department A then a Saturday is great. If it's on Department B though Saturday is the worst possible time. Department C's systems are mainly used from 2000-0700. Department D's systems are used 24/7, which is why we have geographic resilience. But you don't get to choose this with XaaS. It goes down when it goes down, it comes up when it comes up. Our connectivity supplier sends us a notice that "circuit from X to Y will be going down from 0200-0500" and we have no choice but to accept it. Typically updates are best done on Tuesday morning given that most people are awake and working and thus if there are problems they can fix it, but you wouldn't go ahead while the resilience is down (say due to a fibre cut, or a power outage)
    • deleted 3y ago
      [deleted]