This PR is a follow-up to incident 161. In the review discussion, we agreed that it makes sense that incidents affecting staging, but not production, still go through the same process. This just adds instruction to that effect in the incident playbook.
If everyone is on board I'll share the change in #dev, as a follow-up.
Note: we had discussed in the call that we keep the discussion to #dev, and not use #incidents when it just affects staging. While finalizing the postmortem, It seemed overly confusing to have two different processes. So, instead, I just added a line here to emphasize the scope of the incident should be communicated.
Happy to change course if anyone feels this was a bad call.
This PR is a follow-up to incident 161. In the review discussion, we agreed that it makes sense that incidents affecting staging, but not production, still go through the same process. This just adds instruction to that effect in the incident playbook.
If everyone is on board I'll share the change in #dev, as a follow-up.
Note: we had discussed in the call that we keep the discussion to #dev, and not use #incidents when it just affects staging. While finalizing the postmortem, It seemed overly confusing to have two different processes. So, instead, I just added a line here to emphasize the scope of the incident should be communicated.
Happy to change course if anyone feels this was a bad call.
PLATFORM-4789