Hi all! It's been a while, Ryan has been sending out the train release emails, I'm going to send out train preview emails.
An easy way to see a full list of GitHub issues we have committed ourselves to for this train is to visit our Waffle board [1] and look at the "in progress", "in review", and "now" columns. Unfortunately, just looking at the Waffle board doesn't provide much high level context. We have several ongoing, multi-train efforts: - *Multi-device metrics* - Do our users use one or more devices? If so, what sorts of devices? Are multi-device users more likely to use Firefox on other devices? - *Retention metrics* - Do our users stay around after the sign up? If so, for how long? If not, when do they start to drop off? Do these users contribute positively to Firefox's use? - *Improved email support* - Our emails had a few conflicting styles, these are being made more consistent. - *Marketing email integration improvements *- We provide users with the ability to sign up to Firefox related marketing emails. We want to make this experience better and open to as many users as possible. - *Integration with Fennec's firstrun flow* - Fennec is replacing their native Firefox Accounts client with the web flow. We are trying to make this as awesome as possible. - *Software Quality* - Any project of this size starts to build technical debt. We try to pay off a little each cycle. Breaking each of these down (includes both issues and outstanding PRs). *Multi-device Metrics* - Use new metrics script to feed FxA metrics dashboards [2] - Test impact of metrics gathering on production traffic [3] - Implement device metrics dashboard [4] *Retention Metrics* - add avatar.get activity event [5][6] - Implement retention graph [7] - Process new retention metrics in a Heka filter [8] *Improved email support* - Add Firefox logo to all emails [9]. - Reduce the amount of HTML in the strings to be translated [10] - Sign in to Sync email subject should include "Firefox Accounts" [11] *Marketing email integration improvements* - Move basket event processing into basket specif repo [12] - Move basket proxy into its own repo [13][14] - Enable marketing email preferences for more users [15][16] *Integration with Fennec's firstrun flow* - Provide an FxA content server internal API for auth brokers to notify a view of what to do "next" (behaviors) [17] - Provide an FxA content server internal API for views to query auth brokers if a feature is supported (capabilities) [18] - Add /signin_completed, /force_auth_completed, and /reset_password_completed screens [19][20] - Choose what to sync screen [21] *Software Quality* - New settings UI header tweaks [22][23] - Speed up the settings panel render [24][25][26][26a] - Password reset functional tests frequently fail because of timing issue [27][28] - Track how long uers remain in the unverified state [29] - All settigns panels report the screen name as `settings` [30] - Drop the whitelisted column in the clients table [31] - The profile server's /1/display_name returns 404 if not set [32] - Implement ability to rotate from old to new keys [33] - Differentiate between firstrun and regular screen views to facilitate better metrics visualizations [34] - OAuth client IDs are being logged as expired [35] That's quite an ambitious list. Will we get it all done? Ryan will tell you once the train goes out. Shane --------------------------- [1] - https://waffle.io/mozilla/fxa [2] - https://github.com/mozilla/fxa-auth-db-mysql/issues/83 [3] - https://github.com/mozilla/fxa-auth-db-mysql/issues/81 [4] - https://github.com/mozilla/fxa-auth-db-mysql/issues/84 [5] - https://github.com/mozilla/fxa-profile-server/pull/147 [6] - https://github.com/mozilla/fxa-profile-server/issues/146 [7] - https://github.com/mozilla/fxa-auth-db-mysql/issues/87 [8] - https://github.com/mozilla/fxa-auth-db-mysql/issues/86 [9] - https://github.com/mozilla/fxa-auth-mailer/issues/62 [10] - https://github.com/mozilla/fxa-auth-mailer/issues/74 [11] - https://github.com/mozilla/fxa-auth-mailer/issues/76 [12] - https://github.com/mozilla/fxa-auth-server/issues/1037 [13] - https://github.com/mozilla/fxa-basket-proxy/pull/2 [14] - https://github.com/mozilla/fxa-content-server/issues/2535 [15] - https://github.com/mozilla/fxa-content-experiments/pull/25 [16] - https://github.com/mozilla/fxa-content-server/issues/2676 [17] - https://github.com/mozilla/fxa-content-server/pull/3097 [18] - https://github.com/mozilla/fxa-content-server/pull/3077 [19] - https://github.com/mozilla/fxa-content-server/issues/2771 [20] - https://github.com/mozilla/fxa-content-server/pull/3094 [21] - https://github.com/mozilla/fxa-content-server/issues/3080 [22] - https://github.com/mozilla/fxa-content-server/issues/3055 [23] - https://github.com/mozilla/fxa-content-server/issues/3089 [24] - https://github.com/mozilla/fxa-content-server/issues/3061 [25] - https://github.com/mozilla/fxa-content-server/pull/3088 [26] - https://github.com/mozilla/fxa-content-server/pull/3092 [26a] - https://github.com/mozilla/fxa-content-server/issues/3053 [27] - https://github.com/mozilla/fxa-content-server/issues/2483 [28] - https://github.com/mozilla/fxa-content-server/pull/3083 [29] - https://github.com/mozilla/fxa-content-server/issues/3046 [30] - https://github.com/mozilla/fxa-content-server/issues/3029 [31] - https://github.com/mozilla/fxa-oauth-server/issues/267 [32] - https://github.com/mozilla/fxa-profile-server/issues/144 [33] - https://github.com/mozilla/fxa-auth-server/issues/1025 [34] - https://github.com/mozilla/fxa-content-server/issues/3002 [35] - https://github.com/mozilla/fxa-oauth-server/issues/324
_______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
