On 6/17/2011 10:31 AM, [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?
It's exactly the "test for changes" we're doing for TT every day. Hence
your team is exactly part of this effort already. :)
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?
Emm. Probably it's not practical to add extra state for this change. If
that's the case, release eng has to come back to touch each bug twice to
change the status in Bugzilla. (dev->TT, TT->T). The reality is most of
changes should fall into scenario "promote TT->T in 2 days after it's
released". Otherwise it will be a problem of the release process. Let's
see how the data tells that later. And revisit the process if the data
shows it's not true. Make sense?
----------------------------------------------------------------
Please note: This e-mail may contain confidential information
intended solely for the addressee. If you have received this
e-mail in error, please do not disclose it to anyone, notify
the sender promptly, and delete the message from your system.
Thank you.
_______________________________________________
MeeGo-qa mailing list
[email protected]
http://lists.meego.com/listinfo/meego-qa
