Topic locked

BugWeek Session 0 - Plasma Desktop

User avatar Dario_Andres
Mentor
Posts
67
Karma
3
OS

BugWeek Session 0 - Plasma Desktop

Sat Dec 26, 2009 1:55 am
Welcome to the first BugWeek session. ;)

Introduction

This week we will be organizing and checking the Image Plasma Desktop bug reports.


Preparations (from December 28 to January 01)

  1. Read the Getting Started article, prepare your accounts and setup your testing environment.
  2. Register yourself for this Bugweek by posting into this forum thread and telling us which KDE Platform version are you going to use.
    (copy the output of the "kde4-config --version" command; or the SVN revision if you are building from trunk sources)
    Do not forget to write down your bugzilla account name

If you have any question about the environment setup, just ask on the questions thread

Start Working! (from January 02 to January 03)

Workflow

  1. Choose a batch of bug reports from the list below (and check that no one else picked that one already) Create a new post in this thread telling us which one you have chosen.
    You will use this post to add the preliminary results of your triaging work on this batch of bug reports.
  2. Pick a bug report from your batch and check it using the following criteria:

    You should categorise your bug reports under a set of "headings". These are:

    A. Bug is no longer present
    B. Need more information from the reporter to test bug
    C. Bug is a duplicate of another bug report
    D. Bug is still present
    E. Any other bug reports or special cases.

    The first thing to do when triaging a bug is to check it still exists. You should follow the instructions in the report and note if you can reproduce the bug or not. If you are not able to follow the instructions due to them lacking information, then you should record the bug under heading B. If you can’t reproduce the bug, put it under heading A.

    If you can reproduce the bug, the next thing to do is to search for duplicates. Take a few keywords from the bug description and search for them. Look at any other bug reports that are found, and see if they sound like the same issue. If they do, there is a good chance (but no guarantee) they are duplicates, so list the bug number and the bug you think it is duplicate of under heading C.

    If there is anything different about the bug that makes you think should be taken into account (like, for example, the problem explained is not actually a bug, or the bug is in a different application to the one it is listed under) then list it under heading E. Otherwise, go for heading D.

    You can also write down if the title needs to be improved or updated in order to better describe the bug.

  3. If you could handle the bug report then add a comment in the report itself including the KDE Desktop version you used to test the bug and your conclusion about it.
    Examples:
    If the bug seems fixed:
    I cannot reproduce this bug using KDE SC 4.3.4 and Qt 4.5.3

    If the bug is still valid and you can add more information:
    I could reproduce the bug using KDE SC 4.4.0 and Qt 4.6.0. You need to click on X before pressing Y.

  4. Append the bug report's number and your conclusion (or tell us if you could not handle the report) in the batch's post (created on step 1).
    Example of a batch's post:
    Batch 1:
    Bug 100000: A. It works for me here...
    Bug 120000: C. It seems to be a duplicate of bug 120001
    Bug 140000: B. The reporter forgot to mention an important detail
    Bug 150000: E. I don't have two screens to test this bug.
    Bug 120030: D. The bug it is still reproducible. The report needs a better title.

  5. Check the next bug report in your batch (step 2)
  6. When you finish your current batch, you can pick another one

Not sure what to do with a bug report ?

If you have any doubt, just ask on the questions thread or in the #kde-bugs channel on IRC (FreeNode)

Bug Report Batches

Registered Users Table
User | KDE SC | Qt
jtamate | 4.4 SVN 1066188 | 4.6-stable-patched
Rémy Greinhofer | 4.3.4 | 4.5.3
Ingo Malchow | 4.4 Beta2 | 4.6.0
tampakrap | 4.4 SVN | 4.6 kde-qt master
Henry Rust | 4.3.4 | 4.5.3
Ryan J Redding | 4.3.4 | 4.5.3
talavis | 4.4 SVN 1068561 | 4.6 kde-qt
Lasse Liehu | 4.4 Beta2 | 4.6.0
ComputerDruid | 4.4 SVN 1067986 | 4.6.0
Kolia | 4.4 SVN 1068732 | 4.6.0
meloon | 4.3.4 | 4.5.3
User avatar jtamate
Registered Member
Posts
4
Karma
0
OS
bugzilla account: jtamate (Jaime Torres)
Qt: On branch 4.6-stable-patched
KDE Development Platform: 4.3.85 (KDE 4.3.85 (KDE 4.4 Beta2)) (revision: 1066188)
kde4-config: 1.0

