Reporting and tracking regressions across the ecosystem
summary
Mail-list reports become tracked by sending a rebot command in mail, then the system watches replies, patch submissions and link and closes tags to mark fixes and auto-resolve when a commit lands. A web UI and weekly report to Linus summarize status; rebot exposes data as JSON export for external systems. Ongoing work: GitHub/GitLab issue support, UI filtering between actionable and non-actionable reports, and careful CI integration (KCI) to avoid creating noisy, unsalvageable trackers.
AI-written summary · about
chapters (6)
- 0:00Introduction to regressions
- 1:51Current regression tracking
- 7:56Rebot demo and features
- 14:56Tracking regression lifetime
- 23:26Closing the CI data loop
- 27:54Future improvements and Q&A
related talks
44mRegression tracking & fixing: current state, problems, and next steps
30mRHEL Kernel Workflow using GitLab
25mTracking repository health at scale
24mNetworking track kick-off
18mRed Tide Revert
38mFrom Backlog To Breakthrough: How FreeBSD and Bitergia Tackled 7k+ Bugs With Data-Driven Dashboards
26mImprove Upstream Code Quality by Bringing Testing to Patch Level
08mAll eyes on Open Source: Monitoring community sovereignty