SprintPilot
Jelle van der Waa edited this page Feb 6, 2024
·
20 revisions
On each two-week sprint there is some designated Cockpit developer responsible for maintenance tasks. Delegation, asking for help etc. is of course possible, but the Pilot is responsible for the coordination and that the tasks get done.
- Image refreshes and image build failures: Investigate, debug, report, and work around/adjust/naughty regressions. There should not be any open PRs/issues that are open for longer than a few days.
- Keep an eye on pull requests, especially from outside contributors, and make sure they get responded to, get appropriate reviewers assigned, and don't get stuck on trivial things or negligence. Review PRs or ask someone to review them. Retry tests if needed.
- Keep up with bots created PRs in all repos. These include dependabot, po-refreshes and naughty-prune: cockpit.
- Other issues tracked on our Pilot Tasks project
- While watching over PRs be aware of tests. Are there some stability issues? Is some test broken (report it or fix it)? Are tests slower? Keep an eye on our Grafana and the CI weather report
- In the middle of the sprint, do the releases of all our projects that have significant changes.
- Pilot is also a good time to invest time in improving bots and tests in general. Go wild 😀
Pilot duty rotates between these team members:
The current pilot is mentioned in the cockpit Matrix channel topic