Steve, Tim and Herm have been working on the 3.0 plugin breakout,
they've been combing through all the plugins on each of the platforms
and breaking them out.  That being said, I haven't seen this method
used in 2.9.0, so I think we should be OK with this.



On Fri, Jun 28, 2013 at 1:35 PM, Andrew Grieve <[email protected]> wrote:
> Hey Joe,
>
> Who are PBR guys?
>
> What do you think might break?
>
>
> On Fri, Jun 28, 2013 at 4:28 PM, Joe Bowser <[email protected]> wrote:
>
>> Actually, can the PBR guys look at this one? I'm pretty certain that
>> this will break some plugin but now that they're broken out, I don't
>> know which one.
>>
>> On Thu, Jun 27, 2013 at 7:45 PM, Andrew Grieve <[email protected]>
>> wrote:
>> > I just added UriResolvers, but needed to add a public method to
>> > PluginManager that really should be package-private. I'd like to fix this
>> > since it seems easy to do. I've pushed up a branch showing this:
>> >
>> >
>> https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=commitdiff;h=f724df7101c300520b70f944457307d399ec1088
>> >
>> > It:
>> > 1. moves the files from .api up one dir,
>> > 2. Leaves skeletins in .api that extend them
>> > 3. Changes PluginManager.resolveUrl to package private
>> >
>> > I'm fine with holding off deprecating things and privatizing existing
>> > symbols until after 3.0, but I think we should make this change now.
>> >
>> > Joe - looking for your "Ship It". reviewboard couldn't handle the diff
>> for
>> > some reason :(
>> >
>> > I'll wait until after the branch merging to commit this.
>> >
>> >
>> >
>> > On Tue, Jun 25, 2013 at 11:59 AM, Brian LeRoux <[email protected]> wrote:
>> >
>> >> July 19. In the past we've aimed at the last tues of every month.
>> >>
>> >> On Tue, Jun 25, 2013 at 8:34 AM, Marcel Kinard <[email protected]>
>> wrote:
>> >> > Sounds like I missed something. What firm date?
>> >> >
>> >> > On Jun 24, 2013, at 2:04 PM, Joe Bowser <[email protected]> wrote:
>> >> >
>> >> >> Unlike other releases, 3.0 is the only one with a firm date.
>> >> >
>> >>
>>

Reply via email to