| 1 |
On 03/30/2017 07:52 PM, William Hubbs wrote: |
| 2 |
|
| 3 |
|
| 4 |
> |
| 5 |
> I disagree with resolved/invalid being appropriate. That means it isn't |
| 6 |
> a bug at all. Resolved/upstream should be used when we direct a user to |
| 7 |
> file an issue upstream or file the issue ourselves. |
| 8 |
> |
| 9 |
> Resolved/upstream acknowledges that this is an issue but directs it |
| 10 |
> upstream. Resolved/invalid says this isn't an issue. |
| 11 |
> |
| 12 |
|
| 13 |
If it actually is a bug affecting users it shouldn't be closed to begin |
| 14 |
with but kept open , this would be appropriate use of the UPSTREAM |
| 15 |
keyword after filing the bug and preferably updating URL field to point |
| 16 |
to bug report. |
| 17 |
|
| 18 |
From a gentoo point of view, the issue would require fixing and |
| 19 |
stabilization before the bug is closed. |
| 20 |
|
| 21 |
-- |
| 22 |
Kristian Fiskerstrand |
| 23 |
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net |
| 24 |
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 |
Archives