On Saturday, January 12, 2013 02:04:13 Jekyll Wu wrote: > If there is such an (plasma) master available, I think he/she should > probably better spend time on development, instead of on "poking others".
that's a lovely idea, but who knows who needs to be poked when but someone who knows the technology inside and out and keeps a close eye on how it progresses? > Don't get me wrong. I'm not implying that quality assurance is not > important. I just feel it is the wrong way to improve quality to expect > some master to notice the problem and then poke you. That doesn't scale. > It might work in a short time, but I bet it will fail in the long term. it's not the whole solution, no. but it's a critical part of the solution. it is what kept the biggest, as well as some of the smaller, problems from reaching releases in past years. having someone who watches the overall state of things with some number of other people concentrating more on specific areas and/or looking exclusively at bugs.kde.org will result in a high % of problems caught and a good pace of movement forward. it is exactly what we did when plasma was moving fastest. > I ask that because I don't notice(hint again, > I'm subscribed to kde-bugs-dist@) many plasma developers are dealing > with incoming bug reports in a regular and timely way. used to. > watch it and receive no bug reports at all. What if I'm only interested > with three components which are currently assigned to plasma-bugs@ ? > There is no plasma-kickoff-bugs@, plasma-taskbar-bugs@, > plasma-pager-bugs@, plasma-battery-bugs@, etc . if someone wants to take one of these on over the long term, that's great, and we could accomodate that with CC's on the BR (bugzilla supports this). history shows, however, that people don't. -- Aaron J. Seigo
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/plasma-devel
