| Summary: | patchwork: auto-delegate patches | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Patchwork/Patchtest | Reporter: | Paul Eggleton <bluelightning> |
| Component: | Patchwork | Assignee: | Paul Eggleton <bluelightning> |
| Status: | RESOLVED WONTFIX | QA Contact: | Apoorv <apoorv.sangal> |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | anibal.limon, benjamin.esquivel, jose.perez.carranza |
| Version: | unspecified | ||
| Target Milestone: | Future | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
| Bug Depends on: | 9130 | ||
| Bug Blocks: | |||
|
Description
Paul Eggleton
2015-04-24 09:59:05 UTC
(In reply to comment #0) > It would be useful if Patchwork could be made to automatically delegate (or > otherwise assign) patches to a reviewer based on a set of rules. These might > be a regex on the path of files modified by the patch, or on subject, etc. I agree, it need to be defined in a resource file like maintainers.inc that works for recipes. Who should define it? Upon reflection I don't think this will practically work for our project. If patchwork is reliable and we keep an eye on the queue then we shouldn't need this anyway. |