Theme: Coming to the end of train-73
A lot of content in yesterday's meeting, so this is a bit longer than
normal.
- Circle based tests have been giving us grief. This seemed to have been
fixed by re-deploying fxa-ci.dev.lcip.org, until last night, possibly
when cron auto-updated the stack.
- Train-73 strings are going to be extracted by vladikoff today. One
auth-mailer PR is outstanding [1], if it's not merged today it'll have to
wait until next train so that we give the localizers the requested 2
weekends to translate.
- We'll cut train-73 early next week, if you have a PR you want merged,
add the shipit label!
- Because a large portion of the team will be in Toronto next week, we
have decided to drop next Monday's Web Coordiantion meeting. Thursday may
also be dropped, we'll decide by Wednesday whether it's needed.
- The Web Coordination meeting format was discussed. We currently have 4
meetings, 2 on Monday, 2 on Thursday.
- Feedback was mixed. Some felt both sets of meetings contained
sufficient high value content to keep. Others questioned whether the
Thursday Web Coordination meeting provided enough value.
- We have decided to keep the format, with some slight modifications.
- If the Monday UX meeting finishes early, triage bugs until the
Ops/General dev meeting starts. If we finish the 2nd meeting
early, we get
out early.
- In the Thursday Web Coordination meeting, if we have triaged half
of the bugs already on Monday, we'll hopefully be able to get out early.
- There are three flaky tests on latest/stage [2]. The two Gmail
failures are caused by rate limiting, the Blocked OAuth test is because of
timing issues - when using a remote connection with latency, we check the
URL before the page has transitioned.
- Instead of using a GMail address to test "Open GMail", Vlad is going
to add restmail.net to the list of providers that have the button.
restmail.net requests are not rate limited on latest.
- I have opened a PR to fix the OAuth test [3].
- Signin unblock
- Proposed SUMO text for "Why is this happening to me?" link [4].
- We are going for 50% rollout to ensure our metrics are in order.
50% was decided instead of 100% so that we can ensure we can correctly
compare the sign-in success rate of users who have the feature enabled vs
users who do not. I read someone signed me up for a cage-match
with Sean as
a result.
- Vijay and Phil have two PRs that will give us significantly
more/better flow metrics for the signup and reset password flows. Vijay's
PR is ready for final review (Phil on the hook), Phil's PR needs updated to
avoid causing an "engaged" event on autofocus, I'm on the hook for review.
- We currently double count the `_complete` screens because they are
displayed in both the "initiating" and "verification" tabs. For example,
for signup, we show "signup_complete" in the tab the user signs up in, as
well as in the tab they verify in. DataDog graphs that use
"signup_complete" are all wrong as a result. [5] tries to fix that by using
distinct screen names for both. Phil is going to review.
Again, next Monday's FxA Web Coordination meeting is cancelled!
Shane
---------------------
[1] - https://github.com/mozilla/fxa-auth-mailer/pull/227
[2] - https://github.com/mozilla/fxa-content-server/issues/4339
[3] - https://github.com/mozilla/fxa-content-server/pull/4341
[4] -
https://docs.google.com/document/d/18haB0ApoqPGJgXZuX2L58tU7DgRUTM2DhvH5PjDP3Q0
[5] - https://github.com/mozilla/fxa-content-server/pull/4306
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct
