Difference between revisions of "Contribute/Bugsquad/OrganizingABugDay/Templates/ProductDayX"

Jump to: navigation, search
(create Template page)
m (Completed Bugs)
Line 77: Line 77:
{{:Contribute/Bugsquad/BugDays/ProductDayX/Bugs to be marked as NEW}}
{{:Contribute/Bugsquad/BugDays/ProductDayX/Bugs to be marked as NEW}}
{{:Contribute/Bugsquad/BugDays/ProductDayX/Bugs needing attention from <product> developers}}
{{:Contribute/Bugsquad/BugDays/ProductDayX/Bugs needing attention from "product" developers}}
{{:Contribute/Bugsquad/BugDays/ProductDayX/Bugs needing the reporter's feedback}}
{{:Contribute/Bugsquad/BugDays/ProductDayX/Bugs needing the reporter's feedback}}

Revision as of 10:48, 14 August 2012



This bug day will take place on <date> but feel free to start early. The aim of this bug day is to get as many <product>-related bugs done as possible. Our target for triage is bugs listed in bugs.kde.org under the product <product>.

Goals of this Bug Day

  • Main goals
    • Check if bugs reported for older versions of <product-currentversion> are still reproducible.
    • Check for duplicates of newer bugs
    • Check if bugs reported for <product> which are previously UNCONFIRMED are reproducible.
  • If a bug's description is somewhat unclear, try to provide a better step-by-step procedure on how to reproduce it. This will make it easier for developers to find and fix the bug. If necessary, ask the reporter and change the status to NEEDSINFO -> WAITINGFORINFO

(* Some bugs will only be reprocudible on certain graphics hardware, so please always provide the graphics card and driver you are using.)

  • Some bugs may not be reproducible on every installation of KDE. Thus we use a 4-eye principle, having at least 2 triagers look at the bugs before we make any changes on the bugs themselves.
  • Some more information on how to mark bugs can be found on This page.
  • 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 SC <currentrelease> (preferably Git trunk) for testing these bugs.
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).

Is it a big bug?

Prioritizing is good. If a major application doesn't work, this should be taken care of.

Version field

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.

Keep this page updated!

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, Git branch/trunk with revision and graphics hardware/driver below:

IRC Nickname KDE version used for testing Hardware
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).

Division of Labour

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.

Batch No of bugs IRC Nickname Status Query
1 20 [[User:<wikiusername>]] done [ Query]

(total bugs: <number>)

Completed Bugs

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.

Contribute/Bugsquad/BugDays/ProductDayX/Bugs needing Version Field changed

Contribute/Bugsquad/BugDays/ProductDayX/Bugs with step-by-step Instructions

Contribute/Bugsquad/BugDays/ProductDayX/Bugs to be marked as RESOLVED

Contribute/Bugsquad/BugDays/ProductDayX/Bugs to be marked as DUPLICATE

Contribute/Bugsquad/BugDays/ProductDayX/Bugs to be marked as INVALID

Contribute/Bugsquad/BugDays/ProductDayX/Bugs to be marked as NEW

Contribute/Bugsquad/BugDays/ProductDayX/Bugs needing attention from "product" developers

Contribute/Bugsquad/BugDays/ProductDayX/Bugs needing the reporter's feedback

Contribute/Bugsquad/BugDays/ProductDayX/Bugs needing users with particular setups

Contribute/Bugsquad/BugDays/ProductDayX/Bug reports against performance issues

Contribute/Bugsquad/BugDays/ProductDayX/Bugs not related to today

Contribute/Bugsquad/BugDays/ProductDayX/Bugs that you cant do


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal