Closing bugs

[Nils Philippsen]

On Wed, 2006-09-06 at 23:38 +0200, Axel Thimm wrote:
> On Wed, Sep 06, 2006 at 10:19:27PM +0100, Jeremy Sanders wrote:
> > On Wed, 6 Sep 2006, Jesse Keating wrote:
> > 
> > >These reference the release of the package, not of a distribution. 
> > >NEXTRELEASE
> > >could be the next release of the package, CURRENTRELEASE is the release of
> > >the package you've built into the devel repo or the FC-5 repo, or whatever.
> > >Rawhide is well rawhide.
> > 
> > Thanks - those answers make sense.
> 
> No, here are the definitions which more or less relate "RELEASE" to
> the distribution and not the package's upstream version. That's also
> how it's used in RHEL - we should keep the same semantics behind these
> keywords.
> 
> CURRENTRELEASE
>     The problem described has already been fixed and can be obtained
>     in the latest version of our product. Information on the package
>     version in which it was fixed should be included in the summary
>     when a bug is closed to this resolution.
> 
> NEXTRELEASE
>     The problem described has been fixed in the next release of the
>     product, and is not planned to be fixed in the release against
>     which the bug was filed. Include information on the release in
>     which this was fixed in the summary when a bug is closed to this
>     resolution.
> 
> So if you fix an FC5/FC4 bug you should use CURRENTRELEASE.

Nope, rather use ERRATA if you fix it for the FC version in question,
RAWHIDE if only for fixing it in development (and not planning to do it
for the FC version reported against) instead as CURRENTRELEASE is only
for stuff already fixed at the time of reporting the bug ("already"
being the keyword in the description above ;-).

Nils
-- 
     Nils Philippsen    /    Red Hat    /    nphilipp at redhat.com
"Those who would give up Essential Liberty to purchase a little Temporary
 Safety, deserve neither Liberty nor Safety."  --  B. Franklin, 1759
 PGP fingerprint:  C4A8 9474 5C4C ADE3 2B8F  656D 47D8 9B65 6951 3011