|Line 51:||Line 51:|
|[[User:Blauzahl|Blauzahl]] || ||
|[[User:Blauzahl|Blauzahl]] || ||
|[[JontheEchidna]] || Kubuntu
|[[JontheEchidna]] || Kubuntu 10with KDE 4.3.3, Amarok 2.2.0 ||
This bug day will take place on Sunday, November 8th 2009, but feel free to start early. The aim of this bug day is to clear as many Phonon-related bugs as possible. Our target for triage is bugs listed in bugs.kde.org under the product Phonon.
The goal of this bug-day is to check for: simple step-by-step instructions, reproducibility, and most of all, come up with test-cases for reproducing the bugs. This will enable the Phonon developers to deal with bugs more easily, and so have more time left to actually fix them. When you have added step-by-step instructions for the reproduction of a bug, please list it in the appropriate section below, so that a second triager can see if they can get your instructions/test-case to work correctly. This page has useful information on how to not mis-mark bugs. In particular, "duplicates are hard". and Phonon currently has a lot of duplicate reports. The other tricky thing is that you will need to test with various applications like Amarok or Dragonplayer, since many KDE applications use Phonon for sound. Please make sure to double check them with someone else, preferably one of the developers before marking/closing.We especially don't want to create more work for developers!
Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. (You can even join now!)
You should be working with KDE 4 (either 4.3.2 or newer is best or SVN trunk) for testing these bugs. To test bugs noticed with Amarok, we strongly suggest aou have either Amarok 2.2.0 or 2.2-git
|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).|
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. If a major website doesn't work, that is important. Let's keep track of them.
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)
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.
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>
Add your comments even on bugzilla for a more complete feedback by users and developers.
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 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:
|IRC Nickname||KDE version used for testing|
|Mamarok||Kubuntu 9.10 with KDE 4.3.3, Amarok 2.2-git|
|JontheEchidna||Kubuntu 10.04 with KDE 4.3.3, Amarok 2.2.0|
|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 month that is not already taken and then query bugs.kde.org for all bugs in that month. Please mark you irc nickname in the table below to show which month's bugs you are working on to avoid duplication of effort.
The bugzilla query to use for this triage day can be found here.
|Month/Time period||No of bugs||IRC Nickname||Status||Query|
(Total bugs 180)
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.
Bugs should be listed here if their version field is invalid (i.e. it is listed as "unspecified") and they are still present in KDE 4, so that the version field can be corrected. In general, we are not changing the version numbers.
If a bug fits another category, put it there and add the notation that the version field needs changing.
If you have provided step by step instructions on how to reproduce a bug, please list the bug here.
A bug is INVALID if it describes desired behavior, or something that isn't a bug.
Put suspected duplicates here.
ex. hardware, locales, etc.
If anything is in doubt, put it here, and give a description of why you think a developer should look at it.
If you are waiting for feedback from a reporter, put your bug here.
If it is a valid bug, but not a phonon bug, put it here and reassign it to the proper component.
If there are bugs you can't test with your settings, fill those in here. Since this is most likely due to one of the backends not working for you, we group those by backends here: