| 1 |
> > 2.3. Upstream issues |
| 2 |
> > |
| 3 |
> > Do not close a bug (as RESOLVED/UPSTREAM) until it is fixed by |
| 4 |
> > upstream. |
| 5 |
> |
| 6 |
> This implies that the upstream is alive enough to fix it. |
| 7 |
> |
| 8 |
> I feel it should mean that the bug has been reported to upstream, and |
| 9 |
> that state is documented in the bug. |
| 10 |
> |
| 11 |
> If we keep every upstream bug open instead of closed, we'd have probably |
| 12 |
> another 2500 open bugs (5312 RESO/UPSTREAM in the history of Gentoo, and |
| 13 |
> I'm ballparking that 50% aren't actually fixed yet upstream). |
| 14 |
|
| 15 |
|
| 16 |
Some teams are already tracking (some) upstream bugs like this. E.g. kde. |
| 17 |
|
| 18 |
This is another case where RESOLVED does not really apply. We'd really need an |
| 19 |
alternative category, e.g. DEFERRED. Meaning the problem is still there but we |
| 20 |
can't / won't do anything about it now. The bug is not resolved but remains as |
| 21 |
a silent reminder. |
| 22 |
|
| 23 |
Then, |
| 24 |
RESOLVED UPSTREAM -> DEFERRED UPSTREAM |
| 25 |
RESOLVED LATER -> DEFERRED LATER |
| 26 |
|
| 27 |
Cheers, Andreas |
Archives