On Thu, 2011-06-16 at 15:18 +0800, Wan, Shuang wrote: > In addition, I just drafted a wiki page
It's not mentioned anywhere that it is a draft. > at meego.com wiki based on the discussions at F2F and ML, see bellow: > http://wiki.meego.com/Quality/BugzillaRequestProcess > Welcome to revise it if something lost or incorrect ;) After reading it twice I *guess* that it is about changes in MeeGo Bugzilla itself, and not in the MeeGo codebase? "Bugzilla Request Process" to me sounds like processing any kind of MeeGo platform requests in Bugzilla. Not clear what it means. * "This process is to ensure the features or changes are implemented & deployed under the planned way and also ensure the feature is generic enough for most of users." Does that refer to any MeeGo UX, or to the Bugzilla UI? * "Have a bug entry or feature entry for all change requests both for code level and new custom fields & new flags" Direct link welcome. Make it easy to create such entries... * "Error management team will provide feedbacks in one working day normally once receive the request notification" One working day is not enough if you don't want to have a national holiday and accidentially be excluded from decision process. I propose one week. * "but nice to have a bug entry for change request" Can we please make this a "should"? I am tired of all this intransparency. When I wanted to have admin rights for the MeeGo wiki I was also asked to file a bug report first, for transparency. And it made sense. * "Feedbacks from testing on our staging instances" So how can I test the "staging instances" please? Can you please link the URL on that wikipage? andre -- Andre Klapper (maemo.org bugmaster) http://www.openismus.com _______________________________________________ MeeGo-qa mailing list [email protected] http://lists.meego.com/listinfo/meego-qa
