| Tip |
|---|
| This is a mostly self-contained page for an introduction to triage. At this point, it is ongoing. If you are new, carefully document your work, and do a month or two. Then find grundleborg or blauzahl on irc. |
This bug day will take place on Sunday, October 12th 2008, but feel free to start early. The aim of this bug day is to clear as many Konqueror-general bugs as possible. Our target for triage is bugs listed in bugs.kde.org under the product Konqueror, component General.
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 rendering bugs. This will enable the Konqueror developers to deal with bugs more easily, and so have more time left to actually fix them. When you have added either a test-case or 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 provides an excellent explanation of how to create a test-case. This page also has useful information on how to not mis-mark bugs. In particular, "duplicates are hard". Konqueror doesn't have as many duplicates as some applications, and we don't want to claim things are duplicates when they aren't. So do not look too hard for them, and 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 either be working with Konqueror from KDE 4 (either 4.0.3 or newer is best or SVN trunk) for testing these bugs.
| Warning |
|---|
| 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 you come across a bug with a testcase in the text, put it under the testcase section. If it isn't marked "testcase" in the title, make a note of that. Check that the testcase works! (And doesn't work!)
Most importantly, we need to create testcases. These are time-consuming, but extremely useful and really help out developers. These are especially important if it is a site that is either a non-Western language or a site you need some sort of account for.
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 3.5.2 to 4.0.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.
All bugs that you investigate during the bug day, whether they appear on this page or not, should have the keyword triaged added to them. If you don't have bugzilla permissions, list all bugs needing that keyword added in the Bugs to be marked as triaged section below, even if you have already added them to another section of this page.
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 | |
|---|---|---|
| lemma | svn trunk r870274 | |
| brot | last update failed, will try to get latest svn trunk on sundays ;) | |
| jtamate | svn trunk |
|
| katastrophe | svn trunk r869427 | |
| gkiagia | svn trunk r870041 |
| Tip |
|---|
| 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. Be sure to correct the dates to the month which you will triage before running the query.
| Tip |
|---|
| The most recent months (2008+) should be done by people using recent SVN trunk. In general, the most recent version you can use of 4, the better. |
| Warning |
|---|
| 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. |
| Month/time period | No of bugs | IRC Nickname | Status | Query |
|---|---|---|---|---|
| 2007-05-1 | 12 | lemma | done | Query |
| 2007-05-2 | 17 | Query | ||
| 2007-05-3 | 19 | katastrophe | done | Query |
| 2007-06-1 | 24 | Query | ||
| 2007-06-2 | 25 | Query | ||
| 2007-08-1 | 20 | Query | ||
| 2007-08-2 | 21 | Query | ||
| 2007-09-1 | 20 | Query | ||
| 2007-09-2 | 18 | Query | ||
| 2007-10-1 | 18 | jtamate | done | Query |
| 2007-10-2 | 17 | Query | ||
| 2007-10-3 | 18 | Query | ||
| 2007-11-1 | 18 | Query | ||
| 2007-11-2 | 18 | Query | ||
| 2007-11-3 | 19 | Query | ||
| 2007-11-4 | 20 | Query | ||
| 2007-12-1 | 21 | Query | ||
| 2007-12-2 | 20 | Query | ||
| 2007-12-3 | 21 | Query | ||
| 2007-12-4 | 20 | Query | ||
| 2008-01-3 | 26 | jtamate | done | Query |
| 2008-01-4 | 25 | Jtamate | working | Query |
| 2008-02-2 | 25 | Query | ||
| 2008-02-3 | 22 | Query | ||
| 2008-05-2 | 13 | jtamate | working | Query |
| 2008-05-03 | 18 | Query | ||
| 2008-06-01 | 18 | Query | ||
| 2008-06-02 | 19 | Query | ||
| 2008-06-03 | 17 | Query | ||
| 2008-06-04 | 15 | Query | ||
| 2008-07-01 | 20 | Query | ||
| 2008-07-02 | 19 | Query | ||
| 2008-07-03 | 17 | Query | ||
| 2008-07-04 | 11 | Query | ||
| 2008-07-05 | 12 | Query | ||
| 2008-08-01 | 18 | Query | ||
| 2008-08-02 | 18 | Query | ||
| 2008-08-03 | 11 | Query | ||
| 2008-08-04 | 18 | Query | ||
| 2008-08-05 | 23 | Query | ||
| 2008-09-01 | 10 | Query | ||
| 2008-09-02 | 17 | Query | ||
| 2008-09-03 | 19 | Query | ||
| 2008-09-04 | 17 | Query | ||
| 2008-09-05 | 14 | Query | ||
| 2008-10-01 | 15 | Query | ||
| 2008-10-02 | 20+ | don't pick this. it's growing :) | Query |
(Total bugs: max. 868, probably less)
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 [edit] links". When you click edit you will automatically edit the subpage.
Bugs that need the triaged keyword adding to them should be listed here even if they are already in another section of this page. This is a convenience for people who do not yet have bugs.kde.org permissions.
If a bug is reported against a version of KDE before 4.0, but the bug can no longer be reproduced in KDE 4.x, then it should be listed here. Please do not close the bug. The Konqueror developers would like to check each one before they are closed.
*bug #145023 - Mouse cursor over scaled input boxes doesn't detect new size. Works for me. Lemma Closed by Maksim.
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.
Add the bug here if it describes something which is not present in 4.x.
Bugs with a testcase (an example of how to reproduce the bug), but not [Testcase] in the title, should be entered below.
If you have provided step by step instructions on how to reproduce a bug, please list the bug here.
Bugs filed against KDE 4 (ie, only very recent ones) that can no longer be reproduced should be listed here. Bugs filed against earlier versions of KDE that can no longer be reproduced should be listed in the section above.
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.
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 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.
| Warning |
|---|
| Always defer policy decisions to developers. |
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.
Bugs that are not related to today's target application should be listed here so they can be reassigned to the correct bugzilla product.
If you have bugs in your month 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.
KDE TechBase 