https://bugs.kde.org/show_bug.cgi?id=345100
--- Comment #40 from ianse...@btinternet.com --- (In reply to S. Christian Collins from comment #39) > (In reply to ianseeks from comment #38) > > Does that mean users like me should no longer post bugs in here and just > > post bugs to the distro mailing lists or perhaps only to the distro's bug > > database? To a user like me, unless the status changes in some way, we have > > no idea if its even been seen let alone be investigated. Maybe create a > > status of "Noted". We users that post bugs do feel like a small part of the > > development process. > > As a fellow bug-poster, I understand that it can be frustrating when it > seems that a bug affecting you isn't getting the attention that you would > like, but we need to respect the developers' process and realize that these > guys aren't just sitting on their thumbs. There is an awful lot of bug data > for them to sift through, and I would imagine it is easy for bugs like this > one to slip under the radar, especially considering it is not major. > > Nonetheless, this bug has been fixed, and all because somebody took the time > to report it here on the KDE bugzilla. I don't see how reporting it to the > distros would have helped anything. All i was asking (generally and not this bug) is that if its been opened and looked at by a dev then make a note on the bug report, how else do you run accurate stats on a system if the data is incorrect. If you read some of the emails in the mailing lists, you'll see some people moaning that a bug has been sitting there for X months or years and assume its been ignored - i was hoping that suggesting changing a status or making a note to say its been seen would halt that moaning email. I was no way getting at the devs, just trying to help remove some of the nonsense in the mailing lists that imply the devs aren't doing anything. -- You are receiving this mail because: You are watching all bug changes.
