While our KOffice krush day is already more than a month ago (25th of January) it still deserves someone blogging about it. It was a great pleasure to see 9 people working hard on finding issues in KOffice and - no surprise - issues we did find. In total we identified about 100 separate crashes, general bugs as well as some ways to improve usability. I was also happy to see some of the most important ones be fixed while we were still finding new ones. Time to send a big thankyou to jtamate, grundleborg, blauzahl, m4v, dtritsched, JLP, Enkithan and brot as well as all of the hard-working KOffice developers who spent their time coaching and answering questions.
On to the actual topic. I'm happy to announce (another) beginning of the bug triage season. Since the KDE 4.2 came out, the general bug count on
bugs.kde.org has pretty much been skyrocketing. Of course we're regulary introducing new bugs with every release but I guess that 4.2 also marked the point where a lot more regular users were joining the KDE4-using crowd. This does not only lead to more bugs being found but - sadly - also to more people reporting the same bugs or reporting simple support issues on our bugtracker.
That's where our next Bugday will come into play. We'll be revisiting KMail once more hoping to find duplicate bug reports, already resolved issues and generally clean up. If you're willing to help, you're very welcome to join us on
#kde-bugs this Sunday (the 15th) starting around
10:00 CET. I think I mentioned it before but I'll do it again just for the record: No programming skills needed. All you'll have to bring are a recent version of KDE (preferably
trunk), some time to spare and the will to make a little difference. Of course we'll have senior Bugsquadders around to help newcomers get started.
currently, here's the url: http://techbase.kde.org/Contribute/Bugsquad/BugDays/KMailDay3.
If you're still pondering wether to join, just do it. Any helping hand - be it developer or user - is welcome and helping hands we need a lot 
