[Meego-qa] BoF MeeGo Bugzilla Structure Enhancement Prototype in SF conference - Meeting minutes

[Wan, Shuang]

Hello,


We had a MeeGo QA BoF at San Francisco conference for demonstrating bugzilla structure enhancement prototype:
http://sf2011.meego.com/program/sessions/bof-meego-bugzilla-structure-enhancement-facilitate-bug-reporting-and-bugs-disposit

There were ~15 attendees in this session. The session time was 40 minutes.


We had a brief explanation of basic motivation & idea and then demoed the prototype Bugzilla to attendees. There was a hot discussion on the 3 open topics in this session and the answers as bellow:


Q1: Package maintainer might refer only the integrator in MeeGo distribution team and not exact the developers or maintainer of that package

A1: The package maintainer from MeeGo distribution team is really the package maintainer.



Q2: There should be a group of peoples working on the package: developer, legal guys etc;

A2: Currently Bugzilla only supports default assignee and QA contact. For other relevant peoples could be presented on default cc list.



Q3: The SUBMITTED resolution is not necessary. We could enforce developer to set the bug status to RESOLVED FIXED only when the fix is integrated into OBS.

A3: We may need to distinguish these 2 statuses RESOLVED FIXED and RESOLVED SUBMITTED. The RESOLVED FIXED is used to mark the fix has been submitted into git tree personal repository branch and later one is used to mark the fix has been submitted into git tree main line branch. If we don't have separated resolutions to identify each status, there will be a project updating latency since usually it will take some time to integrate the fix into main line branch from personal repository branch. Therefore separated status will make it clear to identify each status both for human and possible automation tool.



And one issue discussed in F2F sync up on MeeGo conference 2011:

Q1: The changes need to be encapsulated by extension mechanism;

A1: Totally agree. But current 3.6 Bugzilla doesn't have enough hooks to satisfy this requirement. The fallback solution was agreed that we port the necessary APIs from 4.0 to 3.6.


In addition, prototype bugzilla url is as bellow, welcome to have a try and share you feedbacks and suggestions:
https://02.bugs-dev.meego.com/

We also tracked this as a new Bugzilla feature request for further follow up, please refer bellow:
https://bugs.meego.com/show_bug.cgi?id=18308

Please correct me if something lost and or something wrong.

Thanks
Shuang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.meego.com/pipermail/meego-qa/attachments/20110531/16d664fa/attachment.html>