4 ms·

My company just had to do it today in response to a critical security issue we identified in production. Saying that nobody should ever do it isn't realistic,

My company just had to do it today in response to a critical security issue we identified in production. Saying that nobody should ever do it isn't realistic, sometimes things go wrong on a Friday, sometimes you can't afford to wait 3 days to watch them become even worse.

falcolas 10y ago
IMO, if you deploy on Friday, you are promising to be available for fixing it on Saturday... which makes it not really a Friday in the sense in which it's meant. Don't deploy when you won't be around to support it is a better description; but it doesn't roll off the tongue as easily.
- deleted 10y ago
  [deleted]
- tomjen3 10y ago
  So I should just leave a security vulnerability rather than fix it on a Friday, because I won't be available Saturday?
  - falcolas 10y ago
    If it has the potential to take down your site? Unless you have someone who can fill in for you, absolutely. Really, it will come down to a cost/benefit analysis. Are your chances of the site going down due to being hacked over the weekend higher than the chances of a last minute update taking down the site? The answer is almost always no (much to a sysadmin's chagrin). If the answer is yes (i.e. another heartbleed), then you are probably going to be working through the weekend anyways.
  - niij 10y ago
    Read to comprehend, not to argue.
    - danielweber 10y ago
      Great, now what am I going to do with my life?
    - lucaspiller 10y ago
      This should on the top of every page here.
garethsprice 10y ago
It's a good rule to live by, and like all rules it can be overridden when the circumstances require. It's good to instill in your team that Friday deployments should be done only in special circumstances, or they become a habit (and people inevitably end up working Saturday). But yes, sometimes it's necessary.
admax88q 10y ago
Yay pedantry!
- Shanea93 10y ago
  I don't think I was being pedantic. The parent poster was very clear, there was nothing there for me to overstate.
samspot 10y ago
See if you like this version better: "Only deploy on Friday if you like working weekends"

falcolas 10y ago

IMO, if you deploy on Friday, you are promising to be available for fixing it on Saturday... which makes it not really a Friday in the sense in which it's meant. Don't deploy when you won't be around to support it is a better description; but it doesn't roll off the tongue as easily.

deleted 10y ago
[deleted]
tomjen3 10y ago
So I should just leave a security vulnerability rather than fix it on a Friday, because I won't be available Saturday?
- falcolas 10y ago
  If it has the potential to take down your site? Unless you have someone who can fill in for you, absolutely. Really, it will come down to a cost/benefit analysis. Are your chances of the site going down due to being hacked over the weekend higher than the chances of a last minute update taking down the site? The answer is almost always no (much to a sysadmin's chagrin). If the answer is yes (i.e. another heartbleed), then you are probably going to be working through the weekend anyways.
- niij 10y ago
  Read to comprehend, not to argue.
  - danielweber 10y ago
    Great, now what am I going to do with my life?
  - lucaspiller 10y ago
    This should on the top of every page here.

garethsprice 10y ago

It's a good rule to live by, and like all rules it can be overridden when the circumstances require. It's good to instill in your team that Friday deployments should be done only in special circumstances, or they become a habit (and people inevitably end up working Saturday). But yes, sometimes it's necessary.

admax88q 10y ago

Yay pedantry!

Shanea93 10y ago
I don't think I was being pedantic. The parent poster was very clear, there was nothing there for me to overstate.

samspot 10y ago

See if you like this version better: "Only deploy on Friday if you like working weekends"