Discuss and adopt processes that focus on rolling out scary changes |
||||||
Issue descriptionDiscuss and adopt processes that focus on rolling out scary changes, e.g. changes to tools, late in the day/week - this has been discussed in prior post mortems and is a policy, but not yet enforced Context is https://docs.google.com/document/d/1KzPTGYToPJXpCgX1HG8EcIF6Xy7RBYlKaqPpGl-tGeY/edit# We've talked about this before, and I think chrome infra knows a lot of these ideas, but we might need to disseminate this information to chrome devs who change infrastructure code. I'm not sure what the best way to do this is. Ben, we should figure out what the best way to do this is.
,
Dec 6 2016
Ok. 1. I'll ahve to talk to a few people 2. We'll have to come up iwth a universal proposal - one that addresses this from a high level. 3. We cover some of this in the PRR, so I'm adding Aaron.
,
Jan 10 2017
Erik - handing off some work to you.
,
Sep 18
,
Oct 10
Unassign myself. This is not on my plate ATM. It might be useful for SRE to think about this more as part of PRR.
,
Jan 11
Assigned, but no owner or component? Please find a component and/or owner |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by benhenry@google.com
, Oct 24 2016