-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2009-04-03 at 14:26 +0200, Vladimir Nadvornik wrote:
On pá 3. dubna 2009, Carlos E. R. wrote:
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.
Yes, indeed, this is a third situation:
Packager - didn't write the code himself and does not know about potential problems. - can fix bugs that he is able to reproduce - debugging bugs that he is not able to reproduce is very time consuming - it basically means guessing potential problems and navigating the user through testing them. The logs, etc. are often not sufficient. - there are tasks with higher priority
IMHO bugs in this situation should be moved upstream and the original reporter is probably in a better position to do so because he can at least reproduce the problem.
I have bugs frozen for months, some even years, after I did all the requested tests and supplied all the info I was asked for. After that, not a single comment. Even for years! A new suse version is released, I retest, I comment that the bug is not solved, no answer. It is discouraging. And about moving upstream... sometimes the bug is caused by a suse patch. I can not decide to go upstream unless told to, and then, reporting upstream for somebody that is not accustomed to the ways and people upstream... is not very productive. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknWBbAACgkQtTMYHG2NR9XaXACfToUfqd4/o34E+k85Ug96dHBe /bgAn3FQ2UwKN0rdHEqRl6H+4brMiqwI =hpQY -----END PGP SIGNATURE-----