Sorry people on meego-qa, You did not get the original mail because "it was automatically discarded". I hope you don't get utterly confused with the different posting styles -- this conversation seems to be a good example of why top-posting is bad. You will find the original post at the bottom.
On 10/21/2010 01:31 PM, Liu, Bing Wei wrote: > It's a typical example - when a bug does not seem to have a clear > component to assign, it is easily neglected at the corner. Are we > kind of lacking bug triage efforts on the ambiguous bugs? > - Bingwei Hi Bing Wei, It's possible that better triage would have made the situation better, but this is a highly "cross-stack" problem area and I think solving the problems requires that we step out of our little boxes. Also, knowledge of power management problems down the stack would be useful for power management UI developers even when they are correctly triaged. - Jussi >> -----Original Message----- From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On >> Behalf Of Jussi Kukkonen >> I've been working on the Netbook UX parts related to power >> management and have realized that we have a QA communication >> problem in areas that do not conform to the bugzilla product >> boundaries. Issues around suspend/idle/power management are one of >> those: bugs are filed all over the bugzilla and I'm fairly sure >> no-one can keep track of them currently. This is _not_ the fault of >> the bug reporters: it's often impossible to know the correct >> component and there are at least a dozen different possible >> components all over the stack. >> >> This means important bugs fall through cracks as the relevant >> developers do not see the bugs. Bug 5794 was a good example: QA >> found it 2 months ago and then _nothing_ happened (except for a >> seemingly arbitrary decision to not fix it for 1.1‽‽). The required >> fix was simple enough: change "moblin" to "meego" in one script... >> >> >> Question: Is there a bugzilla best practice that makes sure >> <developers-interested-in-power-management> get email notifications >> of bugs that reporters or QA think might be related to power >> management, regardless of their actual product or component? >> >> The only solution that I could think of was a dummy "pm-bugs" user >> that QA CCs on relevant bugs and developers watch. Any better >> suggestions? >> >> - Jussi _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
