On bugs and docs
speeddymon at gmail.com
Tue Mar 20 16:12:02 CDT 2007
On 3/20/07, James Hawkins <truiken at gmail.com> wrote:
> On 3/20/07, Tom Spear <speeddymon at gmail.com> wrote:
> You shouldn't be searching all bugs when filing a new bug...the reason
> to search for bugs (in the case of a new bug report) is to make sure
> you're not making a duplicate report. A new bug can't be a duplicate
> of a closed bug (technically not always true, but for all intents and
> purposes, the generalization can be made).
Thats just the problem. Not all users are using the latest and
greatest wine and those that aren't usually dont realize they aren't.
So if we resolve or close a bug because it's fixed in the latest
snapshot, if we dont search all bugs, then the user doesnt find it and
we end up with duplicates.
While technically you are right a user could be using the latest
snapshot and have a closed bug come up too, if they have done enough
research to search for their bug first, then they will probably be
able to tell by the comments in a closed bug that that particular bug
applied to an older version and therefore the symptoms need to be
documented and so they need to file a new bug.
It is kind of a catch 22 because if we leave it as is, then we get
dupes, but if we change it then a new bug that is like an old one but
caused by different symptoms may not get reported right away.
Perhaps a new option under user preferences for beginner search (where
it doesnt search all bugs) and non-beginner search (where it does),
and then still have the different search pages too would be nice.
Could either of the above changes conceivably be made in our local
Check out this new 3D Instant Messenger called IMVU. It's the best I
have seen yet!
More information about the wine-devel