| ▲ | ecshafer 5 days ago |
| In a financial company I worked at we would do some of the biggest, riskiest changes at 5pm on a Friday (or Saturday evening if we were worried about impacting international trades). The logic being that we would have the most time to fix things before markets open monday. |
|
| ▲ | NikolaNovak 5 days ago | parent | next [-] |
| Our release window is Saturday morning. All the support people are on, most users are not, gives us 36hrs.
We absolutely do not release during week if we can help it. But we are traditional ERP application so pretty much everything we do is contrary to the HN/modern zeitgeist :-) |
| |
| ▲ | signal11 5 days ago | parent | next [-] | | Being able to release safely during the week is super important for eg financial services, for fairly obvious reasons. In trading and market making contexts for instance, we release 100s of times a day — including Fridays. This includes bog-standard infra changes like roleswaps and server rebuilds. The releases that happen on weekends tend to be highly disruptive infra changes, eg unexpected changes to some kind of physical connectivity where we’re not comfortable with carrying weekday risk. We didn’t explicitly set to to optimise QoL for engineers (the real driver for safe intraday change was being responsive as a business) but not usually being on call on weekends was a big plus. | |
| ▲ | Scoundreller 5 days ago | parent | prev [-] | | > All the support people are on Either Rogers thinks it can’t make mistakes, or nobody was informed that a potential enterprise breaking change was taking place. Took some hours to get any official indication from them (partly because of their employees dependency on the service they provide). |
|
|
| ▲ | atemerev 5 days ago | parent | prev | next [-] |
| Yes. It is either Friday evening or Sunday in finance. |
|
| ▲ | Scoundreller 5 days ago | parent | prev [-] |
| Well this was like 6AM Friday Eastern time, soooo… |