On Mon, Jun 27, 2016 at 2:26 PM, Cory Price <cpr...@mozilla.com
<mailto:cpr...@mozilla.com>> wrote:
On Mon, Jun 27, 2016 at 11:05 AM, Justin Dolske <dol...@mozilla.com
<mailto:dol...@mozilla.com>> wrote:
What's the policy for reviews and testing with this addon?
You can see the current process for deploying things in the Go
Faster documentation (Wiki
<https://wiki.mozilla.org/Firefox/Go_Faster>, Release Process
<https://docs.google.com/document/d/1x27I7hAmWDWiqk3o3YC3fklhE3N59bdgHCQHF5p_lkU/edit#>).
Thanks, I wasn't aware of the Release Process doc (so I guess I owe an
"Intent to Implement" email to the right lists in the coming weeks).
On 6/27/16 1:45 PM, Benjamin Smedberg wrote:
>
This seems like an inadequate answer to the particular question: who in
particular is the module owner of this code, who is responsible for
doing code review?
How do other go faster addons operate? My naive answer is people on our
team.
> And who is the QA/QE lead for this addon and what
> kind of systems will be used to determine whether a particular webcompat
> tweak is working both before before and after deployment?
If you read the explainer doc, near the end we mention needing automated
testing to verify that patches are needed post-deployment. We've built
similar things in the past for testing "bugfix" regressions. The design
of that is TBD, but our team will build it and monitor it.
One of the requirements of this addon is that it can be (temporarily)
disabled so site owners can verify that they've fixed things. We don't
have dedicated QA resources, so this will likely be a manual process by
our team: turn it off, verify, turn it on, verify, etc.
--
Mike Taylor
Web Compat, Mozilla
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
