gt; ton, but now that beta is out (and even worse when the final will come out)
> there will be a significant number of reports
>
> I am already picking some sign of the situation repeating in the form of
> one
> thing: old bugs of dubious reproducibility that just stay there rot
gt; ton, but now that beta is out (and even worse when the final will come out)
> there will be a significant number of reports
>
> I am already picking some sign of the situation repeating in the form of
> one
> thing: old bugs of dubious reproducibility that just stay there rot
ow that beta is out (and even worse when the final will come
> out) there will be a significant number of reports
>
> I am already picking some sign of the situation repeating in the form of
> one thing: old bugs of dubious reproducibility that just stay there
> rotting away. I do no
On Wed, May 14, 2014 at 12:47 PM, David Edmundson <
da...@davidedmundson.co.uk> wrote:
> https://bugs.kde.org/show_bug.cgi?id=331956 has been updated recently.
> It seems active. I see it too.
>
I have this bug here every single day. I think noone actually really looked
into yet.
Cheers
--
Mart
https://bugs.kde.org/show_bug.cgi?id=331956 has been updated recently.
It seems active. I see it too.
The other one we can close.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
Do it.
Bugs can always be re-opened.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
will be a significant number of reports
I am already picking some sign of the situation repeating in the form of one
thing: old bugs of dubious reproducibility that just stay there rotting away.
I do not want this to repeat, even if this means closing old stuff that still
happens for somebody in