if this was the case, it usually indicates an incomplete report (i.e a convoluted example file, or irreproducible bug in trunk)
Be careful with your reasoning, son! This forum is already polluted with too many narcissistic big-headed kiddies, don’t add one more to it.
I’ll make bug reporting only if they make the process less time consuming and more straightforward. I’m not a student who has so much free time to spend. I’d completed my degree more than two decades ago. I’ve a few businesses to run at hand, time is just too precious for me. Don’t make assumption!
Concerning sdfgeoff’s remark, it’s important to stress that developers don’t go looking for bugs. To do so would require an inordinate amount of time, and patience, because it’s tedious as hell. Instead, we rely on regression tests (for which the BGE has few to its name), and bug reports. If you do not report a bug, there is little guarantee developers will be made aware of it. Furthermore, even if you mention it to a developer, others are not aware of this situation, and thus cannot benefit from the information made public by the bug reports.
I’ll make bug reporting only if they make the process less time consuming and more straightforward. I’m not a student who has so much free time to spend. I’d completed my degree more than two decades ago. I’ve a few businesses to run at hand, time is just too precious for me. Don’t make assumption!
I’d be interested in hearing more about your thoughts on this process. As far as I can tell, the process as it stands is quite straightforward. You choose a category for the bug, write a short descriptive title, lengthier but concise body and attach an example file for reproduction, followed by a priority tag.
Arguably the main point of conclusion is that you are justified in complaining about bugs if developers are aware and ignoring them (though, of course it’s their own free will), otherwise it’s unreasonable to expect all for nothing!