<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 06/04/2012 11:41 AM, Thijs Heus wrote:
<blockquote
cite="mid:CACa3R7Akj-J-8kwS91Waxuo4SAi=E3x9SueV3mvB-1t2fcQGJg@mail.gmail.com"
type="cite">
<div class="gmail_quote">On Sun, Jun 3, 2012 at 10:41 PM, Marco
Martin <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:notmart@gmail.com" target="_blank">notmart@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br>
</div>
</blockquote>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
> 2) Are the components useful? I could see a lot of use
for grouping bugs,<br>
> and trying to keep a component bug free. But again -
only when it is in<br>
> use. And what is the difference between e.g.
containment-desktop and<br>
> desktop?<br>
<br>
</div>
i think components are fine, maybe there could be a couple
more but thise are<br>
fine. in this particular case containment-desktop means
strictly what happens<br>
in the desktop background area, while desktop is the plasma
desktop shell<br>
application, the actual executable that creates desktops,
panels etc. yeah i<br>
know, jargon :/<br>
<div><br>
</div>
</blockquote>
<div>OK, clear. If there is one place where jargon is allowed,
it is BKO, as long as it is being used consistently. I guess
there has been a fair amount of mix up there, but I'll check.</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
> 3) There is a fair amount of bugs that need to be
treated with the<br>
> authority and wisdom of a developer. I can be almost
certain that a bug is<br>
> a wont fix, but only a dev can mark it as such. I could
keep a list of such<br>
> bugs, and throw them over this mailing list once in a
while, or perhaps a<br>
> flag "for_devs" could work here. This would not be
meant as a kicking devs<br>
> to fix a bug, but should only take 2 minutes of time to
comment/check<br>
> out/close/whatever.<br>
<br>
</div>
something that would be very useful i think is a day of irc
meeting with you<br>
guys to do this kind of not immediately obvious prioritization
and maybe with<br>
people taking tasks for actually fixing the ones with more
priority.<br>
<br>
next weeks are quite thehorror (talking at least for me and
probably aaron) we<br>
could manage to do something in the second half of june a bit
before akademy<br>
perhaps?<br>
</blockquote>
<div><br>
</div>
<div>I'll try and keep a list of bugs to check. When life allows
it, I lazily am around at irc, so if anyone is bored ;) </div>
<div>A (minor) bugdays would be useful, but in the case of late
June I would combine oldbug-compression with the
beta-polishing and a focus on the latest bugs and regressions.
Other than that, there is no real urgency for me - as long as
we can work our way to a reliable (and short) buglist.</div>
<div><br>
</div>
<div>Thijs</div>
</div>
<br>
</blockquote>
Some bugs need to be fixed before 4.9 is out: for example the
Weather Station applet does not display anything anymore (API
changes from ions I suppose) so it'll be either fixed or removed as
we cannot seriously ship things that are really broken.<br>
<br>
Anne-Marie<br>
<br>
</body>
</html>