Contribute/Bugsquad/BugDays/KMailDay3

< Contribute‎ | Bugsquad‎ | BugDays
Revision as of 09:57, 15 March 2009 by Lemma (Talk | contribs)

Jump to: navigation, search

Contents

Introduction

This is the page for KMailDay3 which takes place on Sunday, March 15th 2009, but feel free to start early. The aim of this bug day is to organize as many of the KMail bugs as possible, identifying duplicate bug reports and already fixed bugs. Our targets for triage are bugs listed in bugs.kde.org under the product kmail.

Requirements

You don't need any programming experience to help out with Triaging, but you will need a recent version of KMail, either svn trunk or a recent release (eg. KDE 4.2.1). 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.

General information

  • This page has useful information on how to not mis-mark bugs. In particular, "duplicates are hard". Generally we don't want to claim things are duplicates when they aren't. Make sure you get approval from a developer before you mark something a duplicate. We don't want to create more work for the 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!)

Preparations

First of all, put your name and the version of KMail you are testing with into the Sign-in section. Then read the descriptions of the various sections to file bugs in carefully.

Junior Jobs

KMail is in search for bugs which are easy enough to fix for someone just starting out developing for KDE or KMail. 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 KMail developers if they really fit the scheme. In case a developer is around, you might as well ask him right away.

Workflow

  1. Select one of the batches of bugs you'd like to do and pick it by putting your name into the appropriate column.
  2. Execute the query to get the list of bugs and go through the bugs one by one.
    1. Read the bug description and the comments carefully and try to reproduce the bug.
    2. Post a comment on bugzilla explaining what you found out. Be sure to also put the version of KMail you are testing with in the comment.
    3. Put the bug into the appropriate section and describe your findings here as well (eg. "Can't reproduce any longer" or "This bug is still reproducible for me"). If there's something special about a bug, you can prepend a little label like eg. crash. Please mark every bug with your IRC nickname. You can easily do that by appending ~~~.
    4. Check if the bug's Version field is set properly. The version field for KMail bugs should always contain the last KMail version the bug is/was reproducible with. If the bug is no longer reproducible and it's unclear which version the bug last appeared in, please set it to the version you think it last happened.
    5. Check if the bug's component is set correctly. It will be of great help when checking for duplicates (eg. comparing similar bugreports in the "Disconnected IMAP" component). If you lack permissions to change the component or are unsure about it, please put the bugs in the "needs component change" section along with a comment.
    6. Check if the bug might qualify as a "Junior Job". If so, please put it in the "Junior Job Proposal" section.
    7. Mark the bug as triaged by adding the triaged keyword on the bug. Again if you lack the permissions to do so, additionally put it in the "Needs triaged keyword" section.
  3. If you're done with your batch, pick another one and start from the top :-)

Testcases

Some bugs might have documents that expose the bugs attached, for some bugs you might be able to create data that shows the buggy behaviour. In both cases we have to add the testcase keyword. If you lack permissions to do so, additionally add the bug to the "Needs testcase keyword" section.

Unclear

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!

Is it a big bug?

Prioritizing is good. We're especially interested in problems that result in dataloss. Let's keep track of them.

Double Check!

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.

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 use the tag <s>...</s> to mark a bug as done like this.

Hints

  • You can edit single sections of this page if you you check Enable section editing via edit links in your TechBase Preferences.
  • Sometimes you might encounter edit conflicts if several people are working on the wiki page at once. We can mostly avoid those by keeping notes of the bugs we encounter in a text editor and file several of them later at once (don't forget to save).
Ktip.png
 
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).


Sign-in

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 Nickname KMail version used for testing
Lemma svn trunk r939483

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 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.

noframe
 
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.


KMail Bug Firewall catch-up

We've been checking incoming bugs for KMail for a while now. Newly filed bugs are assigned to bugsquad-triage@kde.org, checked by us and reassigned/forwarded to the developers if there was enough information and the bug was not a duplicate. This section lists the bugs which are still assigned to bugsquad-triage and thus are either rather new or need some more work before they can be passed on. We should start with those.

Ktip.png
 
Tip
All of the Bug Firewall bugs' assignees have been set to the default assignee for KMail once they're handled by us. If you lack the permissions to do so, please put them in the "Needs assignee changed" section.


Information mostly for people organizing:

Batch No of bugs IRC Nickname Status Query
1 10 Query
2 10 Query
3 10 Query
4 10 Query
5 10 Query
6 10 Query
7 10 Query
8 10 Query
9 10 Query
10 10 Query
11 10 Query
12 10 Query
13 10 Query
14 10 Query
15 10 Query
16 10 Query
17 10 Query
18 10 Query
19 10 Query
20 5 Query

(Total bugs: 193)

Other batches

