On 17 May 2017 at 16:29, Ryan Kelly <[email protected]> wrote:
> Based on the above and the items we flagged as P1, here's what will be in
> the everything-went-according-to-plan version of train-88 in two weeks
> time:
>
>
> -
>
> Feature-flagged db support for chaning primary email address.
> -
>
> API support for sending and consuming signin codes in the SMS install
> link.
> -
>
> Support for emojis in device names.
> -
>
> A completed feature doc for the SMS deep-link work.
> -
>
> Finalized protocol and prototype for OAuth key support.
> -
>
> The ability to deploy docker images from private repos.
> -
>
> Working loadtests for the auth-server.
> -
>
> Working verification reminders, after we disable replication on that
> table.
> -
>
> The deeplinking patch landed (or ready to land) for Firefox on iOS.
>
>
> Naturally some things will change over the next two weeks, but I think
> it'll be interesting to sanity-check the above list and then to compare it
> to what actually gets shipped in practice.
>
Now that we're about to cut train-88, I'd love to get your feedback on
whether this "looking forward" train summary email was a useful exercise.
How well does the above list map to the things we're about to ship? Did we
end up prioritizing other things that didn't come up during the planning
session? Did you forget I'd even sent out this list because it was two
whole weeks ago? :-P
Any and all feedback is welcome!
To reiterate, the idea here is not to look at this list and feel bad if we
haven't shipped every single thing on it. Software is hard, priorities
shift, and things come up. The idea is simply to see whether and how we
can extract more value from the planning work we do every cycle, to keep
our top-level priorities moving forward.
So, thoughts?
Cheers,
Ryan
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct
