Quality/defects

Contents 1 MeeGo Defects Management 1.1 MeeGo Core 1.2 MeeGo Handset 1.3 MeeGo Netbook 1.4 MeeGo In-Vehicle Infotainment 2 Bug Cleanup after Project Release

MeeGo Defects Management

MeeGo Core

• Open bugs
  • 1.1 Open Bugs
  • 1.2 and 1.2.0 Open Bugs
  • 1.3 Open Bugs
• Release Blocker
  • 1.1 Release Blocker
    • Proposed and waiting for review
    • Reviewed and Accepted (Still Open)
    • Reviewed and Rejected
  • 1.2 Release Blocker
    • Proposed and waiting for reviewed
    • Reviewed and Approved.
    • Reviewed and Rejected
  • 1.3 Release Blocker
    • Proposed and waiting for reviewed
    • Reviewed and Approved.
    • Reviewed and Rejected

MeeGo Handset

• Open Bugs
• 1.1 Release Blocker
  • Proposed and waiting for review
  • Reviewed and Accepted (Still Open)
  • Reviewed and Rejected

MeeGo Netbook

• Open Bugs
• 1.1 Release Blocker
  • Proposed and waiting for review
  • Reviewed and Accepted (Still Open)
  • Reviewed and Rejected

MeeGo In-Vehicle Infotainment

• Open Bugs

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