Merge b2g branch into dev #2982
Comments
Is there any creative way we can make this transparent to rps? Isn't this analogous to the browserid-> persona transition? -- lloyd (thumb-typing) On Jan 31, 2013, at 3:34 PM, Jed Parsons notifications@github.com wrote:
|
@jedp do we have a hard date when this needs to be all merged, happy, and On Thu, Jan 31, 2013 at 3:18 PM, Lloyd Hilaiel notifications@github.comwrote:
|
Well, the closest thing we have to a hard date is the time when FirefoxOS phones hit the market, which will be this summer. |
Preliminary PR #3059 - still work in progress |
So ... close ... |
@jedp good to close? |
Closing |
The work done to support marketplace and native implementations (b2g) should be merged into dev.
Once this is done, we can rejoice, as all users will share a single database, and RPs will not need to know in advance whether they are serving native or shimmed; they will only need to include js from persona.org.
This needs to happen before the final b2g code is shipped to vendors to put on phones that go to market. I think we should plan on anticipating this date by about a month to allow for stress-free QA, staging, and deployment.
Bug 836928 tracks this on the bugzilla side.
The text was updated successfully, but these errors were encountered: