Contribute/Bugsquad/BugDays/Beta46Week1

< Contribute‎ | Bugsquad‎ | BugDays
Revision as of 15:39, 2 December 2010 by OpenIDUser6 (Talk | contribs)

Jump to: navigation, search

The 4.6-beta1 BugWeek will be from 27.11 till 4.12 :)

noframe
 
Note
Additions to this wikipage welcome :)

Contents

Introduction

Goals of this Week

This bugweek tries to improve the quality of the 4.6 release by triaging all recent bug reports (bugs from 4.6-beta1 and the pre-beta versions). We also check if the bugs for 4.5 apply for 4.6 and triage those.

Prerequisites

You should have a recent version of KDE, preferably trunk or the beta 1 release. You can still help if you only have the 4.5.3 release though.

LiveCD

Some packagers provide LiveCD/DVDs to faciliate testing:

Packages

For some distributions pre-compiled and -packaged versions of trunk or the beta are available in additional repositories, ready for consumption:

Sources

If there are no packages for your distribution, you can always build KDE. kdesrc-build is a nice way to get the newest code and have it compiled for you. Be sure to get the sample rc from trunk.

Is it a big bug?

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

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>

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 beta1 if you're using that). It would be helpful to add what distribution you use.

IRC Nickname KDE version used for testing Distribution
Brot 4.6 beta 1 Kubuntu 10.10
radu 4.6 beta 1 openSUSE 11.4 Milestone 3
javier_ 4.6 Beta1 openSUSE 11.4 Milestone 4
annma trunk compiled
codertux 4.6 beta 1 Chakra

Details

Please select a batch 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.

Hints

  • Take note of bugs with high priority and put them in the section titled High priority bugs.
  • 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.
  • Some bugs will only be reproducible on certain graphics hardware, so for workspace-related bugs also 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-eyes 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.

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 5 annma Done Query
2 5 annma Done Query
3 5 radu Done Query
4 5 brot in Progress Query
5 5 radu In progress Query
6 5 codertux In progress Query
7 5 Query
8 5 Query
9 5 Query
10 5 Query
11 5 Query
12 5 Query

(total bugs: 60)

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.

High priority bugs

Some bugs are more important than others, eg.

  • Crashes that happen often
  • Bugs reported by many users
  • Bugs affecting large parts of our software
  • Bugs rendering important application functions unuseable

If you think a bug is of high priority and needs to be fixed as soon as possible, put it here.

Bugs needing Version Field changed

If you don't have bugzilla permissions yet, you can't change version fields. Put what needs changing here and someone else will go through and do it for you.

Valid bugs with step-by-step instructions

If it is a deterministic bug, put it here. Make sure it has instructions. You should be able to verify it. (Write that you did on bugzilla and include your version information.)

Bugs that are RESOLVED

If the bug doesn't exist anymore, it goes here. WORKSFORME!

  • bug #257894 - I can't reproduce this; i did notice it some time ago though, it might have been fixed in the meantime
  • bug #257954 - This looks like it was fixed in KMail 2.0.89
  • bug #257972 - Neither me nor the reporter were able to reproduce this
  • bug #253386 - I wasn't able to reproduce it in both kde 4.5.4 and kde 4.6 beta 2. It looks like it was fixed.

Duplicate Bugs

Put suspected duplicates here.

INVALID bugs

A bug is INVALID if it describes desired behavior, or something that isn't a bug.

Valid bugs that should be marked as NEW

If a bug was previously UNCONFIRMED and you can reproduce it, put it here.

  • bug #256952 was reproduced in another language thus confirmed. CCed a l10n guru to the bug.

KWin bugs that need attention from developers

If anything is in doubt, put it here, and give a description of why you think a developer should look at it.

Bugs needing Feedback

If a bug sounds valid but can't really be reproduced and needs more information from the reporter, put it here.

  • bug #257596 duplicates are older and should be fixed, I asked if the reporter could reproduce and to try with default settings.
  • bug #257979 - Can't reproduce this with kmail 2.0.89, but the reporter can with the same version
  • bug #257976 - Can't reproduce this with kmail 2.0.89, but the reporter can with the same version
  • bug #253499 is related to the kmail spam filter, but the spam detection tool used is not mentioned

Bugs that need particular setups/equipment to test

If a bug needs for example special hardware or a specific video driver or other particular configuration, put it here.

  • bug #257953 needs a soundcard with "tone" switches. my soundcard doesnt offer those switches. also this should be tested without pulseaudio
  • bug #252974 - you need an imap account with a large inbox with subfolders
  • bug #253000 - you need an imap account with a large inbox with subfolders

Performance issues

Put here bug reports against performance issues.

Bugs you can't do

If there are bugs you can't test for whatever reason (apart from the ones needing a particular setup which have their own section), fill those in here.

  • bug #257842 - I can't reproduce this bug and didn't find any similarities with existing bugs;

Wishes

If the bug should actually be a wish and needs to be marked as such, put it here.


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