Views
Quality/Bugtriage
From MeeGo wiki
< Quality(Difference between revisions)
(linking "Program managers" as per May's private email) |
Ionutgavaz (Talk | contribs) (→MeeGo Bug Triage Meetings) |
||
| (48 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 | + | ** 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 | ** Set appropriate bug priority | ||
** Adjust bug severity properly (initially set by bug reporter) | ** Adjust bug severity properly (initially set by bug reporter) | ||
** Resolve obvious invalid, duplication, won’t fix bugs etc. | ** Resolve obvious invalid, duplication, won’t fix bugs etc. | ||
| + | ** Forward bugs in upstream components to [[Quality/UpstreamBugTrackers | upstream bugtrackers]] and adding the upstream URL to the URL field of the report, if applicable | ||
* Bug Triage Team | * Bug Triage Team | ||
** A small team works on bug triage, could be experienced developer, distro engineer or QA | ** 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 | ** Triage team members are expected to contribute significant time to bug triage | ||
| + | |||
| + | Please share your triaging knowledge by adding/editing [[Quality/Bugtriage_Stock_Answers | MeeGo Bug Triage Stock Answers]]. | ||
== Bug Triage Process == | == Bug Triage Process == | ||
| Line 20: | Line 24: | ||
Triage Process Flow as follows: | Triage Process Flow as follows: | ||
| - | [[File: | + | |
| + | [[File:bug_triage_2.PNG]] | ||
== MeeGo Bug Triage Guide == | == MeeGo Bug Triage Guide == | ||
| - | Check the [ | + | Check the [[Quality/Bugtriage_Guide|Triage Guide]] that explains good practices when triaging bug reports. |
== MeeGo Bug Triage Team == | == MeeGo Bug Triage Team == | ||
| Line 30: | Line 35: | ||
!|Member | !|Member | ||
|- | |- | ||
| - | | MeeGo Core OS Triage || | + | | 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 || | + | | 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/ | + | | MeeGo Netbook UX Triage || Daniel Tao,[http://meego.com/users/rossburton Ross Burton] |
| + | |- | ||
| + | | 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] | ||
|- | |- | ||
| - | | MeeGo Translation Triage || [http://meego.com/users/margie Margie Foster] | + | | MeeGo Translation Triage || [http://meego.com/users/margie Margie Foster], [http://meego.com/users/pmccarty Patrick McCarty] |
|- | |- | ||
| - | | MeeGo SDK Triage || | + | | 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 56: | Line 65: | ||
** Time: TBD | ** Time: TBD | ||
* MeeGo SDK Bug Triage | * MeeGo SDK Bug Triage | ||
| - | ** Time: | + | ** Time: On demand on Wednesday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC] |
| + | * MCTS Bug Triage | ||
| + | ** Time: Every Wednesday at 08:00 [http://www.timeanddate.com/worldclock/converter.html UTC] | ||
Those meetings take place in the IRC channel'''#meego-meeting''' on [http://freenode.net irc.freenode.net]. | Those meetings take place in the IRC channel'''#meego-meeting''' on [http://freenode.net irc.freenode.net]. | ||
| + | |||
| + | * MeeGo Tablet Bug Triage | ||
| + | ** Time: Every Thursday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC] | ||
| + | ** IRC channel '''#meego-meeting2''' on [http://freenode.net irc.freenode.net] | ||
To discuss MeeGo bug triaging at any time feel free to visit the IRC channel '''#meego-bugs''' on [http://freenode.net irc.freenode.net]. | To discuss MeeGo bug triaging at any time feel free to visit the IRC channel '''#meego-bugs''' on [http://freenode.net irc.freenode.net]. | ||
| Line 65: | Line 80: | ||
* [[HandsetBugTriageMinutesArchive|MeeGo Handset Bug Triage Meeting Minutes Archive]] | * [[HandsetBugTriageMinutesArchive|MeeGo Handset Bug Triage Meeting Minutes Archive]] | ||
* [[NetbookBugTriageMinutesArchive|MeeGo Netbook Bug Triage Meeting Minutes Archive]] | * [[NetbookBugTriageMinutesArchive|MeeGo Netbook Bug Triage Meeting Minutes Archive]] | ||
| + | * [[SDKBugTriageMinutesArchive|MeeGo SDK Bug Triage Meeting Minutes Archive]] | ||
=== Getting involved === | === Getting involved === | ||
| - | Anyone can sign up for the triage team and start helping (see the [ | + | Anyone can sign up for the triage team and start helping (see the [[Quality/Bugtriage_Guide|Triage Guide]] for information and steps). Just send an email to the [http://lists.meego.com/listinfo/meego-qa meego-qa mailing list] to get involved in. Thanks for your contribution to MeeGo! |
== Other references == | == Other references == | ||
| - | [ | + | *[[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]] | ||
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:
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
- Time: Every Thursday at 07:00 UTC
- IRC channel #meego-meeting2 on irc.freenode.net
To discuss MeeGo bug triaging at any time feel free to visit the IRC channel #meego-bugs on irc.freenode.net.
- MeeGo Core Bug Triage Meeting Minutes Archive
- MeeGo Handset Bug Triage Meeting Minutes Archive
- MeeGo Netbook Bug Triage Meeting Minutes Archive
- MeeGo SDK Bug Triage Meeting Minutes Archive
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!