Hi, > -----Original Message----- > From: Adalberto Medeiros [mailto:[email protected]] > Sent: Friday, December 06, 2013 11:18 PM > To: OpenStack Development Mailing List > Subject: [openstack-dev] [qa][tempest] Bug triage and monitoring process > > Hello all! > > Yesterday, during the QA meeting, I volunteer myself to help the team > handling bugs and defining a better process to triage them.
Thanks for doing this, this would help for digging problems. > Investigating the current bug list, I checked we have: > > * 7 critical and high bugs. From those, 3 critical non-assigned: > https://bugs.launchpad.net/tempest/+bugs?search=Search&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH > &assignee_option=none One HIGH report has been solved the last weekend, and I have been changed it. and I tried to solve the other one(https://bugs.launchpad.net/tempest/+bug/1213209), but I cannot find the way. This seems a libvirt problem, but we don't have some log file under /var/log/libvirt in gate tests. Can we add these log files to gate tests for digging this kind of problems? > * 113 new bugs > * 253 open bugs > > The first step here is to triage those NEW bugs and try to verify as > much as possible the OPEN bugs are being addressed. One goal is to check > duplicates, find assignees, confirm if the bugs are still valid and > prioritize them. Another one is to ensure recheck bugs are marked > correctly (critical or high) and that they have the right people looking > at them. Finally, it's important to revisit old bugs in order to check > they are still valid and re-prioritize them. > > To accomplish that, I would like to suggest a Bug Triage Day for next > week on Thursday, 12th (yup, before people leave to end-of-year holidays > :) ). > > The second step, after getting a concise and triaged bug list, is to > ensure we have a defined process to constant revisit the list to avoid > the issues we have now. I'm would like to hear suggestions here. > > Please, send any thoughts about those steps and any other points you > think we should address for monitoring the bugs. We may as well define > in this thread what is needed for the bug triage day. I feel these steps are nice, thanks! Thanks Ken'ichi Ohmichi _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
