Last Saturday was the first KDE 4 Krush Day and if you did not take part, here is your chance to redeem yourself: tomorrow is Saturday again! And it'll happen on #kde4-krush on IRC.
This techbase webpage explains everything you need to know.
First of all, you need the latest KDE 4 possible, from svn trunk or from a Live CD. If you had KDE 4 already and are updating, it's better to backup your ~/.kde or ~/.kde4 and run KDE 4 with defaults config. Also if you have phonon/sound related problems please rm ~/.config/kde.org/libphonon.conf and retest.
So, what to do and how?
Pick your favourite program and start looking if it behaves as intended. If not, jump to the techbase page and look if the problem has already been mentioned. If so and if you cannot add anything useful, please don't clutter the page, add "Confirmed" and your nickname.
For crashes: always attach a backtrace otherwise it is useless to report a crash. Please use pastebin for the backtrace. Explain how to reproduce the crash in details. If possible find someone who can reproduce it. All about backtraces is explained here.
If you have svn trunk and reported a bug last Saturday, if the bug was fixed you can test if the fix works for you.
Remember that you can test all programs! And if you want to fixe some bugs, feel free to do it and please send your patch (neat HowTo here) to the kde-devel mailing list or post it on pastebin and link it to the bug on the techbase page with your nickname.
I enjoyed meeting new people last Saturday and working to debug some programs. Not sure I can participate very much tomorrow as I'll look after a 1-year old baby so my friends can prepare their boxes for their move without their daughter wanting attention!
No comments:
Post a Comment