This bug day will take place on Sunday, August 1st 2010, but feel free to start early. The aim of this bug day is to get as many Dolphin-related bugs done as possible. Our target for triage is bugs listed in bugs.kde.org under the product Dolphin.
|Always make a note on the bug of what the status is in the version you are testing with (be explicit as to what version of 4 you are using, mentioning whether it is a source build and which distro the packages come from).|
Prioritizing is good. If a major application doesn't work, this should be taken care of.
Keep an eye on what the "Version:" fields say in Bugzilla. If it says "unspecified", change the version field to match what the report says, i.e. to match version the bug was first reported in. Do not change the version number if it is currently set as a number! (ex. from 4.0 to 4.2)
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 do this with the tag <s>...</s>
Please select a period of bugs from the Division of Labour section below and mark your name next to it and mark it with your irc nickname to show that you are working on it. When you have completed all the bugs in that section, please mark it as complete.
For each bug, try and reproduce it as described in the report. Then list it in the appropriate section below. If you wish to close or mark as duplicate a bug, please list it here even if you have the bugzilla permissions to do so, in order to get a second opinion from another triager. This will help to reduce the number of incorrect actions taken on bugs.
Tell developers what you are testing with. (If you expect to upgrade between now and Bug Day, 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:
|IRC Nickname||KDE version used for testing|
|Lemma||KDE SC 4 svn trunk|
|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).|
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 batches bugs you are working on to avoid duplication of effort.
The bugzilla query to use for this triage day can be found here.
|Batch||No of bugs||IRC Nickname||Status||Query|
(Total bugs 147)
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.
Please note that this is an experimental layout designed to reduce the number of edit conflicts on this page. Each section is its own subpage. The best way to work with this is to enable section editing by going to "My preferences" > "editing" > "Enable section editing via  links". When you click edit you will automatically edit the subpage.
If you don't have bugzilla permissions yet, you can't change version fields. Put what needs changing here and someone else will go through and do it for you. Don't worry, you'll have permissions soon enough...
If it is a deterministic bug, put it here. Make sure it has instructions. You should be able to verify it. (Write that you did on bugzilla and include your version information.)
Put suspected duplicates here.
A bug is INVALID if it describes desired behavior, or something that isn't a bug.
If a bug needs for example special hardware, network servers or locales installed, put it here.
If it is a valid bug, but not a dolphin bug, it might have been assigned the wrong product on Bugzilla. Put it here so it can be reassigned to the proper component.
If there are bugs you can't test for whatever reason (apart from the ones needing a particular setup which have their own section), fill those in here.