On 6/16/11 7:31 PM, "[email protected]" <[email protected]> wrote:
>Hi Jerry, > >Thanks for the clarification. > >> > - How we can know that bug fix is in the daily/weekly image, after >> > verified in trunk:testing? >> [Jerry] we validate "fixing" in TT but not change the status >> to "verified". "verify" still happen on T as usual. no >> change here. The "validating on TT" effort is only limited to >> "daily build QA team". > >Just asking is the "validating on TT" for release/fix bugs similar as >test for change? Is there dedicate "daily build QA team" to validating >released fix on TT? Yes. > >> For most "released" change, we could expect it >> should be in trunk image in 2 days. (otherwise, it will be >> reopened by daily build QA). Hence for submitters, QA contact >> or any community users who would like to help on bug >> verification, the only thing they may pay attention is to >> leave enough buffer (e.g. released 2 days ago) to have >> released fix propagating from TT to T. > >IMHO, expecting the released change in trunk image in 2 days is not a >obvious indication while the released fix is promoted from TT to T. Will >there any other indication in the bug (e.g. commenting in the bug and >update the target release)besides this? Yes, it usually is good practice for QA or release engineering to make a comment within the bugzilla when changes have hit T or T:T, but this isn't enforced, and sometimes doesn't happen. So best thing is to use the bugzilla flags, and to also check the daily changelogs in the images on what has made it into a certain image. That's what our QA, developers and Release Engineering do for instance And lasty, (Jerry correct me if I'm wrong), but the bug reporter _should_ set the bug to verified/fixed once they verify that the fix has made it all the way to Trunk. See the wiki for the bug cycle: http://wiki.meego.com/Quality/Bug_Life_Cycle_and_Handling Keep in mind that all of these bug statuses are dependent on folks manually changing them, so sometimes, they slip through the cracks (as most manual processes do). Thanks, rs >_______________________________________________ >MeeGo-releases mailing list >[email protected] >http://lists.meego.com/listinfo/meego-releases _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
