Bye Bye Boogs!
9 06 2007
Well, the past 14 or so hours I went on a bug rampage. I was able to close over a 100 bugs, most of which were stale, fix released, or support type reports. I confirmed a ton, wishlisted a ton, created a ton of upstream bug reports, and knocked down the national deficit while I was at it 
This is a cool utility that Carthik has put together. Take a look at all of the trendlines, but one, and look at the drops reported. I got on a roll, became somewhat addicted, and went into the zone, and now the KDE-PIM package is happy I worked on it.
Tomorrow if I get some time, there are still quite a few kdebase and kdelibs reports I want to go over, as well as some of the other KDE apps. Well, that is all the bragging I have in me tonight, so off to bed I go…
Good night ladies and gents!
You rock!
Congratulations. This is really impressive!
That absolutely rocks!
I’m impressed
Great work!!
Thank you very much!
Awesome! I used to go on these hunting trips too - maybe I should, one of these days.
I’ve been thinking about using Amazon’s mechanical turk system to motivate tackling this. The two big factors in not doing so at the moment is the money, and the potential to motivate the filing of useless bugs. But the last part is probably going to exist in any paid QA.
As impressive as that graph looks, the numbers on the side tell a different story. You closed a hundred bugs, but that’s only one third of one percent of all open bugs. What’s scarier is that over the last 180 days, an average of 100 new bugs were created. Tomorrow we can expect that unless you’re involved that much again, all that progress will be rolled back
thanks everyone. The main reason to this post was to make people go WOW! and hopefully get motivated. After checking email this morning, well I can say it worked to an extent. I have seen people triaging that I have never seen before. You are right, if the effort isn’t continued, then it will be rolled back, if it hasn’t already.
You have to remember, there are quite a few bugs on LP that have already been fixed but have yet to be closed. But if 10% of our community would do 1/2 of what I did yesterday, we would be able to get a pretty good grasp on the bugs. Another thing too, a lot of our reported bugs are due to upstream bugs, so we need to take the bugs people have reported, verify them upstream and create/link to upstream reports. If we just harbor the reports in Malone and don’t inform the upstream developers, then the bugs will never get fixed.
Wow, awesome job! That’s the biggest dip I’ve ever seen!
And now I know why my inbox is flooded. I think I should get working on flooding it myself.
I’ve noticed an unmentioned trend - the people making bug reports are becoming more abusive. It would not surprise me if there was a high churn in triagers as the rise in complaints drains morale. Who wants to spend their spare time interacting with the Ubuntu community in bugs like https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/119659 ? Perhaps Ubuntu has had a honeymoon period and soon folks will be bemoaning it the same way they bemoan Fedora…
Wow, nice bug report. Unfortunately every community has poisonous people. From what I have read from the reporter, he has no idea what project management is about, let alone management. He probably isn’t a developer either, probably read someone had problems on slashdot and he followed along. I bet if the kernel changed /dev/hda to /dev/pda he wouldn’t have complained. He acts like it is always the distros fault, so if he knew anything about Linux he might not have been such an idiot.
https://launchpad.net/~beranger/
Take a look at his LP page, he even admits to being poisonous.
I participated in the last HUG DAY.. and closed a lot. What I’ve doing for some time is getting the oldest bugs from LP listing and check them.
Start here:
https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=datecreated&search=Search&field.status%3Alist=Unconfirmed&field.status%3Alist=Confirmed&field.status%3Alist=In+Progress&field.status%3Alist=Needs+Info&field.status%3Alist=Fix+Committed&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=&start=1