Meego Wiki
Views
From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(MeeGo In-Vehicle Infotainment)
Line 85: Line 85:
* For bugs which are unlikely fixed in any MeeGo release, close them directly by bug owner
* For bugs which are unlikely fixed in any MeeGo release, close them directly by bug owner
* For bugs which are verified fixed on branch only, clone new bugs for next MeeGo release
* For bugs which are verified fixed on branch only, clone new bugs for next MeeGo release
 +
 +
==See Also==
 +
*[[Quality/CoreQualityMetrics | Core Quality Metrics]]
 +
*[[Quality/TabletQualityMetrics | Tablet Quality Metrics]]
 +
*[[Quality/HandsetQualityMetrics | Handset Quality Metrics]]
 +
*[[Quality/IVIQualityMetrics | IVI Quality Metrics]]

Revision as of 04:15, 28 June 2011

Contents

MeeGo Defects Management

MeeGo Core

MeeGo Handset

MeeGo Tablet

  • Tablet Release Blocker
    • 1.2 Tablet Release Blocker
      • Proposed and waiting for reviewed
      • Reviewed and Approved.
    • 1.3 Tablet Release Blocker
      • Proposed and waiting for reviewed
      • Reviewed and Approved.

MeeGo Netbook

  • Netbook Open Bugs
  • Netbook Release Blocker
    • 1.1 Release Blocker
      • Proposed and waiting for reviewed
      • Reviewed and Approved.
    • 1.2 Release Blocker
      • Proposed and waiting for reviewed
      • Reviewed and Approved.
    • 1.3 Release Blocker
      • Proposed and waiting for reviewed
      • Reviewed and Approved.

MeeGo In-Vehicle Infotainment

  • IVI Release Blocker
    • 1.1 IVI Release Blocker
      • Proposed and waiting for review
      • Reviewed and Approved
    • 1.2 IVI Release Blocker
      • Proposed and waiting for review
      • Reviewed and Approved
    • 1.3 IVI Release Blocker
      • Proposed and waiting for review
      • Reviewed and Approved

Bug Cleanup after Project Release

After a MeeGo release, e.g. MeeGo 1.0, MeeGo 1.1, some bugs on this version may still be valid for next MeeGo release. To make sure these valid bugs are well tracked on next MeeGo release, QA will do bug cleanup using following general process:

  • For bugs which will be likely fixed in SW update release, clone new bugs for next MeeGo release
  • For bugs which are unlikely fixed in SW update release, update bug version to next MeeGo release
  • For bugs which are unlikely fixed in any MeeGo release, close them directly by bug owner
  • For bugs which are verified fixed on branch only, clone new bugs for next MeeGo release

See Also

Personal tools