Re: Should FxA remove support for old browser integrations?
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 Tomlinsonwrote: > > > On Mon, Sep 25, 2017 at 6:50 AM, Ryan Kelly 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 Dev-fxacct@mozilla.org https://mail.mozilla.org/listinfo/dev-fxacct
Re: Should FxA remove support for old browser integrations?
On Mon, Sep 25, 2017 at 6:50 AM, Ryan Kellywrote: > 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 Dev-fxacct@mozilla.org https://mail.mozilla.org/listinfo/dev-fxacct
FxA Web Coordination agenda for Sept 25th, 2017
*Today's Theme: Train-96 deploy, the last full week of the quarter.* Since it's a Monday, it's the long meeting. 30 mins UX/PM, 30 mins Ops/Dev. https://public.etherpad-mozilla.org/p/fxa-engineering-coordination Shane ___ Dev-fxacct mailing list Dev-fxacct@mozilla.org https://mail.mozilla.org/listinfo/dev-fxacct
meeting reminder: Q3 retrospective
Hi All, It's the last Monday of Q3, which means we have a special edition of our usual Monday meetings coming up. We'll kick off at 12:30 Pacific with our usual Show & Tell session, so if you've got something to share as we bring the quarter to a close, please sign up in the etherpad: https://public.etherpad-mozilla.org/p/fxa-engineering-coordination Then at 13:00 Pacific, we'll use our standing Retrospective timeslot to retrospect on Q3 as a whole. We'll start by scoring the Q3 OKRs, which should hopefully be quick and painless since we've been keeping confidence updated throughout the quarter: https://docs.google.com/document/d/1lM0XGpLcR8WXjEBYjjd7xArT66A1WiPQi-QHVaV59Ds/ Then we can dive into the what-went-well, the what-could-we-improve, and the what-to-try-for-next-time as we set ourselves up for Q4. See you there! Cheers, Ryan ___ Dev-fxacct mailing list Dev-fxacct@mozilla.org https://mail.mozilla.org/listinfo/dev-fxacct