[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-panel-devel
Subject: Re: Re: Thoughts about a better Quality Management process for Plasma
From: David Edmundson <david () davidedmundson ! co ! uk>
Date: 2013-02-18 14:48:41
Message-ID: CAGeFrHDARoOLWD5-mfk52HNamqDPSwWAFOXCeVGb2Cr0kzJ5qg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Thu, Jan 17, 2013 at 11:51 AM, Martin Gr=E4=DFlin <mgraesslin@kde.org> w=
rote:
> On Thursday 17 January 2013 11:22:04 David Edmundson wrote:
> > This morning I spent an hour going through the list of "general", I
> > found a few problems.
> >
> > There were several bugs I looked at where the relevant component
> > didn't exist (webslice plasmoid, timer plasmoid).
> > All plasmoids should have a component, it's much easier to manage lots
> > of small lists than one big one, especially for delegating. I created
> > components for the items I found (hope that's OK), and will continue
> > to do so. If anyone else finds one of these, ping someone with
> > bugzilla superpowers (like me)
> I think that's the way to go. As I wrote: there should be a component for
> it.
> >
> > There are a lot of crashes filed against general, looking at the
> > backtrace it's impossible to see who's at fault. The backtrace only
> > shows some timer firing, or a python binding call or something generic
> > - it's impossible to tell what's at fault. I have no idea how we can
> > fix this.
> For those crashes the most important one is whether there is a way to
> reproduce them. If not -> garbage. No use in a crash report where we don'=
t
> know what caused it.
> >
> > Some bugs weren't even against plasma (as devs know it). As we use the
> > phrase "plasma workspaces" I guess it's natural for bugs to end up
> > here which are totally generic. I found bugs on kwin, dolphin, and
> > other KDE things. I don't think there's really a fix for this.
> ah that was the reason for the bug you moved to us :-)
>
> It's a common thing to happen. In KWin we get bugs for:
> * Plasma
> * X
> * screen locker (that's very recent due to the original plans to move it
> inside KWin)
>
> So I think it will always happen that bugs are wrongly reported. Actually
> that's what I would love to have the bug squad for. No need to have devs
> move
> it around.
> >
> > There's a lot of wishlists.
> > I found these very hard to triage because I can't say on someone
> > else's project saying "we're never doing this, wontfix", which I would
> > do on my projects (maybe slightly more politely). I imagine many
> > others are in the same position, how can we manage this?
> get a proper policy, like wishes only on brainstorm. I just find
> bugtrackers
> unsuited for wishes.
>
> I went through plasma - general again today and on top of the usual bits
of triage I made a list of all requests for new plasmoids and new
wallpapers.
I want to triage these out of general and put them into a new component
"plasma-requests", or we can go with Martin's suggestion for all feature
requests and just close them.
I don't generally agree with the concept of close all wishlists, however
new plasmoids are the most extreme case of wishlists and I think in this
case it makes sense.
If we have a ruling, I'l update all of them.
List of new plasmoids:
163593
171737
186974
187562
199001
203313
208742
219631
229768
259598
314223
315352
157048
169457
> Thanks for looking into it :-)
>
> --
> Martin Gr=E4=DFlin
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel@kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
>
[Attachment #5 (text/html)]
<br><br><div class="gmail_quote">On Thu, Jan 17, 2013 at 11:51 AM, Martin Gräßlin \
<span dir="ltr"><<a href="mailto:mgraesslin@kde.org" \
target="_blank">mgraesslin@kde.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">
<div>On Thursday 17 January 2013 11:22:04 David Edmundson wrote:<br>
> This morning I spent an hour going through the list of "general", \
I<br> > found a few problems.<br>
><br>
> There were several bugs I looked at where the relevant component<br>
> didn't exist (webslice plasmoid, timer plasmoid).<br>
> All plasmoids should have a component, it's much easier to manage lots<br>
> of small lists than one big one, especially for delegating. I created<br>
> components for the items I found (hope that's OK), and will continue<br>
> to do so. If anyone else finds one of these, ping someone with<br>
> bugzilla superpowers (like me)<br>
</div>I think that's the way to go. As I wrote: there should be a component for \
it.<br> <div>><br>
> There are a lot of crashes filed against general, looking at the<br>
> backtrace it's impossible to see who's at fault. The backtrace only<br>
> shows some timer firing, or a python binding call or something generic<br>
> - it's impossible to tell what's at fault. I have no idea how we can<br>
> fix this.<br>
</div>For those crashes the most important one is whether there is a way to<br>
reproduce them. If not -> garbage. No use in a crash report where we don't<br>
know what caused it.<br>
<div>><br>
> Some bugs weren't even against plasma (as devs know it). As we use the<br>
> phrase "plasma workspaces" I guess it's natural for bugs to end \
up<br> > here which are totally generic. I found bugs on kwin, dolphin, and<br>
> other KDE things. I don't think there's really a fix for this.<br>
</div>ah that was the reason for the bug you moved to us :-)<br>
<br>
It's a common thing to happen. In KWin we get bugs for:<br>
* Plasma<br>
* X<br>
* screen locker (that's very recent due to the original plans to move it<br>
inside KWin)<br>
<br>
So I think it will always happen that bugs are wrongly reported. Actually<br>
that's what I would love to have the bug squad for. No need to have devs move<br>
it around.<br>
<div>><br>
> There's a lot of wishlists.<br>
> I found these very hard to triage because I can't say on someone<br>
> else's project saying "we're never doing this, wontfix", which \
I would<br> > do on my projects (maybe slightly more politely). I imagine many<br>
> others are in the same position, how can we manage this?<br>
</div>get a proper policy, like wishes only on brainstorm. I just find \
bugtrackers<br> unsuited for wishes.<br>
<br></blockquote><div>I went through plasma - general again today and on top of the \
usual bits of triage I made a list of all requests for new plasmoids and new \
wallpapers. </div> <div><br></div><div>I want to triage these out of general and put \
them into a new component "plasma-requests", or we can go with Martin's \
suggestion for all feature requests and just close them. </div><div> <br></div><div>I \
don't generally agree with the concept of close all wishlists, however new \
plasmoids are the most extreme case of wishlists and I think in this case it makes \
sense.</div><div><br></div><div>If we have a ruling, I'l update all of \
them.</div> <div><br></div><div>List of new plasmoids:</div><div>
<p style="margin:0px"><span style="font-family:'Sans \
Serif';font-size:9pt">163593</span></p> <p style="margin:0px"><span \
style="font-family:'Sans Serif';font-size:9pt">171737</span></p> <p \
style="margin:0px"><span style="font-family:'Sans \
Serif';font-size:9pt">186974</span></p> <p style="margin:0px"><span \
style="font-family:'Sans Serif';font-size:9pt">187562 </span></p> <p \
style="margin:0px"><span style="font-family:'Sans \
Serif';font-size:9pt">199001</span></p> <p style="margin:0px"><span \
style="font-family:'Sans Serif';font-size:9pt">203313</span></p> <p \
style="margin:0px"><span style="font-family:'Sans \
Serif';font-size:9pt">208742 </span></p> <p style="margin:0px"><span \
style="font-family:'Sans Serif';font-size:9pt">219631</span></p> <p \
style="margin:0px"><span style="font-family:'Sans \
Serif';font-size:9pt">229768</span></p> <p style="margin:0px"><span \
style="font-family:'Sans Serif';font-size:9pt">259598</span></p> <p \
style="margin:0px"><span style="font-family:'Sans \
Serif';font-size:9pt">314223</span></p> <p style="margin:0px"><span \
style="font-family:'Sans Serif';font-size:9pt">315352</span></p> <p \
style="margin:0px"><span style="font-family:'Sans \
Serif';font-size:9pt">157048</span></p> <p style="margin:0px"><span \
style="font-family:'Sans Serif';font-size:9pt">169457</span></p></div><div> \
</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks for looking into it :-)<br>
<br>
--<br>
Martin Gräßlin<br>_______________________________________________<br>
Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org" target="_blank">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br> \
<br></blockquote></div><br>
_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic