If 46 makes the most sense from an engineering standpoint, it seems to make a lot of sense from a metrics standpoint. We'd continue to support 98% of active users from the last 7 days.
Questions: - Can we easily display a message to pre-56 users to upgrade? (IIUC, we seem to already do it in some cases) - What quantity of work is required to remove support for old browsers? (1 engineer in 2 weeks? 4 weeks? 6 weeks?) - I suppose that the answer of the previous question will influence this one but... Is this work that we want/need to plan for in Q4 OKRs? In our draft Q4 OKRs, we didn't plan to this. We thought Q1 would make sense combined with some performance work. Do we still feel that this makes sense? -- Alex Davis // Mountain View Product Manager // FxA & Sync (415) 769-9247 IRC & Slack: adavis On Mon, Sep 25, 2017 at 9:39 AM, Shane Tomlinson <[email protected]> wrote: > > > On Mon, Sep 25, 2017 at 6:50 AM, Ryan Kelly <[email protected]> wrote: > > >> AFAICT, Firefox used context=fx_desktop_v1 up until Firefox 45 and our >> switch to webchannels in this bug: >> >> https://bugzilla.mozilla.org/show_bug.cgi?id=1218022 >> >> If then used context=fx_desktop_v2 for a while one release, when we >> landed this bug for Firefox 46: >> >> https://bugzilla.mozilla.org/show_bug.cgi?id=1204714 >> >> So IIUC dropping support for those two integrations would disable Fxa >> login on Firefox 45 and earlier, which seems reasonable to me. >> > > fx_desktop_v1 and fx_desktop_v2 are the two that cause the most slowdown. > I'd also like to get rid of fx_firstrun_v1. fx_firstrun_v2 was used > beginning with Firefox 46: > > https://github.com/mozilla/bedrock/pull/3851 > > >> >> That said, I'll note that the fx_ios_v1 broker currently extends >> fx_desktop_v1: >> >> https://github.com/mozilla/fxa-content-server/blob/master/ >> app/scripts/models/auth_brokers/fx-ios-v1.js >> >> So we'll have to double-check that we don't accidentally lose test >> coverage for iOS if we remove the desktop version. >> > > > This also needs to be considered for fx_desktop_v2=>fx_desktop_v3 and > fx_firstrun_v1=>fx_firstrun_v2. I want to speed up development, but not > at the expense of broken supported flows. > > Shane >
_______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
