Re: Back-compat extension #2: clients

> Thanks for getting this done, Richard. Hopefully we can start making use of > this new metadata. I know we could start filing some bugs on our mobile > clients. For Android: Bug 1101344, Bug 1101343. bnicholson, wesj, and stefan were CCed for our other efforts. I’m holding off on filing bug

Re: Back-compat extension #2: clients

Thanks for getting this done, Richard. Hopefully we can start making use of this new metadata. I know we could start filing some bugs on our mobile clients. Finkle - Original Message - > This has landed. Tomorrow’s desktop Nightly will upload richer client > records; Wed or Thur’s An

Re: Back-compat extension #2: clients

This has landed. Tomorrow’s desktop Nightly will upload richer client records; Wed or Thur’s Android Nightly likewise. You’ll see new payload fields: "device": "Nexus 7", "appPackage": "org.mozilla.fennec_rnewman", "id": "enQ9iVZLzRrN", "version": "36.0a1", "name": "Fennec rn

Re: Back-compat extension #2: clients

This is filed as Bug 1097218. An etherpad is here: https://etherpad.mozilla.org/rnewman-client-record Please opine if you have thoughts. -R On 6 Nov 2014, at 1:32 PM, Richard Newman wrote: > (For context, see > ) > > Th

Back-compat extension #2: clients

(For context, see ) The Sync 1.5 clients format is very limited: it essentially includes name and mobile/not mobile, and some version metadata that we included in 1.5 clients. I’d like to make a backwards-compatible extension