[Meego-qa] MeeGo netbook bugs triage on Nov 16th
yan.yin at intel.com
Tue Nov 16 17:17:57 PST 2010
Is it better for developers to change the bug status to RESOLVED FIX after they really submitted the fix to correct trunk/branch?
It can avoid the case that developers forget to deal with this bug as it's already RESOLVED, not NEW or ASSIGNED.
From: meego-qa-bounces at lists.meego.com [mailto:meego-qa-bounces at lists.meego.com] On Behalf Of Tao, Daniel
Sent: Tuesday, November 16, 2010 9:33 PM
To: meego-qa at lists.meego.com
Cc: Burton, Ross
Subject: [Meego-qa] MeeGo netbook bugs triage on Nov 16th
Time: 9:00 PM China, 1:00 PM UK
Below netbook bugs are triaged through #meego-bugs irc.
For the details, please refer to the attached logs. Appropriate comments are also added in bugzilla as necessary.
#9792 (Fail to pair keyboard in bluetooth panel): Keep severity as normal
#9807 (Status panel's reply and retweet function is not properly work): Change status to "resolve+fix" and hope developer submit the fix into trunk
#9809 (Unable show Chinese task in myzone panel): Change status to "resolve+fix" and hope developer submit the fix into trunk
#10025 (IM fail to login with network proxy configured): This is an upstream issue and mark as "waiting for upstream"
#10038 (status panel used now-removed API): Keep severity as normal
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MeeGo-qa