-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
change release engineer to base load engineer #4917
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a few suggested changes
0cf56e3
to
a7b0596
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @groovecoder, looks good.
Is the base load engineer also the incident engineering lead, or do we pick the person based on the incident type?
Co-authored-by: John Whitlock <[email protected]>
Good question. It seems that we usually create an incident out of items from one of the channels that the base load engineer monitors. So I say we treat incident engineering lead like the other tasks re: base load engineer: "you may delegate the resulting task to the most appropriate party". I'll make that explicit in the doc too. |
I updated it to say: If any items found during the checks below are incident-level severity, you are likely to take the role of engineering lead for the incident unless you delegate to another more appropriate party. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new playbook makes sense! Thanks for updating this.
No description provided.