MeeGo Defects Management
MeeGo Core
- Open bugs
- Release Blocker
- 1.1 Core Release Blocker
- 1.2 Release Blocker
- 1.3 Release Blocker
MeeGo Handset
- Open Bugs
- Release Blocker
- 1.1 Handset Release blocker
- 1.2 Handset Release Blocker
- 1.3 Handset Release Blocker
MeeGo Tablet
- Tablet Release Blocker
- 1.2 Tablet Release Blocker
- 1.3 Tablet Release Blocker
MeeGo Netbook
- Netbook Open Bugs
- Netbook Release Blocker
- 1.1 Release Blocker
- 1.2 Release Blocker
- 1.3 Release Blocker
MeeGo In-Vehicle Infotainment
- IVI Release Blocker
- 1.1 IVI Release Blocker
- 1.2 IVI Release Blocker
- 1.3 IVI Release Blocker
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