| 1 |
On 02/05/2016 03:47 PM, Rich Freeman wrote: |
| 2 |
> The main problem I see with auto-assignment is that some asignees end |
| 3 |
> up being black holes for bugs. If two active devs get their bugs |
| 4 |
> crossed it isn't a big deal since they'll just reassign them to each |
| 5 |
> other. If an active dev gets their bug assigned to an inactive dev, |
| 6 |
> they might never hear about it. |
| 7 |
> |
| 8 |
|
| 9 |
We already trust users to tell us what went wrong and put bugs in the |
| 10 |
right component. I think we can trust the package atom if one exists in |
| 11 |
the summary. How about, if there's (exactly) one portage-compatible atom |
| 12 |
in the summary and that package has (exactly) one maintainer, we |
| 13 |
auto-assign it? Otherwise, leave it to the bug wranglers. |
| 14 |
|
| 15 |
That's easy and won't create any problems we don't already have. |
Archives