Mathias Bauer wrote:
Rich wrote:
i was filling an issue and again i thought - why the hell are there all
those old builds in version field - like m13 - anybody, m13, no ?
even if somebody would file an issue with 680m13, answer probably would
be to check with later build. finding the correct build in that small
window is possible, but hard enough. why are there all those old builds
? is there really _any_ use for them ?
I don't know where you're aiming at. If a build is referenced in this
field it doesn't mean that this build exists anywhere, it's just the
information about when the reporter stumbled over it.
of course. i'm rumbling about availability of these versions when users
file a new issue. i understand reasons you mentioned and, of course,
completely agree with them - it's just that a lot of records in a small
listbox are hard to use.
The information about the build number where a particular issue was
reported for is important for developers even if the build doesn't exist
in binary form anymore. If the bug doesn't appear in newer versions
anymore they can assume it's fixed and close the issue (that's different
than a "works for me" if the build information is not available). In
cases of very important issues (where the pure assumption that the bug
is fixed isn't enough and you want the prove) it would still be possible
to create a build with that ID just to verify if the issue was *really*
visible in that build and if it was *really* fixed afterwards.
Additionally the build ID can be used to track changes in the source
file revisions that might be related to the issue or its resolution.
Best regards,
Mathias
--
Rich
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
