[Bugsquad] Looks like this bug is fixed ...

[Richard llom]

Hi Myriam,

Myriam Schweingruber wrote:
> On Thu, Apr 18, 2013 at 12:23 AM, Richard llom
> <richard.llom at gmail.com> wrote:
>> Am 17.04.2013 21:22, schrieb Myriam Schweingruber:
>>>
>>> On Wed, Apr 17, 2013 at 8:21 PM, Richard llom
>>> <richard.llom at gmail.com> wrote:
>>>>
>>>> by random I noticed that notifications, do not longer have their lower
>>>> part
>>>> cropped. I did some testing and I think this is fixed as of 4.10.2 :
>>>>
>>>> https://bugs.kde.org/show_bug.cgi?id=278309
>>>>
>>>> However since there is no comment at all from any dev, does this mean
>>>> this
>>>> bug was fixed unintentional i.e. by "accident" ;-) ? Or do the/some
>>>> devs have their own bugtracker?
>>>
>>>
>>> This was not fixed, see comment #7 and no, the developers do not have
>>> another bugtracker.
>>>
>> It wasn't fixed in *4.10.1 *, but as I said it is (at least here) in
>> 4.10.2. (However I will ask the reporter to make sure.)
> 
> 
> Please just leave that report closed,
> 
I can't reopen the bug and I did not so in the past.

> the new QML Notification went
> life in 4.10.2, the old non-QML notification app is not shipped
> anymore and will not get any code contribution anymore.
> 
On bko you wrote it is 4.10 now it is 4.10.2 what is the case now?

>>> No idea who reopened that, but the notification you see now in KDE
>>> 4.10.2 is a different application, the old one is unmaintained and I
>>> closed it as unmaintained with that comment...
>>>
>> Your comment (and the previous) is highly unclear:
>> Does the different application mean there is a new product/component in
>> bko? If so, which one?
> 
> What is unclear? It is not maintained anymore because it is replaced
> by a re-write in QML. If you want more information ask the Plasma
> developers, I only do the triaging work.
>>
>> If not, why then fill a new report? The component in question could have
>> been rewritten a 1000times (since those 2years) does this mean the report
>> has to be rewritten a 1000times as well? I don't think so.
> 
> Erm, that makes absolutely no sense to me, sorry.
>>
>> IMHO this should be moved to the new component (if there is) and marked
>> as resolved *fixed*.
> 
> No, as it was not "fixed"in that product. What do you not understand
> in the fact that those are two different products?
> 
Yes, I do not understand, because you don't tell me.
>> Does the different application mean there is a new product/component in
>> *bko*? If so, which one?
What is the answer to this questions? I still don't know.


> The code in product
> A which the bug report refers to is faulty, the product is
> discontinued as a better, new notification written with QMl replaces
> it.  The notification you see in KDE 4.10.2 is a different code.
> 
And the question is does it matter if there is a different code or not?

IMHO the version and date mark the initial occurrence of a bug in the KDE SC 
(as a whole).[1]
The code changes (i.e. is different) with every git-commit, so according to 
your logic after every git-commit all bugs are are to be marked as resolved 
unmaintained... ;-)


Of course this still means the bug has to be (re-)validate after every code 
change (which was the case here, see comment #1, #2, 4# and #6). But you are 
proposing to close and open a new bug each time instead. This is not what 
I'm used to from other bugzillas/projects and it still doesn't sound very 
reasonable to me.


Regards
richard



1:
>From BKO:
> Version
> The version field defines the version of the software the bug was
> found in.
i.e ... was (first) found in.