Closing bugs UPSTREAM

[Mike A. Harris]

On Sun, 22 Feb 2004, Michel Alexandre Salim wrote:

>> Hello Mark,
>> 
>> > 	We want to work upstream as much as possible.
>> 
>> With this I firmly agree. But that does not mean that bugs that are
>> fixed locally (ie by applying upstream patches or update releases)
>> should be closed as UPSTREAM, because in relation to the distribution
>> they are fixed CURRENTRELEASE.
>> 
>[snip]
>But would not CURRENTRELEASE indicate that an update has been released
>by the distributor (Red Hat/Fedora) ? It's similar to RAWHIDE which
>indicate that the bug has been closed in the development tree.

CURRENTRELEASE means you filed a bug report for an older version 
of the OS, which is fixed in the current version of the OS, or in 
an erratum update for the new OS, but it is not fixed in any 
erratum for the OS release that you filed it for, and there is no 
plan to do so.

For example:  Someone files a bug report against XFree86 for Red 
Hat Linux 8.0 tomorrow.  I look at it and immediately know that 
this problem is not present in RHL 9 or FC1.  Alternatively, 
maybe it is in RHL 9 or FC1 but has been fixed in an update to 
FC1.  I close it as "CURRENTRELEASE".

The rough translation being "this is fixed in the current version 
of our operating system, or by an update to the current version.  
We wont be fixing this problem as an update to the version of the 
OS that you are using.  Please upgrade your OS."

Something like that anyway.


-- 
Mike A. Harris     ftp://people.redhat.com/mharris
OS Systems Engineer - XFree86 maintainer - Red Hat