Hello Andre, > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Andre Klapper > Sent: Wednesday, June 29, 2011 8:58 PM > To: [email protected] > Subject: Re: [Meego-qa] [MeeGo-dev] Poor decision making in MeeGo, > again ... > > On Wed, 2011-06-29 at 11:44 +0800, Zhao, Fan wrote: > > It's originally sent to meego-qa and meego-release mailing lists. > > ...which didn't address all parties that were and are affected by this > decision. Not the first time this happens. > > > I just forwarded it to meego-dev mailing list in case some dev didn't > > subscribe these 2 mailing list. > > Does that imply that you expect developers to be subscribed to -qa or > -releases? Because I wouldn't... > > andre > --
I am a little confused here, who are responsible for detecting such risk/impact and involving more people for discussion if necessary? May I suppose it should be EM team? however I didn't find clear definition within EM page (http://wiki.meego.com/Quality/Error_Management)... Anyway, to avoid its happening again, how about we start from enhancing bugzilla Request Process? http://wiki.meego.com/Quality/BugzillaRequestProcess: How MeeGo Bugzilla requests are handled Have a bug report or feature request for the complete requests both for code level and new custom fields & new flags; Error management team will provide feedback in one working day normally once receive the request notification; The follow up and feedbacks should happen in the bug/feature comments in the report; + Error management team will involve more people for discussion if the request impacts more parties; + once the implementation is done, Error management team will send out announcement letter to inform people; For minor change like component adjustment and component owner changes, MeeGo Bugzilla admins will go ahead directly but nice to have a ticket. Btw: As for R&R of EM, it is another history and Eric will define it according to http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-06-28-06.58.html Thanks, Elva _______________________________________________ MeeGo-qa mailing list [email protected] http://lists.meego.com/listinfo/meego-qa
