The answer was focused on the policy question which should be covered for the most part in the documentation. With respect to individual roles and responsibilities for this add-on, I've added it to the agenda in the aforementioned team check-in.
On Mon, Jun 27, 2016 at 11:45 AM, Benjamin Smedberg <bsmedb...@mozilla.com> wrote: > > On Mon, Jun 27, 2016 at 2:26 PM, Cory Price <cpr...@mozilla.com> wrote: > >> >> On Mon, Jun 27, 2016 at 11:05 AM, Justin Dolske <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#> >> ). >> >> I've also added this to our system add-on pipeline >> <https://trello.com/b/moJCpVCD/go-faster-system-add-on-pipeline> which >> we discuss in our weekly meetings (invited Mike/Justin). >> > > 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? 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? > > --BDS > > -- > Benjamin Smedberg > Engineering Manager, Firefox > > -- Cory Price /ckprice _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
