Closing bugs UPSTREAM

Mark McLoughlin markmc at redhat.com
Sat Feb 21 18:42:54 UTC 2004


Hi,

On Sat, 2004-02-21 at 18:04, Leonard den Ottolander wrote:
> Hello,
> 
> I would like to know what the policy about closing bugs UPSTREAM is. I
> feel resolving bugs as UPSTREAM might not be the correct approach if the
> bug will be fixed in an update. Also there is the danger of it being
> abused as an easy way out. More appropriate would be to close a bug as
> UPSTREAM if it can not be addressed locally. Bugs for which upstream
> fixes are applied are more appropriately closed CURRENTRELEASE as soon
> as the update is made available.

	My take on it is that the only bugs that *shouldn't* be closed UPSTREAM
are Fedora specific bugs and/or highly visible/important bugs. If you
identify a bug as existing upstream and you don't think the bug is
important enough to address with with an extra patch in Fedora, then it
should be tracked upstream.

	We want to work upstream as much as possible.

> An example of this is
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114498 . This bug
> will be fixed locally with the next update of gnome-panel. Thus I feel
> it should be closed CURRENTRELEASE at the release of the update, and not
> UPSTREAM.

	I wouldn't have closed this, but the end result is the same. Its fixed
upstream and the fix will be in the next update.

Good Luck,
Mark.





More information about the fedora-devel-list mailing list