Good morning! 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 KonquerorDay7 which starts on Saturday, June 20, 2009, but feel free to start early and feel free to keep going! The aim of this bug day is to
a) Triage: organize as many of the Konqueror bugs as possible, identifying duplicate bug reports and already fixed bugs b) Testcases: Make testcases for the rendering bugs that have been filed. c) Prioritize bugs to fix: Go through a list of websites and check how well they work. Keep an eye out for MAJOR bugs.
Our bug targets are listed in bugs.kde.org under the product konqueror. (That link gives component breakdown.)
You don't need any programming experience to help out with Triaging, but you will need a recent version of KDE, either svn trunk (4.2.92 atm), a snapshot of it (Neon Nightly, etc.), or a recent release (eg. KDE 4.3beta2). 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. Else, #kde-devel can always help you.
First of all, put your name and the version of KDE/Konqueror (ie kdelibs and kdebase should be the same version) you are testing with into the Sign-in section. Then read the descriptions of the various sections to file bugs in carefully.
We are in search of bugs which are easy enough to fix for someone just starting out developing for KDE. Those kinds of bugs are called "Junior Jobs". If you think a bug sounds really easy to fix so it might qualify as a junior job, please put it in the "Junior Job Proposals" section. They will later be checked by the developers if they really fit the scheme. In case a developer is around, you might as well ask right away.
Some bugs might have a short html file that gives an example of the bug. Add the testcase keyword. If you lack permissions to do so, additionally add the bug to the "Needs testcase keyword" section.
If it is a rendering bug, and it doesn't have one, put it in the wiki section "needs testcase" for someone to write one.
For bugs involving webpages, if the site doesn't exist anymore, check the "Wayback Machine" on http://archive.org - if you see it there, use that to come up with a testcase.
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 dataloss and crashes. 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.
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):
|IRC Name||KDE/Konq version||Qt version|
|Blauzahl||svn 984123||4.5.0 qt-copy with patches|
|someone else||svn 123354/134325||qt-git|
|siyuan||svn 983852||qt-copy 979410|
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.|
The following bugs are related to displaying webpages using Konqueror.
|Month/time period||No of bugs||IRC Nickname||Status||Query|
The following bugs are related to anything non-html.
|Month/time period||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.
We use this keyword to keep track of how which bugs people have done. You should add it to all bug reports you comment on.
Below lists the various sections for completed bugs, sorted by resolution and other issues.
If a bug is not reproducable for you, then it should be listed here. Please do not close the bug. We'll double-check each others later on. It will probably get closed as WORKSFORME. (FIXED if you knew which commit fixed it, and that it was an actual intentional commit somewhere.)
If it isn't a consistently reproducible bug, it may be not there only with your setup, or you haven't hit the right conditions. Check to see if there are developer comments and if they think it should be left open. Add to your notes here if you aren't sure.
Note: not instructions, actual *testcases* Usually these will be a snippet of code that reproduces and isolates the bug.
This is actually major work. We should list things which could have testcases, so that we can have people who can write some, do so. Put down if you think it is an important bug too, since making a testcase can take a while: on a scale of 1-5, with 1 being most important, how important is the bug to be fixed by 4.3?
If it is still there, and makes sense, list it here. In bugzilla, make sure it is changed from UNCONFIRMED to NEW.
Bugs which are no longer valid go here. A link to the bug and why it qualifies as invalid should be provided.
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 sure to list it here, mentioning why you think it is invalid.
Duplicates found should be placed here with a link to the bug which you think it is a duplicate of.
Add bugs here if you need to find out whether the observed behavior is intended, or if there's some other reason that it would be useful for a Konqueror developer to take a look. Make sure you indicate why the bug needs attention from them.
NB. 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.
Bugs for which feedback has been requested, which should be revisited in 30 days to see if there's any response. Please list all bugs here for which feedback has been requested.
Some bugs aren't actually bugs, just functionality that isn't there. Those should get moved to "wishlist" priority.
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.
People almost by default file their bugs under Konqueror: Bugs that are not related to today's target application should be listed here so they can be reassigned to the correct bugzilla product.
For whatever reason... Put it here, and someone can comment on it.