Hi,
I placed a bug in kde.bugs.org (https://bugs.kde.org/show_bug.cgi?id=200430), but it got reject and they suggested I placed it here instead:


"I've been using KDE4 for quite a while and I am beginning to get disappointed
with the direction the project is taking.

There seems to be allot of work going in to creating new awesome features (The
desktop is really good and powerful ) but the amount of bugs being reported
is increasing day by day...

IMHO there seems to be to much focus on developing new features instead of
fixing already existing ones.
I also develop software, and I know it is not easy to do Bug fixes and it is
more exciting to develop new stuff.

But if KDE aims at being a truly usable/functional/trustworthy desktop then
everybody should concentrate on fixing most of the bugs before creating more
features.

I also understand that this is a project composed of many and different
applications and because of that things are much more complex.

Hope this gets some attention.
Thanks, and keep up the good work "

The problem isn't more bugs, but more users using development versions, leading to more bugs being reported ( in many cases duplicates ). This is a good thing because it means the code has had much more testing before a release is actually made, and it will end up with less bugs overall.

Also, bugs.kde.org is also used for Wishlists so the number of bugs filed per day could have a high percentage of Wishlist items, and not actually be pure bugs.

The above quote from you really seems to fit better into this forum, as it is not about a specific bug. But if you really have a true bug to report bugs.kde.org will fit. If you are unsure about it you can always discuss it here in the appropriate area before you submit it to bugs.kde.org.

Hi,
actually I think my bug is related to the release method. How do you guys decided when a release is "ready"?
It seems that although some really annoying bugs/regressions are being reported, they getting ignored in favor of new features.
The fish protocol is one of those examples. With over 100 comments, one the developers ignore it because he was unable to reproduce it.... I also reported some others bugs that were discarded with "works for me" messages from the devs....

A release is ready when there are no outstanding release blockers (discussed on the release-team malinglist). Also you are not counting the huge number of invalid and duplicate reports on bugs.kde.org.

s. With over 100 comments, one the developers ignore it because he was unable to reproduce it....

But if the developer can't reproduce, how can he/she fix it? That's why proper bug reporting, including detailed steps to reproduce issues, are important.

Well, is there anyway to know how many new bugs are reported+unsolved trough releases (discarding duplicates/invalid)?
Bugzilla isn't very user friendly concerning this kind of statistics.

"mattr" in #kde-www on Freenode, who manages KDE's bugzilla will likely be able to provide information on accessing these statistics.