[opensuse] Reason #7 why bugreporting can be incredibly frustrating ....
Bughandlers/developers that close reports just because they can't reproduce the issue. WORKSFORYOU != WORKSFORME. Most recent example: https://bugzilla.opensuse.org/show_bug.cgi?id=899714 -- Per Jessen, Zürich (0.0°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Bughandlers/developers that close reports just because they can't reproduce the issue. WORKSFORYOU != WORKSFORME.
Does anyone have a suggestion? It seems completely and utterly pointless to report a bug when it will only be looked at if it can be reproduced by the developer. If I had _ever_ taken this attitude in my 25+ years as a software engineer, my career would have been very quickly cut short. The mind boggles. -- Per Jessen, Zürich (0.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/05/2015 02:17 PM, Per Jessen wrote:
Per Jessen wrote:
Bughandlers/developers that close reports just because they can't reproduce the issue. WORKSFORYOU != WORKSFORME.
Does anyone have a suggestion? It seems completely and utterly pointless to report a bug when it will only be looked at if it can be reproduced by the developer. If I had _ever_ taken this attitude in my 25+ years as a software engineer, my career would have been very quickly cut short. The mind boggles.
I don't blame you for your frustration. I'm not a programmer, but I have worked with programmers--I'm a hardware engineer. I think the problem is, that when you and your engineering team are all in one place, you can go look at the problem first had. When the developer sees a bug report that he can't duplicate, how is he going to a) fix it, and b) demonstrate that it is fixed? I wish I could suggest a solution, but short of shipping the whole computer with the offending software, I don't see one. --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 05 January 2015 14.35:31 Doug wrote:
On 01/05/2015 02:17 PM, Per Jessen wrote:
Per Jessen wrote:
Bughandlers/developers that close reports just because they can't reproduce the issue. WORKSFORYOU != WORKSFORME.
Does anyone have a suggestion? It seems completely and utterly pointless to report a bug when it will only be looked at if it can be reproduced by the developer. If I had _ever_ taken this attitude in my 25+ years as a software engineer, my career would have been very quickly cut short. The mind boggles.
I don't blame you for your frustration. I'm not a programmer, but I have worked with programmers--I'm a hardware engineer. I think the problem is, that when you and your engineering team are all in one place, you can go look at the problem first had. When the developer sees a bug report that he can't duplicate, how is he going to a) fix it, and b) demonstrate that it is fixed? I wish I could suggest a solution, but short of shipping the whole computer with the offending software, I don't see one.
We have Internet. We shouldn't need to ship stuff around much. And why limit the tools to email and bugzilla only. I'm tempted to suggest that, in cases where the developer is unable (or unwilling, or too busy) to reproduce the bug himself, he may instead decide to offer to set up a quick video call with the bug reporter, using smartphones or something. Then bug reporter can demonstrate the bug, developer can ask questions, etc, etc., and progress may be expedited. As long as the developer takes the initiative to such a call, and is in charge throughout, it should be possible to stay out of unpaid support territory. Such interaction, even if rare, might pay back by improving community enthusiasm for testing the distro and filing bug reports. Just a thought... \Olav -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Olav Reinert wrote:
On Monday 05 January 2015 14.35:31 Doug wrote:
On 01/05/2015 02:17 PM, Per Jessen wrote:
Per Jessen wrote:
Bughandlers/developers that close reports just because they can't reproduce the issue. WORKSFORYOU != WORKSFORME.
Does anyone have a suggestion? It seems completely and utterly pointless to report a bug when it will only be looked at if it can be reproduced by the developer. If I had _ever_ taken this attitude in my 25+ years as a software engineer, my career would have been very quickly cut short. The mind boggles.
I don't blame you for your frustration. I'm not a programmer, but I have worked with programmers--I'm a hardware engineer. I think the problem is, that when you and your engineering team are all in one place, you can go look at the problem first had. When the developer sees a bug report that he can't duplicate, how is he going to a) fix it, and b) demonstrate that it is fixed? I wish I could suggest a solution, but short of shipping the whole computer with the offending software, I don't see one.
We have Internet. We shouldn't need to ship stuff around much. And why limit the tools to email and bugzilla only.
I'm tempted to suggest that, in cases where the developer is unable (or unwilling, or too busy) to reproduce the bug himself, he may instead decide to offer to set up a quick video call with the bug reporter, using smartphones or something. Then bug reporter can demonstrate the bug, developer can ask questions, etc, etc., and progress may be expedited.
I'm used to bug reports with no progress even for years, I'm sure we all are. That's frustrating too, but I don't really mind anymore. However, when the developer says "it works for me, no need to debug any further", it's just a little too much. I know I could/should be looking for more diagnostics, data, traces etc, but as I'm thoroughly unfamiliar with the territory, that's difficult without someone guiding me. The topic is auto-yast, I think I'll try the mailing-list next. -- Per Jessen, Zürich (-2.0°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 1/5/2015 11:17 AM, Per Jessen wrote:
Per Jessen wrote:
Bughandlers/developers that close reports just because they can't reproduce the issue. WORKSFORYOU != WORKSFORME.
Does anyone have a suggestion? It seems completely and utterly pointless to report a bug when it will only be looked at if it can be reproduced by the developer. If I had _ever_ taken this attitude in my 25+ years as a software engineer, my career would have been very quickly cut short. The mind boggles.
Did I mention Bruce Byfield (Linux Magazine) recently filed a bug report on bug report systems? http://www.linux-magazine.com/Online/Blogs/Off-the-Beat-Bruce-Byfield-s-Blog... and http://www.linux-magazine.com/Online/Blogs/Off-the-Beat-Bruce-Byfield-s-Blog... -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2015-01-05 22:24, John Andersen wrote:
On 1/5/2015 11:17 AM, Per Jessen wrote:
Did I mention Bruce Byfield (Linux Magazine) recently filed a bug report on bug report systems? http://www.linux-magazine.com/Online/Blogs/Off-the-Beat-Bruce-Byfield-s-Blog...
and
http://www.linux-magazine.com/Online/Blogs/Off-the-Beat-Bruce-Byfield-s-Blog...
Interesting
articles. The second one throws an interesting idea into support forums, but I'm afraid that it would not help much here, though. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlSsHvIACgkQtTMYHG2NR9VJRACfXJZ0i8paROARpOs4y6HMrWwL BpQAnRnmlb/Es0ZV6dUOcC51H0I84e4Q =X5Mp -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Carlos E. R. -
Doug -
John Andersen -
Olav Reinert -
Per Jessen