-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-04-02 at 21:10 +0200, Henne Vogelsang wrote:
And here you have perfectly described the misunderstanding that happens constantly on a public bug reporting tool.
User: I want to do A and then B happens. I try to understand why B happens and it turns out that it shouldn't. So i tell the developer that and he will solve my problem.
Developer: I write A and then release it. A has 63 problems because there is no bugfree software. Now a user comes with the 64th problem and does not even provide a backtrace. Why did he not send a patch?
As you can see those are two valid views on the same situation. The solution to this is that both try to get closer to the others side.
There is a third situation: the user supplies the required info, there are precise logs, kernel OOps, etc, but the bug is not solved and remains open for years (literally). I can tell you that it is quite frustrating. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknVTXwACgkQtTMYHG2NR9XbmgCbBH014BIFeyhGoMmvJaex8rOF DKAAn1C7rqfOo5fzd4a5sAs+IOZAMPjG =MLot -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org