<br><br><div class="gmail_quote">On Mon, Mar 17, 2008 at 12:20 PM, James Kosin <<a href="mailto:jkosin@beta.intcomgrp.com">jkosin@beta.intcomgrp.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
</div>max bianco wrote:<br>
|<br>
| << SNIP >><br>
<div><div></div><div class="Wj3C7c"><br>
| |<br>
| | +1, to a point.<br>
| |<br>
| | If the "maintainer" has (reasonably) asked for more information<br>
and it<br>
| has been 1 release with no more information coming in, _then_ it would<br>
| be reasonable to close the bug.<br>
| |<br>
| |<br>
| But, iff the release addressed an issue related to the bug report<br>
in the<br>
| first place. Closing a bug just because you don't have any more<br>
| complaints is not really a valid reason.<br>
|<br>
|<br>
| How long should it be kept open if no more information is forthcoming?<br>
|<br>
|<br>
|<br>
| Maybe part of the release process should be to recreate the<br>
problem and<br>
| be able to prove the problem is fixed by testing!<br>
|<br>
|<br>
| How do you know the bug is real? The person reporting the bug needs to<br>
provide enough information to reproduce the issue. What is essential info?<br>
| I think a bug reporting tool that is integrated into the desktop<br>
itself is going to be required here. The tool could walk a user through<br>
the bug reporting process and maybe insure that appropriate logs are<br>
attached by default, at least we need to ensure that enough info is<br>
provided to reproduce the problem. Sometimes people report as bugs<br>
things that are not bugs and alot of time gets wasted. If we want all<br>
bugs fixed in a timely manner then we have to provide the developers<br>
the means to do so and i think that means some sort of integrated bug<br>
reporting tool that ensures that a minimum amount of info is provided<br>
for them. How many times has someone cursed the application only to find<br>
that they overlooked something simple? Everyone has their own custom<br>
setup and that can make reproducing a problem difficult.<br>
|<br>
|<br>
| Max<br>
|<br>
<br>
</div></div>Max,<br>
<br>
I was commenting on the assumption it was a valid BUG. It is difficult<br>
if not impossible to catch everything. If a bug is or does not contain<br>
enough information then it really isn't a bug yet.<br>
<br>
I agree we need a better method to capture the problem and provide<br>
enough information to reproduce the problem elsewhere, but whose<br>
responsibility is that. The bug reporter often either knows very little<br>
of the problem or has caused the problem himself in most cases; but,<br>
some are caused by others.... selinux security settings for example,<br>
and when fixed sometimes ILL documented in the release notes.<br>
At the same time, the user needs to keep on top of his/her bugs and<br>
update them as needed. Just ignoring a bug can lead to BAD things for<br>
both parties. The user in that the problem may not be fixed (causing<br>
issues for others in the future) or worse still the maintainer not<br>
knowing what the true bug status is.<br>
<br>
At the same time, we shouldn't take bug reports lightly. They are<br>
difficult enough for users to write up properly, so anyone taking the<br>
time to actually write one up should be looked at carefully.<br>
<br>
Some standard questions should be (1) post configuration files, (2) post<br>
any pertinent log files, (3) core dumps if available.<br>
At the same time, the maintainer needs to be able to provide the user a<br>
way to DEBUG the issue. Not everyone is experienced in the debugger<br>
tools or how to get a trace, or dump of any core files.<br>
<div class="Ih2E3d"><br></div></blockquote><div><br>I think we agree on the major points. It is precisely because not everyone is an experienced debugger that I think some sort of integrated tool is required. An integrated tool that would default to attaching appropriate log info is essential. Better to much info than not enough. How many will tell on themselves if they figure out it was their fault? Not many! Most will never report back, in which case you have a bug report floating around that can never be resolved because it was never a bug to begin with....or due to inexperience on the users part it takes forever to get the required information. So some kind of bug reporting\ debugging tool is needed. I don't think you will find many objections to the idea in theory but the rub will be in how it gets implemented.<br>
<br>Max<br></div></div><br>