In general: +1. On Thu, 2011-06-30 at 10:41 +0800, Fu, Elva wrote: > 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;
Yes, *public* feedback from affected parties is needed earlier to avoid irritation and frustration in the future. That's what I was asking for in https://bugs.meego.com/show_bug.cgi?id=19369#c5 ... > + once the implementation is done, Error management team will send > out announcement letter ...on public mailinglists... > to inform people; ...that will be affected by the change. > 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 > andre -- Andre Klapper (maemo.org bugmaster) http://www.openismus.com _______________________________________________ MeeGo-qa mailing list [email protected] http://lists.meego.com/listinfo/meego-qa
