> On Mar 16, 2016, at 4:26 PM, Richard Newman <[email protected]> wrote:
> My tentative proposal for iOS is to ship 3.0 as-is, enabling bidirectional > sync in 4.0 or 5.0 — as soon as we're confident that desktops will eventually > self-recover and our current 50-50 bias will trend towards 100%. I think this > is acceptable; we’ll continue to offer the read-only fallback. The path forward is not clear to me. Our code is finished, so I assume ‘eventually self-recover’ means new Desktop and Android work? * Do we have bugs for that work? * Is that work planned? * Is it estimated? * Do the other teams know what to do and what the problems are? * How long does it take to roll something out to users? * If there is desktop work to do, does that mean 18 weeks at least? * If all this work is done, will things be good, or are there manual ‘recovery’ steps required by our users? I want to understand what exactly needs to be done and what the dependencies are before we can even talk about a specific iOS release where we enable bookmark sync. Do we need a cross-team meeting to figure this out? S.
_______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
