Nope - you can use this flag for areas that don't have a dedicated QA owner. In the cases where there isn't a dedicated QA, I would flag down the QA lead who is overseeing the release currently (i.e. me for 2.0 & 2.1).
----- Original Message ----- > From: "Kyle Huey" <[email protected]> > To: "Jason Smith" <[email protected]> > Cc: "dev-b2g" <[email protected]>, "dev-gaia" > <[email protected]> > Sent: Tuesday, August 5, 2014 12:56:16 PM > Subject: Re: qa-approval flag for indicating when QA signoff is needed before > landing or uplift > > On Tue, Aug 5, 2014 at 11:34 AM, Jason Smith <[email protected]> wrote: > > Hi Everyone, > > > > QA has added a qa-approval flag to Bugzilla to allow someone to indicate if > > a patch needs QA signoff before landing or uplift. You’ll be able to see > > this flag under the details of a patch. Here are example situations on > > when it would be useful to flag a patch for qa-approval: > > > > Uplift Example > > > > FMD patch lands on trunk. Dev wants uplift to 2.0. Release management > > desires a signoff before uplift, so they flag qa-approval? to the FMD > > tester to provide testing and signoff if testing passes for an uplift or > > not. > > > > Patch Landing Example > > > > Vertical homescreen patch is put out for review, but desires QA testing > > before it lands to ensure that we don’t have smoketest fallouts post > > landing. The dev flags qa-approval? to the vertical homescreen tester to > > provide testing and signoff if testing passes for a landing or not. > > > > Let me know if there are any questions or comments on the flag’s usage. > > > > Sincerely, > > Jason Smith > > _______________________________________________ > > dev-gaia mailing list > > [email protected] > > https://lists.mozilla.org/listinfo/dev-gaia > > Is this only applicable to bugs related to features with a dedicated tester? > > - Kyle > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
