3 ms·
I don't this is specifically an Apple issue either, I've filled bug reports on quite a few different projects (mostly open source) including at least one that's
by nicholassmith 15y ago
I don't this is specifically an Apple issue either, I've filled bug reports on quite a few different projects (mostly open source) including at least one that's a full application framework and rarely do they ever move into 'confirmed' or 'accepted' status.
The entire reason of letting people add bugs is that they can be tracked, if the submitter can't track it then why would they want to add it? If you can't see a perceived benefit then you're going to lose interest in reporting the bugs which in the long term is bad for the overall package.
- frou_dh 15y agoAgreed. When I would Google about Windows / Visual Studio problems, I would get an instant feeling of futility when the "connect.microsoft.com" page design appeared. I don't think I ever saw a conclusion that wasn't a generic "we'll consider this for the future" or "won't fix" type thing.
- viraptor 15y agoI believe that at a certain size of the project you will get more incoming bugs than you can handle. Doesn't matter if it's closed/open source, who the users are or anything else. It's just a matter of the number of users / size of QA. Basically over some threshold you'll get conflicting behaviour expectations, duplicates formulated differently so they cannot be linked, QA finding more tiny issues in every release than bugfixes going in, etc. At least that's what I've seen so far from both open and closed projects. (wxWidgets still takes the cake, asking me if the bug still exists after ~8 years since initial report)
- nicholassmith 15y agoTrue, it's definitely a case where eventually the number of bugs becomes incredibly difficult to manage but it's still essentially training people to not report bugs if they can't see even the smallest amount of traction on it.