Meego Wiki
Views

Quality/Bugtriage

From MeeGo wiki
< Quality(Difference between revisions)
Jump to: navigation, search
(MeeGo Bug Triage Team)
(MeeGo Bug Triage Meetings)
 
(26 intermediate revisions not shown)
Line 2: Line 2:
* Bug Triage is a process to:
* Bug Triage is a process to:
** Ensure bug report completeness  
** Ensure bug report completeness  
-
** Analyze and assign bug to proper component  
+
** Analyze and move bug to proper component if needed
-
** Assign bug to proper bug owner  
+
** Set Assignee of bug report (via "Assigned to" field) to proper bug owner  
 +
** Assign bug to packages listed in "MeeGo Distribution Packages" product whenever possible (apply for new incoming bug reports for version 1.3 ONLY at this moment)
** Set appropriate bug priority
** Set appropriate bug priority
** Adjust bug severity properly (initially set by bug reporter)
** Adjust bug severity properly (initially set by bug reporter)
Line 23: Line 24:
Triage Process Flow as follows:
Triage Process Flow as follows:
-
[[File:bug_triage_process.jpg]]
+
 
 +
[[File:bug_triage_2.PNG]]
== MeeGo Bug Triage Guide ==
== MeeGo Bug Triage Guide ==
Line 33: Line 35:
!|Member
!|Member
|-
|-
-
| MeeGo Core OS Triage || [http://meego.com/users/jerry Jerry Yu], Peter Zhu, [http://meego.com/users/shuangeeer Yanshuang Zheng], [http://meego.com/users/ttoropainen Tommi Toropainen], [http://meego.com/users/juhanitaipale Juhani Taipale], [http://meego.com/users/jarnoteivas Jarno Teivas], [http://meego.com/users/iekku Iekku Huttunen]
+
| MeeGo Core OS Triage || [http://meego.com/users/shuangeeer Yanshuang Zheng], [http://meego.com/users/ares2012  Jason Zhou], [http://meego.com/users/jarnoteivas Jarno Teivas], [http://meego.com/users/iekku Iekku Huttunen]
|-
|-
-
| MeeGo Handset UX Triage || Fan Zhao, Cathy Li, [http://meego.com/users/srikanthyarlagadda Srikanth Yarlagadda],[http://meego.com/users/mikikone Mika Ikonen], [http://meego.com/users/jylha Petri Jylha], [http://meego.com/users/pekoski Petri Koski], [http://meego.com/users/ceferron Chris Ferron], [http://meego.com/users/iekku Iekku Huttunen]
+
| MeeGo Handset UX Triage || [http://meego.com/users/fan Fan Zhao], Cathy Li, [http://meego.com/users/srikanthyarlagadda Srikanth Yarlagadda], [http://meego.com/users/iekku Iekku Huttunen]
|-
|-
-
| MeeGo Netbook UX Triage || [http://meego.com/users/lingyu Ling Yu], Daniel Tao, [http://meego.com/users/yanglei Lei Yang], [http://meego.com/users/rossburton Ross Burton]
+
| MeeGo Netbook UX Triage || Daniel Tao,[http://meego.com/users/rossburton Ross Burton]
|-
|-
-
| MeeGo Tablet UX Triage || [http://meego.com/users/lingyu Ling Yu], Daniel Tao, [http://meego.com/users/yanglei Lei Yang]
+
| MeeGo Tablet UX Triage || Daniel Tao, [http://meego.com/users/yanglei Lei Yang], Cathy Li
|-
|-
| MeeGo IVI Triage || [http://meego.com/users/shuangeeer Yanshuang Zheng]
| MeeGo IVI Triage || [http://meego.com/users/shuangeeer Yanshuang Zheng]
Line 45: Line 47:
| MeeGo Translation Triage || [http://meego.com/users/margie Margie Foster], [http://meego.com/users/pmccarty Patrick McCarty]
| MeeGo Translation Triage || [http://meego.com/users/margie Margie Foster], [http://meego.com/users/pmccarty Patrick McCarty]
|-
|-
-
| MeeGo SDK Triage || Juha Peisanen, Ionut Gavaz, Fathi Boudra, Jackie Wu, Max Yu
+
| MeeGo SDK Triage || [http://meego.com/users/ionutgavaz Ionut Gavaz], Jackie Wu, [http://meego.com/users/edmondas Edmondas Girkantas], Azadeh Karimian, Max Yu, Juha Peisanen
 +
|-
 +
| MCTS (MeeGo Core System Testing) Triage || Jeff Zheng,[http://meego.com/users/iekku Iekku Huttunen]
|}
|}
Line 61: Line 65:
** Time: TBD
** Time: TBD
* MeeGo SDK Bug Triage
* MeeGo SDK Bug Triage
-
** Time: Every Wednesday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
+
** Time: On demand on Wednesday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MCTS Bug Triage
* MCTS Bug Triage
** Time: Every Wednesday at 08:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
** Time: Every Wednesday at 08:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
Line 83: Line 87:
== Other references ==
== Other references ==
-
[[Quality/How_To_Report_Bugs|How to report MeeGo bugs?]]
+
*[[Quality/How_To_Report_Bugs|How to report MeeGo bugs?]]
-
 
+
*[[Quality/Triageteam_Assignee|How to deal with bugs assigned to triageteam@meego.bugs]]
-
[[Category:QA]]
+
*[[Category:QA]]

Latest revision as of 07:41, 23 August 2011

Contents

Bug Triage Definition

  • Bug Triage is a process to:
    • Ensure bug report completeness
    • Analyze and move bug to proper component if needed
    • Set Assignee of bug report (via "Assigned to" field) to proper bug owner
    • Assign bug to packages listed in "MeeGo Distribution Packages" product whenever possible (apply for new incoming bug reports for version 1.3 ONLY at this moment)
    • Set appropriate bug priority
    • Adjust bug severity properly (initially set by bug reporter)
    • Resolve obvious invalid, duplication, won’t fix bugs etc.
    • Forward bugs in upstream components to upstream bugtrackers and adding the upstream URL to the URL field of the report, if applicable
  • Bug Triage Team
    • A small team works on bug triage, could be experienced developer, distro engineer or QA
    • Triage team members are expected to contribute significant time to bug triage

Please share your triaging knowledge by adding/editing MeeGo Bug Triage Stock Answers.

Bug Triage Process

  • Triage new incoming bug reports timely by each triage team (from twice a week to daily triage).
  • Triage team members in each triage team could have different focus, such as IA arch bugs, ARM bugs or specific applications etc.
  • Each triage team meet on IRC weekly to discuss controversial bug reports and any open reports
  • Bug assignees accept bug reports by setting target milestones for triaged bug reports
  • Program Managers host bug report scrub meetings to discuss bug reports which do not have a target milestone set

Triage Process Flow as follows:

Bug triage 2.PNG

MeeGo Bug Triage Guide

Check the Triage Guide that explains good practices when triaging bug reports.

MeeGo Bug Triage Team

MeeGo Bug Triage Team Member
MeeGo Core OS Triage Yanshuang Zheng, Jason Zhou, Jarno Teivas, Iekku Huttunen
MeeGo Handset UX Triage Fan Zhao, Cathy Li, Srikanth Yarlagadda, Iekku Huttunen
MeeGo Netbook UX Triage Daniel Tao,Ross Burton
MeeGo Tablet UX Triage Daniel Tao, Lei Yang, Cathy Li
MeeGo IVI Triage Yanshuang Zheng
MeeGo Translation Triage Margie Foster, Patrick McCarty
MeeGo SDK Triage Ionut Gavaz, Jackie Wu, Edmondas Girkantas, Azadeh Karimian, Max Yu, Juha Peisanen
MCTS (MeeGo Core System Testing) Triage Jeff Zheng,Iekku Huttunen

MeeGo Bug Triage Meetings

  • MeeGo Core Bug Triage
    • Time: Every Monday at 07:00 UTC
  • MeeGo Handset Bug Triage
    • Time: Every Wednesday at 07:00 UTC
  • MeeGo Netbook Bug Triage
    • Time: Every Tuesday at 13:00 UTC
  • MeeGo IVI Bug Triage
    • Time: TBD
  • MeeGo Translation Bug Triage
    • Time: TBD
  • MeeGo SDK Bug Triage
    • Time: On demand on Wednesday at 07:00 UTC
  • MCTS Bug Triage
    • Time: Every Wednesday at 08:00 UTC

Those meetings take place in the IRC channel#meego-meeting on irc.freenode.net.

  • MeeGo Tablet Bug Triage

To discuss MeeGo bug triaging at any time feel free to visit the IRC channel #meego-bugs on irc.freenode.net.

Getting involved

Anyone can sign up for the triage team and start helping (see the Triage Guide for information and steps). Just send an email to the meego-qa mailing list to get involved in. Thanks for your contribution to MeeGo!

Other references

Personal tools