| 1 |
On Sat, 2022-12-03 at 14:45 +0100, Florian Schmaus wrote: |
| 2 |
> I think having UNCONFIRMED / CONFIRMED *helps* the issue reporter, and |
| 3 |
> other (affected) persons, to decide if they need to "chase" the issue's |
| 4 |
> assigned entity. |
| 5 |
> |
| 6 |
> Assume looking at the open bugs list of a developer. If the developer |
| 7 |
> has old bugs in UNCONFIRMED state, you may want to issue a friendly |
| 8 |
> ping. Sure, strictly speaking, this would require all bugs to drop back |
| 9 |
> to UNCONFIMRED when the bug assignee changes. But even without such an |
| 10 |
> implicit mechanism, those two states provide some value. |
| 11 |
|
| 12 |
I don't understand how UNCONFIRMED/CONFIRMED makes any difference here. |
| 13 |
If I file a bug against some package, it is CONFIRMED by default. |
| 14 |
If an unprivileged user files it, it's UNCONFIRMED. In both cases |
| 15 |
the assignee didn't do anything. |
| 16 |
|
| 17 |
-- |
| 18 |
Best regards, |
| 19 |
Michał Górny |
Archives