Information mostly for people organizing:

  • The template query for other batches is this one.
  • The query contains bugs filed in 2008.
Batch No of bugs IRC Nickname Status Query
1 10 Query
2 10 Query
3 10 Query
4 10 Query
5 10 Query
6 10 Query
7 10 Query
8 10 Query
9 10 Query
10 10 Query
11 10 Query
12 10 Query
13 10 Query
14 10 Query
15 10 Query
16 10 Query
17 10 Query
18 10 Query
19 10 Query
20 10 Query

(Total bugs: 200)

Bugs that need changes that require permissions

If you put a bug into this section, please be sure you additionally put it into the appropriate Completed Bugs section.

Bugs to be marked as TRIAGED

Bugs that need the triaged keyword adding to them should be listed here.

Bugs to be marked as TESTCASE

Bugs needing the testcase keyword added to them should be listed here.

Bugs needing version field changed

Bugs should be listed here if their version field needs to be changed according to what written above.

Bugs needing component field changed

If a bug can be categorized better by changing its component field but you lack the permission to do it, please put the bug here.

  • bug #186674 Probably isn't kmail fault. I've tested with kmail/kontact from kde 4.2.1 but in a kde 3 environment and I can't reproduce the bug. Santa 21:14, 15 March 2009 (UTC)

Special interest bugs

High profile

Some bugs seem to be more important than the others. If you feel a bug is really really (really) important and you can still reproduce it, please put it here.

Junior Job Proposals

If you think a bug looks easy enough to fix for a developer just starting to develop KMail (or even KDE), please put it here for review by a developer. Of course you can get a developer's opinion right away if you catch one on IRC.

A list of existing KMail Junior Jobs can also be found here.

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.

Bugs to be marked as RESOLVED

Bugs that are no longer reproducible and have been fixed already go into this section. After they are double-checked they can be closed.

Bugs with test-cases

If the bug is still reproducible and has a test-case attached, put it here.

Bugs with step-by-step instructions

If the bug has proper step-by-step instructions to reproduce the bug it should go here. Actually most reproducible bugs should end up in this section.

Bugs to be marked as INVALID

Bugs which are no longer valid go here. Please provide the reason why you think this bug is invalid. Some examples of when a bug should be closed as INVALID:

  • The reported behaviour is not a bug.
  • The bug is completely unrelated to KMail.

This list is not exhaustive. If you feel a bug is invalid for any other reason, be fure to list it here, mentioning why you think it is invalid. Before closing a bug as INVALID, be sure to get a developer's opinion.

Bugs to be marked as DUPLICATE

Duplicates (or possible duplicates) found should be placed here along with a link to the bug you think it is a duplicate of.

Bugs that should be WISHES

Sometimes there are bugs that are actually wishlist items. If you think a bug is not really a bug please put it here.

  • bug #186515 This bug is still reproducible for me with kmail 1.11.1 Santa 17:26, 15 March 2009 (UTC)

Bugs needing users with particular setups

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.

Non english locales

Bugs requiring non-English locales should be listed here, along with the locale they require.

Bugs needing attention from KMail developers

Add bugs here if you need to find out whether the observed behaviour is inteded, or if there's some other reason that it would be useful for a KMail developer to take a look at. Make sure you indicate why the bug needs attention. A second common reason to put a bug here is if it has already been heavily commented on by the application's developer. In the latter case please only add bugs you can reproduce.

noframe
 
Warning
Always defer policy decisions to developers.


Bugs awaiting feedback

Some bugs are hard to reproduce because the reporter left out some explanation you'd need. In that case we have no other means but to request some more information. Bugs for which feedback from the reporter has been requested should be put here. They should be revisited in 30 days to see if there's any response. If there's feedback

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.

  • bug #155119 Unable to reproduce, but asking the user if he still suffers it, as the bug is about losing information. Jtamate
  • bug #177405 Unclear how to set up kmail to produce described behaviour, asked reporter for more detailed instructions. dtritscher 16:38, 15 March 2009 (UTC)
  • bug #186695 Unuseful backtrace, reporter has stripped binaries for kdepim. Santa 20:13, 15 March 2009 (UTC)
  • bug #186551 I've requested an example to reporter. Santa 22:29, 15 March 2009 (UTC)

Bugs that you can't do

If you have bugs in your batch 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.

  • bug #186502 It seems unreproducible, probably a developer needs the ~/.kde4/share/apps/kmail/imap file from the reporter. Santa
  • bug #186536 I don't have 50k+ messages, so I try to reproduce the bug copying a dummy message pressing Crtl+Alt+C and keeping pressed Crtl+Alt+V, but I get a crash. Santa 22:39, 15 March 2009 (UTC)

Bugs not related to KMail

Put a bug in this section if it is not related to KMail and needs reassignment.


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