Skip to content
This repository has been archived by the owner on May 10, 2019. It is now read-only.

Merge b2g branch into dev #2982

Closed
jedp opened this issue Jan 31, 2013 · 7 comments
Closed

Merge b2g branch into dev #2982

jedp opened this issue Jan 31, 2013 · 7 comments

Comments

@jedp
Copy link
Contributor

jedp commented Jan 31, 2013

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.

@lloyd
Copy link
Contributor

lloyd commented Jan 31, 2013

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:

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.


Reply to this email directly or view it on GitHub.

@jaredhirsch
Copy link
Member

@jedp do we have a hard date when this needs to be all merged, happy, and
the train deployed?

On Thu, Jan 31, 2013 at 3:18 PM, Lloyd Hilaiel notifications@github.comwrote:

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:

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.


Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHubhttps://github.com//issues/2982#issuecomment-12971971.

@jedp
Copy link
Contributor Author

jedp commented Feb 21, 2013

Well, the closest thing we have to a hard date is the time when FirefoxOS phones hit the market, which will be this summer.

@jedp
Copy link
Contributor Author

jedp commented Feb 28, 2013

Preliminary PR #3059 - still work in progress

@jedp
Copy link
Contributor Author

jedp commented May 2, 2013

So ... close ...

@jaredhirsch
Copy link
Member

@jedp good to close?

@shane-tomlinson
Copy link

Closing

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants