Meego Wiki
Views

Quality/Bugtriage

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(→MeeGo Bug Triage Team)
(→MeeGo Bug Triage Meetings)
Line 56: Line 56:
* MeeGo Netbook Bug Triage
* MeeGo Netbook Bug Triage
** Time: Every Tuesday at 13:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
** Time: Every Tuesday at 13:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
 +
* MeeGo Tablet Bug Triage
 +
** Time: Every Thursday at 7:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MeeGo IVI Bug Triage
* MeeGo IVI Bug Triage
** Time: TBD
** Time: TBD

Revision as of 08:49, 3 May 2011

Contents

Bug Triage Definition

  • Bug Triage is a process to:
    • Ensure bug report completeness
    • Analyze and assign bug to proper component
    • Assign bug to proper bug owner
    • 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 process.jpg

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 Jerry Yu, Peter Zhu, Yanshuang Zheng, Tommi Toropainen, Juhani Taipale, Jarno Teivas, Iekku Huttunen
MeeGo Handset UX Triage Fan Zhao, Cathy Li, Srikanth Yarlagadda,Mika Ikonen, Petri Jylha, Petri Koski, Chris Ferron, Iekku Huttunen
MeeGo Netbook UX Triage Ling Yu, Daniel Tao, Lei Yang, Ross Burton
MeeGo Tablet UX Triage Ling Yu, Daniel Tao, Lei Yang
MeeGo IVI Triage Yanshuang Zheng
MeeGo Translation Triage Margie Foster, Patrick McCarty
MeeGo SDK Triage Juha Peisanen, Ionut Gavaz, Fathi Boudra, Jackie Wu, Max Yu

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 Tablet Bug Triage
    • Time: Every Thursday at 7:00 UTC
  • MeeGo IVI Bug Triage
    • Time: TBD
  • MeeGo Translation Bug Triage
    • Time: TBD
  • MeeGo SDK Bug Triage
    • Time: Every 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

How to report MeeGo bugs?

Retrieved from "http://wiki.meego.com/Quality/Bugtriage"
Personal tools