Some thigs to make it better:
The batchs should open in a new tab/window by default.

batch 1

Last edited by jtamate on Sat Jan 02, 2010 10:36 am, edited 1 time in total.
User avatar rgreinho
Registered Member
Posts
5
Karma
0
OS
Bugzilla account: Rémy Greinhofer
Qt : 4.5.3
KDE : 4.3.4 (KDE 4.3.4)
kde4-config : 1.0
User avatar neverendingo
Administrator
Posts
2076
Karma
16
OS
Bugzilla account: Ingo Malchow
Qt: 4.6.0
KDE Development Platform: 4.3.85 (KDE 4.3.85 (KDE 4.4 Beta2))


New to KDE Software? - get help from Userbase or ask questions on the Forums
Communicate.
Image
User avatar tampakrap
Registered Member
Posts
5
Karma
0
OS
Bugzilla account: tampakrap
Qt: 4.6 (kde-qt master branch)
KDE: 4.3.85 trunk (daily build)


henryrust
Registered Member
Posts
6
Karma
0
OS
Bugzilla account: Henry Rust
Qt: 4.5.3
KDE: 4.3.4 (KDE 4.3.4)
kde4-config: 1.0

Last edited by Dario_Andres on Tue Dec 29, 2009 3:50 pm, edited 1 time in total.
Reason: Hiding the email address
RJames
Registered Member
Posts
2
Karma
0
OS
Bugzilla: Ryan J Redding

kde4-config --version
Qt: 4.5.3
KDE: 4.3.4 (KDE 4.3.4)
kde4-config: 1.0
talavis
Registered Member
Posts
1
Karma
0
OS
Bugzilla account: talavis
Qt: 4.6-ish (kde-qt)
KDE SC: 4.4-ish (rev 1068561)

No idea whether I will have time, but I'm ready just in case.
lliehu
Alumni
Posts
9
Karma
0
OS
Bugzilla account: Lasse Liehu
Qt: 4.6.0
KDE Development Platform: 4.3.85 (KDE 4.3.85 (KDE 4.4 Beta2)) "release 203"

I'll be doing this in an OpenSUSE VM.
User avatar ComputerDruid
Registered Member
Posts
4
Karma
0
OS
Bugzilla: ComputerDruid
Qt: 4.6.0
KDE Development Platform: 4.3.85 (KDE 4.3.85 (KDE 4.4 Beta2 (SVN r1067986)))
kde4-config: 1.0

I'm not positive of this, but I want to try to help.
Kolia
Registered Member
Posts
22
Karma
0
OS
Bugzilla account: Kolia
Qt: 4.6.0
KDE Development Platform: 4.3.86 (KDE 4.3.86 (KDE 4.4 >= 20091231)) (SVN rev: 1068732)
kde4-config: 1.0

See you soon :)
meloon
Registered Member
Posts
3
Karma
0
OS
Bugzilla : meloon

Qt: 4.5.3
KDE: 4.3.4 (KDE 4.3.4) "release 2"
User avatar Dario_Andres
Mentor
Posts
67
Karma
3
OS

Start!

Sat Jan 02, 2010 3:46 am
I have already added the bug reports batches.
You can pick whatever you want, but check that no one else picked the same batch before 8) (you should get a message from the forum if someone else added a new post to the topic while you were writing a new post)

You can start working on the reports whenever you like.
I'm going to be up again on Saturday 02nd - 13:00 GMT

Happy triaging! ;-D
henryrust
Registered Member
Posts
6
Karma
0
OS
I have chosen Bug Batch 1.
User avatar rgreinho
Registered Member
Posts
5
Karma
0
OS
I take the second one.

 
Topic locked

Bookmarks



Who is online

Registered users: alake, Artmessiah, Baidu [Spider], Bing [Bot], bjoernbalazs, blue_bullet, Charblaze, dniitall, edmael, Exabot [Bot], franku, GentooSimon, Google [Bot], google01103, jensreuterberg, jgrulich, jitseniesen, ken300, koriun, Kver, La Ninje, lazyit, lucyandfatty, Majestic-12 [Bot], Mamarok, MiceAreVeryNice, odysseus-art, okias, robinh, Steve Guilford, urgo, wes33, Yahoo [Bot]