(→MeeGo In-Vehicle Infotainment) |
(→MeeGo 1.1 Defects Management) |
||
| Line 23: | Line 23: | ||
=== MeeGo In-Vehicle Infotainment === | === MeeGo In-Vehicle Infotainment === | ||
* [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_IVI_Open&sharer_id=234 '''Open Bugs'''] | * [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_IVI_Open&sharer_id=234 '''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 | ||
Contents |
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: