3 ms·
That's almost complete... there's another three question flow which gets to yes. 1) Is stuff really badly broken? 2) Was the really bad breakage introduced re
by brongondwana 7y ago
That's almost complete... there's another three question flow which gets to yes.
1) Is stuff really badly broken?
2) Was the really bad breakage introduced recently (this could either be an earlier bad rollout, or it could be external factors changing)?
3) Is this requested deploy either a revert of a recently-made bad change or the minimal possible fix/bandaid?
If all three of these are true, then you can do a deploy RIGHT NOW regardless of the calendar.
(recently - because if this is something which has been broken for years then it's unlikely that it suddenly became urgent absent external change - which is already carved out above)
- michaelt 7y agoSo what you're saying is, it's acceptable to deploy on Friday at 5pm if and only if you're undoing the damage caused by some chump deploying on Friday at 4:55pm?
- Piskvorrr 7y agoYes. And then to find out why a DEFCON-1 level revert was necessary at all: that's a deploy that you want to be prepared for, but you never want to use.
- brongondwana 7y agoOr some data corrupting bullshit that was released on Thursday and it's taken you that long to notice but it's causing ongoing damage.