(created DivisionOfLabour template)
m (Mamarok moved page DivisionOfLabour to Contribute/Bugsquad/BugDays/DivisionOfLabour: move to correct location)
This triage day will run from <enterdate>. Our target for triage is bugs listed in bugs.kde.org under the product Konqueror.
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.
Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated.
You should be working with <productversion> for testing these bugs.
For each bug, try and reproduce it as described in the report. Then list it in the appropriate section below, or if you have the required bugzilla permissions, take the appropriate action as described in the sections below.
Please choose a <period> that is not already taken and then query bugs.kde.org for all bugs in that <period>. Please mark you irc nickname in the table below to show which month's bugs you are working on to avoid duplication of effort.
Only bugs from older releases which have clear instructions on how to reproduce them should be marked as resolved (if you can no longer reproduce of course)
Bugs which are no longer valid go here. A link to the bug and why it qualifies as invalid should be provided.
Duplicates found should be placed here with a link to the bug which you think it is a duplicate of.
Bugs that have been confirmed should go here. A comment should also be left on the bug with a note of what version of <productversion> was used to confirm it.
Bugs that have had a test case (an example of how to reproduce the bug) added should be entered below.
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 <product> developer to take a look. Make sure you indicate why the bug needs attention from them.
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.