Re: Requesting a change to the BugStatusWorkFlow: Closed/UPSTREAM

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 01/20/2012 02:04 PM, Jaroslav Reznik wrote:
----- Original Message -----
On Fri, 2012-01-20 at 09:30 +0000, Tim Waugh wrote:

We already had this discussion, I don't recall exactly - two years ago
and the resolution was similar - rename CLOSED UPSTREAM to HOLD UPSTREAM.
I can try to find it :) As it's usually used this way - bug is reported
to upstream (by reporter, us in case he does not have account or is not
willing to do it), then the bug can bounce between Fedora/upstream (you
know, everyone has to blame other side or sometimes it's not easy to
say who to blame ;-). And the bug is actually not fixed in Fedora until
we receive fix - then it can go to some CLOSED RAWHIDE/NEXTRELEASE state.

The biggest problem here is just - some people misuse this CLOSED UPSTREAM
as we don't care in Fedora. And they would use another CLOSED resolution
to close the bug :)
... and why no simply keep these BZs "open" and/or to add a note "Reported upstream" and keep abrt open to receive more of them
(This would at least provide an indicator for the severity of a bug)?

 This would at least reflect the actual situation in Fedora:
  Bug is still present.

Ralf
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux