I have a bug that will introduce a pref/feature-flag, but that is just one bug that blocks a meta bug. The meta bug covers the whole feature.
Should these flags get set on the meta bug or on the bug that introduces the pref? Testing the specific bug that introduces the pref won't provide much coverage, but setting the flag on the meta bug may be confusing since there will be no patches landed on that bug. I also agree that updating the Trello tracking board is inconvenient (and I also don't know where to find it). Could we just have a Bugzilla query for this information? Thanks, Jared On Thu, May 3, 2018 at 4:45 PM, Jonathan Kew <jfkth...@gmail.com> wrote: > On 03/05/2018 00:57, Emma Humphries wrote: > > To summarize, when you are releasing a feature that "rides behind a flag", >> on the bug for the feature: >> >> * set the behind-pref flag to + >> * set the qa-verify flag to ? >> * note the bug in the Firefox Feature Trello board >> >> We expect qa-verify to be set to + before enabling prefs on features. >> > > I don't see a flag "qa-verify" in bugzilla; was this possibly a typo for > "qe-verify"? > > Thanks, > > JK > _______________________________________________ > firefox-dev mailing list > firefox-...@mozilla.org > https://mail.mozilla.org/listinfo/firefox-dev > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
