> That doesn't make any sense since a fixed bug would be closed.
Not until after time is spent trying to reproduce/understand the bug.
If you know when it was last seen, you can confirm that you are
triggering it correctly, but that it no longer exists in the current
version.
>> interpretation, u
x27;ve noticed a lot of people lately updating the trac version field of to be
more recent. For example changing version from 1.0 to 1.2 or 1.1 to SVN. I
thought this field was supposed to track the version against which a problem
was written -- that is, the version of code in use by the reporter of t
erpretation, updating the version is a mark that you've tested it
in a newer version and that the problem still exists as described.
-FM
On Thu, May 27, 2010 at 1:55 PM, Karen Tracey wrote:
> I've noticed a lot of people lately updating the trac version field of to be
> more recent.
I've noticed a lot of people lately updating the trac version field of to be
more recent. For example changing version from 1.0 to 1.2 or 1.1 to SVN. I
thought this field was supposed to track the version against which a problem
was written -- that is, the version of code in use by the report
