On Tue, 08 Sep 2009, Piotr Engelking wrote:
> > If the bug is not fixed in that version, use found. nontfixed *only*
> > exists to remove erroneous fixed versions with no additional side
> > effects.
> 
> But the bug was marked as fixed in a version that never existed, so
> 'found' would not really be appropriate. Besides, it carries a
> stronger meaning (that I verified that the bug occurs in this
> particular version).

If you've verified that the bug isn't actually fixed in that version,
then it should be found. If it was erroneusly marked as fixed, and
there aren't any versions that the bug should be fixed in, use
found+notfound or reopen, or similar..

notfixed is primarily there because it enables you to play with the
list of fixed versions without additional side-effects such as
reopening the bug.

> There is of course still 'reopen', but it's not generic enough - it
> clears the entire fixed versions history (which wouldn't matter for
> this particular bug, but would for others).

In any of these cases, you want notfixed+found or something similar.

Which bug are we talking about, though? [It's easier for me to
actually talk about specific examples and clarify the documentation if
it doesn't address a case than generalities.]
 
> Hmm... I guess I should wait until I see the updated documentation
> before I comment further.

This is what it was changed to:

    This command is equivalent to <code>found</code> followed by
    <code>notfound</code> (the found removes the fixed at a particular
    version, and notfound removes the found) with the exception that
    the bug is not reopened if the found version is greater than any
    existing fixed version. It is intended for fixing mistakes in the
    record of when a bug was fixed; in most cases, you actually want
    <code>found</code>, not <code>notfixed</code>.


Don Armstrong

-- 
"Facts" are the refuge of people unwilling to reassess what they hold
to be "True".

http://www.donarmstrong.com              http://rzlab.ucr.edu



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to