kernelci / kernelci/kernelci-project
Developer: Getting informed of regressions
- Dominant language
- Python
- Stars
- 14
- Forks
- 32
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 3
Description
**As a kernel developer, I want to be informed of regressions caused by my patches so I can reproduce and investigate them.**
## Background
*Please provide any extra information about this user story such as what led you to create it or any examples to illustrate it.*
## Thank you!
Thanks for adding a user story and contributing to improving KernelCI's user experience. It should soon appear on the user experience [workboard](https://github.com/orgs/kernelci/projects/18/) so we can keep track of it.
*This issue template was inspired by an [Atlassian article](https://www.atlassian.com/agile/project-management/user-stories) on user stories.*
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points to inspect. First clarify how regressions should be detected and delivered to kernel developers, including acceptance criteria for reproduction and investigation; the work is done when that workflow and its implementation scope are defined.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100