> > 2.3. Upstream issues > > > > Do not close a bug (as RESOLVED/UPSTREAM) until it is fixed by > > upstream. > > This implies that the upstream is alive enough to fix it. > > I feel it should mean that the bug has been reported to upstream, and > that state is documented in the bug. > > If we keep every upstream bug open instead of closed, we'd have probably > another 2500 open bugs (5312 RESO/UPSTREAM in the history of Gentoo, and > I'm ballparking that 50% aren't actually fixed yet upstream).
Some teams are already tracking (some) upstream bugs like this. E.g. kde. This is another case where RESOLVED does not really apply. We'd really need an alternative category, e.g. DEFERRED. Meaning the problem is still there but we can't / won't do anything about it now. The bug is not resolved but remains as a silent reminder. Then, RESOLVED UPSTREAM -> DEFERRED UPSTREAM RESOLVED LATER -> DEFERRED LATER Cheers, Andreas
signature.asc
Description: This is a digitally signed message part.
