Hello, on Montag, 11. April 2011, jdd wrote:
anyway, the testers/users have no present way to figure what applications are very well tested and wich are not.
<BOfH mode> There is a way: "If it's totally broken, nobody tested it"
But the chance was I had just to build a dvd and could test them with real data.
That's probably the most important point: People test what they use/need. They don't test something they will never need or use. This is especially true for community (aka "non-paid") testers. (But you would have to pay a lot to make me testing beer *g*) (At least that's how I see it. There might be exceptions, of course.) The good thing is that we have lots of testers in our community and get a good coverage because of the different things everybody needs for his daily work (or fun - games have to be tested as well ;-)
We also should have a better understanding of who is in charge of what.
Now reporting on a mailing list (not this one!) or a forum makes sure you didn't simply made a typo.
Yes, but it also adds some additional work to the bugreporter. Therefore I'd say that step is optional.
Then if it's really a bug, how to report it?
at present, one can report:
* to some user mailing list (opensuse@, forum) and hoping somebody will followup. Most non tech people do so, it's difficult to manage
Short answer: forget it. This will not work. (Someone might in theory work as "bugzilla relay", but that makes things more difficult. What if the developer has a question? NEEDINFO to the "relay", who then has to ask the person who reported the bug in the forum...)
* to bugzilla, but who is in bugzilla? Is the problem a packaging problem, then it's probably one directly for opensuse (or packman). Is it an application problem? is there anybody to report upstream and follow the situation? It's not easy
General rule of thumb: Report it in bugzilla.novell.com. If it is really an upstream issue, the openSUSE developer/packager can still ask you to report it upstream. An additional advantage is that the bug gets known to the openSUSE packager, which can be important too (otherwise he might simply miss the bugfix because he never heard about the bug). Exceptions might apply when it comes to typos etc. (- in this case direct upstream reports might make sense.
* upstream.When I have a problem with an application I know really well, I usually report upstream, for example digikam
Yes, that's always an option if you know it's an upstream bug. It also makes sense for enhancement requests. Nevertheless, for critical bugs you should also open a bug in bugzilla.novell.com with a link to the upstream report to make the openSUSE packager aware of it.
I don't know, for example, if there is a programmer in the openSUSE team for any given application. Can we have a list (even partial). I mean something like "if you find a bug on kde or gnome, you can report on bugzilla, we have specialists, if you have a bug on kdenlive, report it upstream, noboy here can manage it" (*just examples, don't take it as is*) - the page about list of tested apps could have a mark saying: report to bugzilla, report to packman, report upstream...
You'll have a lot of fun in managing this list and keeping it up to date ;-) and as I said above, pointing bugreports to upstream by default (even if only for some packages) isn't the best idea IMHO. Nevertheless, such a list (better: a flag in the buildservice for each package) would be quite interesting. Regards, Christian Boltz -- By the way, it's a sign of how good the distribution is that we're arguing about the name and not dealing with problems in the essence of the thing. Even the overloaded servers are what an old boss of mine would have called a "success problem." [Randall Schulz in opensuse] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org