Plans for a Dolphin bug triage event

Myriam Schweingruber myriam at kde.org
Tue Sep 18 14:40:58 BST 2012


Hi Frank,

On Tue, Sep 18, 2012 at 3:19 PM, Frank Reininghaus
<frank78ac at googlemail.com> wrote:
> Hi Myriam,
>
> thanks for your input, and sorry for the very late reply! I just
> realised that I completely forgot to answer your message.
>
> 2012/9/2 Myriam Schweingruber:
> [...]
...
>> May I add one important point:
>>
>> 5. Attribute versions to all open Konqueror bugs.
>>
>> Currently there are 391 open Konqueror reports with no version set.
>> Those bugs are hard to track if there is no version field, so I think
>> if there is a bug triaging event happening these should be first
>> cleared and have versions set (or be closed as outdated as some are
>> probably pre-KDE 4.6).
>
> Currently, a bit more than one third of Dolphin's bug reports do not
> have a version [1].
>
> The value of the "Version" field should probably the version that the
> bug has been reported for, right? One could also use the last version
> that the bug could be reproduced in, but then one would have to update
> the field quite frequently, which does probably not make much sense.

On the contrary, it allows us to know which version this is
reproducible with, and since we do not backport fixes to previous
stable releases, the version field should always reflect the latest
version this is reproducible with. Of course it is a bit of work, but
since we should go through older bugs every now and then this is the
perfect field to filter out older reports that need attention.

BTW, I added a saved search on b.k.o for the dolphin bugs without
version: https://bugs.kde.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Dolphin%3A%20missing%20version&sharer_id=70102&list_id=216695

You can simply add it to your footer in your saved searches
>
>> I am usually around to give a hand, but since I am only a triager it
>> would be good to have a developer around.
>>
>> As for using the forum: this is a very good idea, but since the forum
>> is an asynchronous media you would need more time than just a weekend,
>> usually a week is more useful. I think it is also a good idea to
>> combine the media: do a bug week in the forum which ends with a bug
>> squashing weekend on IRC.
>
> Yes, a week should be the minimum, or maybe even a month - if the bug
> reports are all done at some point and there are still triagers who
> are not too bored yet, we could start assiging meaningful components
> to the wishlist items, which might also be quite helpful. When we do
> it in October, I would have enough time to prepare a wiki page to
> organise the work and blog about the triage event.

I don't think you will have a lack of work for bored triagers, b.k.o
is full of work for them :)
>
> I'll send another message to the Bugsquad list soon, maybe we'll get
> some more useful ideas then.

Looking forward to it :)

Regards, Myriam

-- 
Proud member of the Amarok and KDE Community
Protect your freedom and join the Fellowship of FSFE:
http://www.fsfe.org
Please don't send me proprietary file formats,
use ISO standard ODF instead (ISO/IEC 26300)




More information about the kfm-devel mailing list