Can someone take a look?

[Myriam Schweingruber]

On Sat, Mar 30, 2013 at 2:53 PM, Richard llom <richard.llom-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote:
> Hi Myriam.
>
> Myriam Schweingruber wrote:
>> On Fri, Mar 29, 2013 at 12:39 AM, Richard llom wrote:
>>> keditbookmarks crashed here. With DrKonqi and stumbling around in bko I
>>> found these two bugs:
>>> https://bugs.kde.org/show_bug.cgi?id=287038
>>> https://bugs.kde.org/show_bug.cgi?id=258505
>>>
>>> 1. They seem strongly related to each other, so I would suggest to set a
>>> block/depends flag, name bug in "See also" or set one even as dup.
>>>
>>> 2. Both bugs are 100% reproducible, so I guess they deserve the
>>> "reproducible" keyword.
>>>
>>> 3. I added a Valgrind trace to bug 28703. However judging from the CC,
>>> there seems to be no dev watching... :-( How could I "attract" one?
>>
>> Thank you for the report, but this should go to the konqueror
>> developer list, setting the Cc.
>>
> Ok, how about the reproducible keyword?

We don't use that, instead the status is set to confirmed, as only
reproducible bugs are getting that status.

> And regarding the relation of the bugs:
> I guess a "See also" link cannot harm, also considering the few manpower
> here ... :-( (this should ease things).

As I said, that is not up to me to set that, let the maintainers do
this. Again, you did NOT send this to the correct mailing list, Cc:ing
them.

In general: the kde-testing mailing list is not for bug reports to the
individual projects, those need to be sent through bugzilla, as the
developers are automatically assigned the bugs correctly. You can
always send an additional mail to the relevant developer list, but
that is generally not necessary, they do see the bug reports when they
come in.


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)