Hi All,
This week we shipped FxA train-79 to production, with the following
highlights:
* The "connect another device" experiment will be going live for
50% of production users, and it includes some improvements based
on last train's trial deployment:
* It's now only shown when a user creates a new account, as
it proved a little confusing after a sign-in.
* The status messages shown when opening the link in a non-Firefox
browser have been improved for clarity.
* The "why connect another device" dialog now has a close button
to make it more obvious how to escape from this view.
* Several improved metrics around email deliverability, including
flow events for email bounces, more details about complaints,
and support for ops-level detailed SES event metrics.
* Users can now skip the sign-in confirmation email if they've logged
in previously from the same IP in the last 72 hours; the limit was
previously 24 hours and this made a big difference to our login
success rate, but 72 seems like the sweet spot based on metrics.
* Users who sign in using a different capitalization of their email
address to the one they signed up with, will no longer be double-
penalized in our rate-limiting logic.
* PRs in the auth-server can now be automated integration-tested with
the latest code from other repos, which will hopefully reduce the
change of bustages due to API changes.
* We now log much better diagnostics auth-db-mysql server returns
an error.
* We've reduced the timeout before sending the `login` message on
Firefox for iOS. This is a stopgap to see if we can increase the
successful completion rate for logins on this platform, while work
continues on improving the flow within Firefox itself.
* Many of our links should now work correctly when you right-click
and "open in new tab"; previously this would discard important
query parameters and result in an error.
* There's been a lot of work on getting fxa-content-server running
under Docker, although IIUC it's not quite complete yet.
* The wording of the choose-what-to-sync screen has been simplified
in response to some user confusion uncovered during user testing.
* The oauth and profile servers now have proper cache-control headers.
* The fxa-customs-server can now use CloudSec's IP reputation service
to check for suspicious IPs, although it's disabled by default while
we get some experience with it.
* It's now much harder to accidentally clobber unrelated fxa-customs-
server settings when tweakings its live config via memcache.
As always, you can find more details in the changelogs for each repo:
https://github.com/mozilla/fxa-auth-server/blob/v1.79.0/CHANGELOG.md
https://github.com/mozilla/fxa-auth-mailer/blob/v1.79.0/CHANGELOG.md
https://github.com/mozilla/fxa-content-server/blob/v0.79.3/CHANGELOG.md
https://github.com/mozilla/fxa-oauth-server/blob/v0.79.0/CHANGELOG.md
https://github.com/mozilla/fxa-customs-server/blob/v0.79.0/CHANGELOG.md
https://github.com/mozilla/fxa-profile-server/blob/v0.79.0/CHANGELOG.md
There are also detailed PR metrics included below if you're interested.
Cheers,
Ryan
------------
This train we had a total of 63 PRs and 70 reviews.
That includes work on the following features:
* FxA-107: ip profile logins: 1 PRs (now 15 / 15 = 100% complete)
* FxA-41: signin funnel metrics: 1 PRs (now 70 / 74 = 95% complete)
* FxA-51: Email Push (Phase 1: 3 PRs (now 13 / 15 = 87% complete)
* FxA-56: oauth consolidation: 1 PRs (now 2 / 4 = 50% complete)
* FxA-89: devices view: 2 PRs (now 51 / 56 = 91% complete)
Along with 54 general quality improvements.
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct
