Meego Wiki
Views

Quality/Bugzilla Fields

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(move info unrelated to *reporting* issues from Quality/How_To_Report_Bugs to Quality/Bugzilla_Fields and Quality/Bug_Life_Cycle_and_Handling)
m (add Keywords section)
Line 38: Line 38:
The architecture (like [http://en.wikipedia.org/wiki/Intel_Atom IA], [http://en.wikipedia.org/wiki/ARM_architecture ARM]) the issue has been identified in. For example N900 Base OS layer bugs are ARM, most Netbooks are IA.
The architecture (like [http://en.wikipedia.org/wiki/Intel_Atom IA], [http://en.wikipedia.org/wiki/ARM_architecture ARM]) the issue has been identified in. For example N900 Base OS layer bugs are ARM, most Netbooks are IA.
For bugs which apply for multiple architectures, like bugs for middleware or applications, there is "All".
For bugs which apply for multiple architectures, like bugs for middleware or applications, there is "All".
 +
 +
==Keywords==
=See Also=
=See Also=

Revision as of 08:28, 29 March 2011

Contents

Bugzilla Fields

MeeGo Release

MeeGo Release field defines in which MeeGo version a bug has been found. Version names are defined according to the MeeGo release plan. If a bug was reported already for an older MeeGo version make sure to handle this bug as described here.

Target Milestone

When bugs are in OPEN status, the Target Milestone is used by an experienced bug reporter or by a developer to propose for which future MeeGo release this bug should get fixed. When bugs are in RESOLVED status,the Target Milestone is used to describe in which (existing or upcoming) MeeGo release this bug is fixed.

Importance

Priority

Priority field describes the importance and order in which a bug should be fixed. It helps developers to prioritize their work. By default the priority is set as "Undecided" when reporting a new bug. A bug triage team sets the initial priority for the bug, which might be changed. Priorities range from High (most important) to Low (least important).

  • High: Bug fixing is on-going, or is planned within 2 weeks, no later than the up-coming milestone. Reproducible crash issues, major function loss, issues greatly impact user experience or issues which block other key features to work would fall in to this category.
  • Medium: Bug fixing is planned before project release, but can't start before HIGH priority items are cleaned up.
  • Low: Bug fixing is not planned for the up-coming project release. Will re-evaluate the importance in next release.

Severity

The "Severity" field describes the impact of an issue. The options include:

  • Critical: crashes, other components are affected
  • Major: major loss of own function
  • Normal: regular issue, some loss of functionality under specific circumstances
  • Trival:cosmetic problem like misspelled words or misaligned text
  • Enhancement: request for enhancement

Platform

Hardware

The UX (like Netbook, Nettop, Notebook, Handset, Automotive, TV) the issue has been identified in. For bugs which apply to all UX (like bugs for Middleware/Core components), there is "All".

Architecture

The architecture (like IA, ARM) the issue has been identified in. For example N900 Base OS layer bugs are ARM, most Netbooks are IA. For bugs which apply for multiple architectures, like bugs for middleware or applications, there is "All".

Keywords

See Also

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