If this is the first time you're taking part in a bug triage, don't be scared by the amount of explanatory text on this page. We hope it's easily understandable - if it isn't bug us on IRC :-)
This is the page for PlasmaDay1 which takes place on Saturday/Sunday, April 25th/26th 2009, but feel free to start early. The aim of this bug day is to organize as many of the Plasma bugs as possible, identifying duplicate bug reports and already fixed bugs. Our targets for triage are bugs listed in bugs.kde.org under the product plasma.
You don't need any programming experience to help out with Triaging, but you will need a very recent version of KDE compiled from svn. Information on setting up KDE from trunk can be found here. If you're having trouble installing KDE, feel free to drop by on #kde-bugs early to get some help.
First of all, put your name and the version of KDE you are testing with into the Sign-in section. Then read the descriptions of the various sections to file bugs in carefully.
Some bugs might have documents that expose the bugs attached, for some bugs you might be able to create data that shows the buggy behaviour. In both cases we have to add the testcase keyword. If you lack permissions to do so, additionally add the bug to the "Needs testcase keyword" section.
If something has no clear instructions on how to reproduce it, or has little useful information, add a comment asking the reporter for more detail. Then list it in the bugs awaiting feedback section. Be polite, we want to be nice to our bug reporters!
Prioritizing is good. We're especially interested in problems that result in an unuseable desktop. Let's keep track of them.
Please list bugs here to get a second opinion before making the change in bugzilla. This also gives a record of what we've done for the developers to check.
|Many Plasma bugreports might be specific to a certain graphics card or the version of Qt/X.org you are using. This means that just because you can't reproduce a bug it might still be there.|
After adding triaged bugs on this page, you should keep an eye on their bugzilla status. Add yourself on the CC field in bugzilla to be informed about updates. When a bug is closed on bugzilla, it should be updated on this page.
You can use the tag <s>...</s> to mark a bug as done
|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup ~~~ to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).|
There are some bugs which are commonly reported several times. If you found such a bug (or think you did), you can put it here:
Tell developers what you are testing with. (If you expect to upgrade between now and BugDay, put what version you are using now next to the bugs/comments that you put on this page.)
Please give distro/version or SVN branch/trunk with revision below (or just beta2 if you're using that). Also put your graphics driver, the version of Qt and X you are using:
|IRC Nickname||KDE version used for testing||Graphics driver||Qt||X|
|Lemma||svn trunk r958924||NVIDIA 185.19||qt-copy||1.6.1|
|jtamate||opensuse r954171||free ati radeon||4.5.1||1.6|
|anselmolsm||trunk 958853||NVidia 180.51||4.5.0+942255||1.5.3-r5|
Please choose a batch that is not already taken and then query bugs.kde.org for all bugs in that batch. Please mark you irc nickname in the table below to show which month's bugs you are working on to avoid duplication of effort.
If you have to leave before you can finish your batch, please put the last bug you triaged as well as if you're going to finish triaging in the table so others will know where you left off.
|With these more recent bugs, if the report has been looked at by a developer (i.e. they cc'd themself or commented on it or posted a patch), and it seems like the issue is fixed, BUT the developer didn't close it, make sure the bug really can be closed. Often it can't.|
Information mostly for people organizing:
|Batch||No of bugs||IRC Nickname||Status||Query|
If you put a bug into this section, please be sure you additionally put it into the appropriate Completed Bugs section.
Bugs that need the triaged keyword adding to them should be listed here.
Bugs needing the testcase keyword added to them should be listed here.
Bugs should be listed here if their version field needs to be changed according to what written above.
If a bug can be categorized better by changing its component field but you lack the permission to do it, please put the bug here.
Some bugs seem to be more important than the others. If you feel a bug is really really (really) important and you can still reproduce it, please put it here.
Below lists the various sections for completed bugs. This aids everyone in double checking each other's work. In addition this allows those of us that don't have bugzilla permissions to list bugs so that the folks with the permissions can follow up.
Bugs that are no longer reproducible and have been fixed already go into this section. After they are double-checked they can be closed.
If the bug is still reproducible and has a test-case attached, put it here.
If the bug has proper step-by-step instructions to reproduce the bug it should go here. Actually most reproducible bugs should end up in this section.
Bugs which are no longer valid go here. Please provide the reason why you think this bug is invalid. Some examples of when a bug should be closed as INVALID:
This list is not exhaustive. If you feel a bug is invalid for any other reason, be fure to list it here, mentioning why you think it is invalid. Before closing a bug as INVALID, be sure to get a developer's opinion.
Duplicates (or possible duplicates) found should be placed here along with a link to the bug you think it is a duplicate of.
Sometimes there are bugs that are actually wishlist items. If you think a bug is not really a bug please put it here.
Bugs that require particular software or hardware that you don't have available should be listed here with a description of the non-standard requirement.
Bugs requiring non-English locales should be listed here, along with the locale they require.
Add bugs here if you need to find out whether the observed behaviour is inteded, or if there's some other reason that it would be useful for a Plasma developer to take a look at. Make sure you indicate why the bug needs attention. A second common reason to put a bug here is if it has already been heavily commented on by the application's developer. In the latter case please only add bugs you can reproduce.
Some bugs are hard to reproduce because the reporter left out some explanation you'd need. In that case we have no other means but to request some more information. Bugs for which feedback from the reporter has been requested should be put here. They should be revisited in 30 days to see if there's any response. If there's feedback
Feedback should only be requested for bugs if you have tried and failed to reproduce them or if the report contains insufficient information to try and reproduce the bug. Requesting feedback for a bug should be seen as a last resort only.
If you have bugs in your batch that you can't do, and no-one has been able to help you with on IRC, please list them here for someone else to have a look at.
Put a bug in this section if it is not related to Plasma and needs reassignment.