Replies: 1 comment
-
Follow up on the feedback from the BuildCaptain Runbook:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Context
This is a follow-up on #56 (comment).
Goal
[1] Speed-up the feedback-loop on contributions across Issues, Pull Requests.
[2] Maintain the latest state of the project healthy(e.g. triage nightly CI failures)
How to?
Introduce a rotation across owners with a best-effort approach. The frequency of the rotation per individual tbd(daily, weekly).
The rotation should consider the following(at least at the beginning):
What's next?
Define if this rotation applies to all projects under shipwright-io.
Define the rotation participants and frequency.
Define communication channels for the rotation.
Define rotation hand-over.
Define the Runbook contents. For example:
Which pieces could be automated?
Additional Context
The above is based on Tekton BuildCaptain Runbook Proposal
Beta Was this translation helpful? Give feedback.
All reactions