[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: "version" field in IssueZilla

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2005-01-25 22:17:07 CET

Max Bowsher wrote:
> Greg Hudson wrote:
>> [...] The "found in version" field gives
>> a hint which you can use to narrow down the possible reasons.
> Ok, that makes sense - but in that case, I think we need a policy of
> tidying up the field during initial triage of filed issues.
> Something like:
> -> "trunk": Bug exists on trunk (and possibly branches).
> -> "1.?.x": Bug does NOT exist on trunk, only on release branch.
> -> "---": Issue is independent of code version - e.g. website or
> translations.

No. For one thing, it would be horribly confusing to try to keep track of the
change of meaning of this field from "Initially found in version ..." to "This
is the group of versions that we have determined the bug exists in." For
another thing, it's sometimes a large amount of work to determine which
versions a given bug exists in.

Instead, we just need to make clear the meaning of the field. Let it be
"Initially found in version ...", where "---" means the information is not
provided or is irrelevant. That much is clear to the initial reporter anyway,
because the form says "Found in version:". It's only after that that the
confusion begins, because the field is then labeled just "Version" and has no
help attached to it. We need to change the label and/or attach some help text
to it, if at all possible.

- Julian

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 25 22:18:19 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.