[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: The number of unassigned bugs is worrisome
From:       Thiago Macieira <thiago () kde ! org>
Date:       2006-01-13 11:31:52
Message-ID: 200601130931.53183.thiago () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Dirk Stoecker wrote:
>Let me note about this:
>In April I filed this bug report:
>https://bugs.kde.org/show_bug.cgi?id=104259
>
>It is easy to reproduce and also has been reproduced by others and
>has been rereported. It is still UNCONFIRMED.
>
>For me this reads a following: No developer ever had a look at this
>report.

I personally read each and every bug report and comment sent to the KDE 
Bugzilla. There are some other people who do that too, and a couple doing 
it only for Konqueror bugs. We even have people who dedicate 100% of 
their KDE time to test Konqueror bugs.

Unfortunately, it happens that I get swamped with other tasks and my 
kde-bugs-dist mailbox grows too much. When that happens, I need to start 
skipping reports, or simply mark them all read in order to start again. I 
can imagine the same happens to the other bug testers.

I don't know what happened to yours. Maybe it fell through the cracks too. 
Reminding us every once in a while helps too. (I've just responded to 
yours)

Hint: if you *attach* a testcase, testing and confirming becomes a matter 
of clicking, not of copying the text, opening an editor, saving the file 
and then opening in the browser.

>As making good bug-reports is really lots of work you discourage 
>bug reporters to report bugs, because:
>
>a) You need a login for reporting bugs
>b) For a good report you need to describe reproducable procedure. This
>   means multiple testings and good description.

Thankfully, because we DON'T want lazy bug reports.

>The bug-report guideline I usually follow (not yet for KDE):
>1) UNCONFIRMED bugs should be tested fast (really fast, no intensive
>   testing). If confirmed, set confirmed.
>2) If not confirmable, ask for more information. After a timeout (e.g. 2
>   weeks) without additional information set to CLOSED/INVALID.
>
>A state NEEDINFO would be good after step 1, as exists in other bug
>trackers.
>
>This means after a short time every bug either gets confirmed or is
>closed. The users are much happier if they know the bug is recogniced.
>Ignoring their work discourages them.
>
>Every developer doing one or more randomly choosen bug report in his
>projects per KDE-working day...

Those are good proposals. In fact, I think it would already help a lot to 
have a RESOLVED/NEEDINFO state. Not that we can't do it with 
RESOLVED/WORKSFORME already...

What we do need is manpower. If each Konqueror developer fixed only one 
bug per day in Bugzilla, we'd see the number grow absurdly for Konqueror.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

3. Ac seo woruld wearð geborod, swá se Scieppend cwæð "Gewurde Unix" and 
wundor fremede and him "Unix" genemned, þæt is se rihtendgesamnung.

[Attachment #5 (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]