Ok so apache wouldn't let me rewrite history, so I've done a giant behemoth of a merge. The jasmine tests still pass so: win?
Anyways, the couple features landed in master recently will likely need to be vetted. This includes some custom config stuff for iOS that Brett from Adobe landed (I will loop back with him on the side) and Jesse's recent windows phone integration. Probably still need lots of eyes on the master branch to make sure all is kosher. Tim and I will keep going with the spec authoring. One thing that I intentionally removed from platform-level `install` was adding <access> tags to the config. I figure this should probably go into `prepare`. Thoughts? On 4/23/13 3:23 PM, "Anis KADRI" <[email protected]> wrote: >Why do you have to delete master? > > >On Tue, Apr 23, 2013 at 3:02 PM, Filip Maj <[email protected]> wrote: > >> Actually, I will be: >> >> - cherry picking recent commits that went into master back into future >> - deleting master on the apache remote >> - pushing up future as the new master >> >> Outstanding tasks are finish tests for blackberry, iOS and common >>project >> handlers, and going over the old node unit tests and seeing if any of >> those are missing from the new jasmine specs. >> >>
