You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Darryl Pogue <dv...@gmail.com> on 2015/02/03 20:46:33 UTC
Re: [DISCUSS] Cordova-Android 4.0.0 Release
I just remembered that there should be a plugins release before
Android 4.0.0 goes out because of the moving of the splashscreen logic
out of the platform and into the plugin. As far as I can tell, that's
still unreleased.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Michal Mocny <mm...@chromium.org>.
And docs, I think.
On Mon, Mar 2, 2015 at 4:37 PM, Joe Bowser <bo...@gmail.com> wrote:
> So, right now the whitelist changes are what's holding up the 4.0.0 release
> now? Is this really the only thing that's holding up this release?
>
> On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve <ag...@chromium.org>
> wrote:
>
> > I think we'll also need to finish with the whitelist changes & have both
> > the legacy and new-way whitelist plugins released before we can do a
> 4.0.0
> > release (otherwise you wouldn't be able to write an app that hits the
> > network)
> >
> > On Wed, Feb 25, 2015 at 12:41 PM, Andrew Grieve <ag...@chromium.org>
> > wrote:
> >
> > > Alright, branch is merged in and I fixed a couple other things I
> noticed
> > > broken in the native test app (back button & background color). I've
> also
> > > gone ahead with removing the LinearLayout and confirmed that both maps
> > and
> > > nativepagetransitions plugins are not affected at all.
> > >
> > > Might as well add in the key signing tweaks that have been agreed
> upon. I
> > > can do that today.
> > >
> > > Would like your input on:
> > > Deprecated show/hide customView
> > > - At first I thought this was just view twiddling for video on old
> > > androids that was not meant to be exposed
> > > - I see now though that there is custom back button logic for it
> > > - and that the maps plugin uses it to go fullscreen
> > > - so I'm thinking let's not deprecate.
> > >
> > > We're also still waiting for a tools release to happen that will set
> > 3.7.1
> > > as the default platform (don't have cycles to do it this week myself)
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Tue, Feb 24, 2015 at 7:39 PM, Joe Bowser <bo...@gmail.com> wrote:
> > >
> > >> I can't come up with any. Let's not delay the release on that. So,
> > other
> > >> than the platform docs, we should be good to go, right?
> > >>
> > >> On Thu Feb 19 2015 at 11:42:40 AM Andrew Grieve <agrieve@chromium.org
> >
> > >> wrote:
> > >>
> > >> > Thanks for the quick review. I'll have a look through your comments.
> > >> Now's
> > >> > a good time to change names, so feel free to suggest alternatives.
> > >> >
> > >> > On Thu, Feb 19, 2015 at 1:32 PM, Joe Bowser <bo...@gmail.com>
> > wrote:
> > >> >
> > >> > > I've done a quick read of the pull request and left some comments
> in
> > >> > > there. I'm in Salt Lake this week, so I haven't had a chance to
> > >> really
> > >> > > test this pull request yet, but while I'm not in love with the
> > naming
> > >> > > convention used, it looks mostly OK.
> > >> > >
> > >> > > On Thu Feb 19 2015 at 11:19:51 AM Andrew Grieve <
> > agrieve@chromium.org
> > >> >
> > >> > > wrote:
> > >> > >
> > >> > > > They would need to do similar to the PR for xwalk. It's
> actually a
> > >> lot
> > >> > > less
> > >> > > > code now to implement a custom engine, so I think it makes
> > geckoview
> > >> > much
> > >> > > > more feasible.
> > >> > > >
> > >> > > > The embedded case (I'm guessing you mean layout xml?) is one of
> > the
> > >> > unit
> > >> > > > tests. Have a look here:
> > >> > > > https://github.com/agrieve/cordova-android/blob/engine/
> > >> > > > test/src/org/apache/cordova/test/CordovaWebViewTestActivity.java
> > >> > > >
> > >> > > > If we delete LinearLayout, we just pass the WebView itself to
> > >> > > > setContentView(). It will still have a FrameLayout as a parent
> > >> (which
> > >> > is
> > >> > > > the unchangeable root View of all Activities)
> > >> > > >
> > >> > > > For reference, here's now NativePageTransitions inserts their
> own
> > >> > Layout:
> > >> > > > https://github.com/Telerik-Verified-Plugins/
> > >> > NativePageTransitions/blob/
> > >> > > > master/src/android/NativePageTransitions.java#L74
> > >> > > >
> > >> > > > On Thu, Feb 19, 2015 at 1:01 PM, Joe Bowser <bo...@gmail.com>
> > >> wrote:
> > >> > > >
> > >> > > > > So, I know that XWalk is the only production-ready WebView
> right
> > >> now,
> > >> > > but
> > >> > > > > what would other third party providers need to
> implement/change
> > >> for
> > >> > > their
> > >> > > > > webviews to work? Also, I'm not clear how the embedded
> > >> CordovaWebView
> > >> > > use
> > >> > > > > case would work in this scenario. If we delete the
> > LinearLayout,
> > >> > what
> > >> > > do
> > >> > > > > we attach our view for the default use case?
> > >> > > > >
> > >> > > > > On Thu Feb 19 2015 at 10:39:59 AM Andrew Grieve <
> > >> > agrieve@chromium.org>
> > >> > > > > wrote:
> > >> > > > >
> > >> > > > > > I've finished playing with third-party plugins. If anyone
> else
> > >> > wants
> > >> > > to
> > >> > > > > > have fun with them, use --thirdpartyplugins in
> > >> createmobilespec.js,
> > >> > > and
> > >> > > > > > then find the manual test for them.
> > >> > > > > >
> > >> > > > > > TLDR - most compiled/worked fine. Two that interacted with
> > >> Views a
> > >> > > lot
> > >> > > > > had
> > >> > > > > > lots of compile errors, but in the end I don't think
> there's a
> > >> good
> > >> > > way
> > >> > > > > to
> > >> > > > > > fix them on our end.
> > >> > > > > >
> > >> > > > > > I've also taken some time to try and eliminate copy & paste
> > >> between
> > >> > > > > > AndroidWebView and XWalkWebView. I'd love to get some
> feedback
> > >> on
> > >> > the
> > >> > > > > > changes (and hopefully get them in). More info /w PRs here:
> > >> > > > > >
> > >> > > > > > https://issues.apache.org/jira/browse/CB-8510
> > >> > > > > >
> > >> > > > > > Another thing that came out of looking at these plugins is
> > that
> > >> > they
> > >> > > > add
> > >> > > > > in
> > >> > > > > > their own Layout, or have logic to handle various parent
> > layout.
> > >> > > So...
> > >> > > > I
> > >> > > > > > think we'd be fine (and should) delete our top-level
> > >> LinearLayout.
> > >> > > > > Plugins
> > >> > > > > > and embedders can easily add in layouts if they want.
> > >> > > > > >
> > >> > > > > > Still waiting on a tools release for 3.7.1.
> > >> > > > > > Still need to update platform docs for 4.0.0
> > >> > > > > >
> > >> > > > > > But... I think that's it! (unless I'm missing something)
> > >> > > > > >
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > On Wed, Feb 4, 2015 at 10:11 PM, Ian Clelland <
> > >> > > iclelland@chromium.org>
> > >> > > > > > wrote:
> > >> > > > > >
> > >> > > > > > > On Wed, Feb 4, 2015 at 7:58 PM, Fu, Junwei <
> > >> junwei.fu@intel.com>
> > >> > > > > wrote:
> > >> > > > > > >
> > >> > > > > > > > What are the test cases don't work for Crosswalk? I'd
> like
> > >> to
> > >> > do
> > >> > > > > > whatever
> > >> > > > > > > > I can to help.
> > >> > > > > > > >
> > >> > > > > > >
> > >> > > > > > > So, Crosswalk 10 (and, I believe, 11) work great for
> > Cordova.
> > >> > There
> > >> > > > is
> > >> > > > > a
> > >> > > > > > > failing test in File Transfer, though, that appears to be
> a
> > >> > > threading
> > >> > > > > > issue
> > >> > > > > > > causing a NPE deep inside of OkHTTP.
> > >> > > > > > >
> > >> > > > > > > It's very similar to a bug we solved almost a year ago:
> > >> > > > > > > https://issues.apache.org/jira/browse/CB-6378, except
> that
> > >> it's
> > >> > > > > > happening
> > >> > > > > > > in a different method, and while the last time, the cause
> > was
> > >> > > obvious
> > >> > > > > > > (connections opened on one thread, and closed on another),
> > >> this
> > >> > > time
> > >> > > > > > > everything *should* be happening on the same thread.
> > >> > > > > > >
> > >> > > > > > > I've just created
> > >> https://issues.apache.org/jira/browse/CB-8431
> > >> > if
> > >> > > > you
> > >> > > > > > > want
> > >> > > > > > > to take a look. I haven't had the chance to really dig
> into
> > >> where
> > >> > > the
> > >> > > > > > error
> > >> > > > > > > is coming from yet, but I'll take a closer look tomorrow.
> > >> > > > > > >
> > >> > > > > > > Ian
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > > > >
> > >> > > > > > > > -----Original Message-----
> > >> > > > > > > > From: agrieve@google.com [mailto:agrieve@google.com] On
> > >> Behalf
> > >> > > Of
> > >> > > > > > Andrew
> > >> > > > > > > > Grieve
> > >> > > > > > > > Sent: Thursday, February 05, 2015 3:43 AM
> > >> > > > > > > > To: dev
> > >> > > > > > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > >> > > > > > > >
> > >> > > > > > > > On Wed, Feb 4, 2015 at 2:25 PM, Joe Bowser <
> > >> bowserj@gmail.com>
> > >> > > > > wrote:
> > >> > > > > > > >
> > >> > > > > > > > > OK, so since we're using e-mail to do a sprint, here's
> > >> where
> > >> > I
> > >> > > > > think
> > >> > > > > > > > > we're at so far.
> > >> > > > > > > > >
> > >> > > > > > > > >
> > >> > > > > > > > > - Ian's been working on getting crosswalk 10 working
> and
> > >> is
> > >> > > > hitting
> > >> > > > > > > > > some FileTransfer crash issues.
> > >> > > > > > > > > (Apparently Crosswalk-11 works? Ian, what's happening
> > with
> > >> > > this?)
> > >> > > > > > > > > - Mobilespec really should be passing, let's
> investigate
> > >> and
> > >> > > fix
> > >> > > > > > > > > plugins / tests if they are the issues.
> > >> > > > > > > > >
> > >> > > > > > > > > Has anyone done this yet?
> > >> > > > > > > > >
> > >> > > > > > > > Don't think so.
> > >> > > > > > > >
> > >> > > > > > > > >
> > >> > > > > > > > > - Android's update script is not preserving artifacts
> of
> > >> > > > <framework
> > >> > > > > > > > > type="gradleReference"/> (hoping to work on this
> today)
> > >> > > > > > > > >
> > >> > > > > > > > > Did you get around to doing this?
> > >> > > > > > > > >
> > >> > > > > > > > Done!
> > >> > > > > > > >
> > >> > > > > > > > >
> > >> > > > > > > > > - *LinearLayoutSoftKeyboardDetect - delete it!*
> > >> > > > > > > > >
> > >> > > > > > > > > It's apparently already gone on Master.
> > >> > > > > > > > >
> > >> > > > > > > > Done!
> > >> > > > > > > >
> > >> > > > > > > > >
> > >> > > > > > > > > - Ensure that our gradle support is to the point where
> > >> > plugins
> > >> > > > can
> > >> > > > > > > > > target android-sdk-provided libs (play services &
> > -compat
> > >> > libs)
> > >> > > > > > > > >
> > >> > > > > > > > > What needs to be done here? Is there a JIRA issue for
> > >> this?
> > >> > > > > > > > >
> > >> > > > > > > > Done! Needs a tools release.
> > >> > > > > > > > Haven't tested how bad the error messages are if you
> don't
> > >> have
> > >> > > > them
> > >> > > > > > > > installed though. That seems like a can-be-done-after
> > thing
> > >> > (e.g.
> > >> > > > If
> > >> > > > > > the
> > >> > > > > > > > error message sucks, we could: before build, pre-scan
> for
> > >> > > existence
> > >> > > > > of
> > >> > > > > > > them
> > >> > > > > > > > in the SDK directly.)
> > >> > > > > > > >
> > >> > > > > > > > >
> > >> > > > > > > > > - Make CordovaActivity not implement CordovaInterface,
> > but
> > >> > > > instead
> > >> > > > > > > > > provide CordovaInterface via an inner class (to
> solidify
> > >> that
> > >> > > you
> > >> > > > > > > > > can't cast the activity to CordovaInterface and expect
> > >> that
> > >> > to
> > >> > > > > work -
> > >> > > > > > > > > some used to do this but I think we've cleaned it all
> up
> > >> now)
> > >> > > > > > > > >
> > >> > > > > > > > done!
> > >> > > > > > > >
> > >> > > > > > > >
> > >> > > > > > > > >
> > >> > > > > > > > > I know there's a vote pending for 3.7.1, and we still
> > need
> > >> > > people
> > >> > > > > to
> > >> > > > > > > > > vote on that (I'll get around to it before the voting
> > >> period
> > >> > > > ends),
> > >> > > > > > > > > but I'm wondering how close we are to getting a 4.0.0
> > vote
> > >> > > > > happening?
> > >> > > > > > > > >
> > >> > > > > > > >
> > >> > > > > > > > I'd like to do a bit more work with playing with third
> > party
> > >> > > > plugins
> > >> > > > > in
> > >> > > > > > > > mobilespec before we vote to release. Right now many of
> > them
> > >> > > don't
> > >> > > > > > > compile,
> > >> > > > > > > > and I think the main reason is that CordovaWebView is
> not
> > a
> > >> > view.
> > >> > > > > > > Planning
> > >> > > > > > > > on writing up a report of how many popular plugins
> break,
> > >> and
> > >> > how
> > >> > > > bad
> > >> > > > > > it
> > >> > > > > > > is
> > >> > > > > > > > to fix them.
> > >> > > > > > > >
> > >> > > > > > > > Also need to update embedder's guide in docs (maybe
> create
> > >> an
> > >> > > > > > > android-4.0.0
> > >> > > > > > > > branch?)
> > >> > > > > > > > Also need to do a plugins release for splashscreen (will
> > >> start
> > >> > > > > > shortly).
> > >> > > > > > > >
> > >> > > > > > > >
> > >> > > > > > > > >
> > >> > > > > > > > >
> > >> > > > > > > > >
> > >> > > > > > > > > On Tue Feb 03 2015 at 7:20:29 PM Fu, Junwei <
> > >> > > junwei.fu@intel.com
> > >> > > > >
> > >> > > > > > > wrote:
> > >> > > > > > > > >
> > >> > > > > > > > > > Crosswalk engine have been tested in mobile-spec and
> > >> owned
> > >> > > > > > > > > > functionality tests with Crosswalk-11, and it was
> our
> > >> plan
> > >> > to
> > >> > > > be
> > >> > > > > > > > > > released. I request a PR in here
> > >> > > > > > > > > > https://github.com/MobileChromeApps/cordova-
> > >> > > > > > > > > > crosswalk-engine/pull/17.
> > >> > > > > > > > > >
> > >> > > > > > > > > > Thanks,
> > >> > > > > > > > > > Junwei.
> > >> > > > > > > > > >
> > >> > > > > > > > > > -----Original Message-----
> > >> > > > > > > > > > From: agrieve@google.com [mailto:agrieve@google.com
> ]
> > On
> > >> > > Behalf
> > >> > > > > Of
> > >> > > > > > > > > > Andrew Grieve
> > >> > > > > > > > > > Sent: Wednesday, February 04, 2015 3:53 AM
> > >> > > > > > > > > > To: dev
> > >> > > > > > > > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > >> > > > > > > > > >
> > >> > > > > > > > > > And, of course, for your FileTransfer change :P
> > >> > > > > > > > > >
> > >> > > > > > > > > > I just last night finished up the fixing of
> <framework
> > >> > > > > > custom=false>
> > >> > > > > > > > > > for gradle-based builds, so we're certainly nearing
> > the
> > >> > > finish
> > >> > > > > line
> > >> > > > > > > > > > for 4.0.0 known issues.
> > >> > > > > > > > > >
> > >> > > > > > > > > > Of the list from before, only remaining are:
> > >> > > > > > > > > >
> > >> > > > > > > > > > - Ian's been working on getting crosswalk 10 working
> > >> and is
> > >> > > > > hitting
> > >> > > > > > > > > > some FileTransfer crash issues.
> > >> > > > > > > > > > - Mobilespec really should be passing, let's
> > investigate
> > >> > and
> > >> > > > fix
> > >> > > > > > > > > > plugins
> > >> > > > > > > > > /
> > >> > > > > > > > > > tests if they are the issues.
> > >> > > > > > > > > >
> > >> > > > > > > > > >
> > >> > > > > > > > > >
> > >> > > > > > > > > >
> > >> > > > > > > > > > On Tue, Feb 3, 2015 at 2:46 PM, Darryl Pogue <
> > >> > > > > dvpdiner2@gmail.com>
> > >> > > > > > > > > wrote:
> > >> > > > > > > > > >
> > >> > > > > > > > > > > I just remembered that there should be a plugins
> > >> release
> > >> > > > before
> > >> > > > > > > > > > > Android 4.0.0 goes out because of the moving of
> the
> > >> > > > > splashscreen
> > >> > > > > > > > > > > logic out of the platform and into the plugin. As
> > far
> > >> as
> > >> > I
> > >> > > > can
> > >> > > > > > > > > > > tell, that's still unreleased.
> > >> > > > > > > > > > >
> > >> > > > > > > > > > >
> > >> > > ------------------------------------------------------------
> > >> > > > > > ------
> > >> > > > > > > > > > > --- To unsubscribe, e-mail:
> dev-unsubscribe@cordova.
> > >> > > > apache.org
> > >> > > > > > > > > > > For additional commands, e-mail:
> > >> > > dev-help@cordova.apache.org
> > >> > > > > > > > > > >
> > >> > > > > > > > > > >
> > >> > > > > > > > > >
> > >> > > > > > > > > > ------------------------------
> > >> > ------------------------------
> > >> > > > > > --------
> > >> > > > > > > > > > - To unsubscribe, e-mail: dev-unsubscribe@cordova.
> > >> > apache.org
> > >> > > > > > > > > > For additional commands, e-mail:
> > >> > dev-help@cordova.apache.org
> > >> > > > > > > > > >
> > >> > > > > > > > >
> > >> > > > > > > >
> > >> > > > > > >
> > >> > > > > >
> > >> > > > >
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >
> > >
> >
>
RE: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by "Treggiari, Leo" <le...@intel.com>.
You may have seen this before (deja-vu).
If this is not the correct place for this, sorry that my focus is not
on following a strict release process but rather releasing a good
product.
Having read the proposed whitelist release notes, I have the following
additional question:
Based upon my understanding, which must be wrong!
The 4.0.0 Android Release will require the cordova-plugin-whitelist in order
to get a whitelist implemented correctly.
Given its name (dash-style) it is only available as an node component.
The is no released CLI that knows how to fetch from npm?
Or does 4.3, even though I don't see it in the release notes?
Even so, there are many previous CLI releases which will not work?
It would be good for the release notes to explain the situation.
Leo
-----Original Message-----
From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of Andrew Grieve
Sent: Wednesday, April 08, 2015 7:08 PM
To: Andrew Grieve
Cc: dev; Homer, Tony
Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
CB-8684 is now merged and I've updated the targetSdk (and made a couple
other changes).
I'll start the release process in the morning as long as there no
objections.
On Tue, Apr 7, 2015 at 2:20 PM, Andrew Grieve <ag...@chromium.org> wrote:
> I'll start on it once CB-8684 lands (Tony - assuming you'll have this done
> shortly and would prefer it lands?)
>
> On Tue, Apr 7, 2015 at 1:33 PM, Jesse <pu...@gmail.com> wrote:
>
>> Sweet!
>>
>> @purplecabbage
>> risingj.com
>>
>> On Tue, Apr 7, 2015 at 8:35 AM, Andrew Grieve <ag...@chromium.org>
>> wrote:
>>
>> > Let's do it!
>> >
>> > On Mon, Apr 6, 2015 at 7:33 PM, Joe Bowser <bo...@gmail.com> wrote:
>> >
>> > > So, I think we should put off the embedder's guide until after the
>> > > release. A lot of it has changed, and since we're still technically
>> > > obligated to support the 3.x release tree for six months, that should
>> buy
>> > > us some time to figure out how that is going to work. Getting
>> Cordova to
>> > > work with a vanilla Android Studio project is a non-trivial task.
>> > >
>> > > Given that everything else appears to be done, should we start voting
>> on
>> > an
>> > > RC for this? What do people think?
>> > >
>> > >
>> > >
>> > > On Thu, Mar 19, 2015 at 10:31 AM Andrew Grieve <ag...@chromium.org>
>> > > wrote:
>> > >
>> > > > Here's issues:
>> > > > https://issues.apache.org/jira/browse/CB-8715 (docs)
>> > > > https://issues.apache.org/jira/browse/CB-8716 (whitelist)
>> > > > https://issues.apache.org/jira/browse/CB-8717 (write
>> RELEASENOTES.md)
>> > > >
>> > > > On Tue, Mar 17, 2015 at 10:15 AM, Carlos Santana <
>> csantana23@gmail.com
>> > >
>> > > > wrote:
>> > > >
>> > > > > I would say let's start RC testing and voting, But not pin the
>> > version
>> > > in
>> > > > > Cordova CLI until the tasks that Andrew mentioned are done.
>> > > > > Andrew can you create the JIRA Items for the tasks that need to be
>> > > done.
>> > > > I
>> > > > > thought there was a discussion about creating JIRA Items to help
>> > track
>> > > > and
>> > > > > know what's left for release something.
>> > > > >
>> > > > > - upgrade guide,
>> > > > > - publishing whitelist plugins,
>> > > > > - and making it so that the default project template includes
>> <plugin
>> > > > > name="cordova-plugin-whitelist" />)
>> > > > >
>> > > > >
>> > > > > On Mon, Mar 16, 2015 at 11:21 PM, Ian Clelland <
>> > iclelland@chromium.org
>> > > >
>> > > > > wrote:
>> > > > >
>> > > > > > We'll probably need at least an RC for the whitelist plugin, if
>> > not a
>> > > > > vote,
>> > > > > > to be able to vote on this.
>> > > > > >
>> > > > > > Or can we just include instructions like "Use
>> > > > > > cordova-plugin-whitelist@f70b1bc for testing" while we start
>> the
>> > > > > official
>> > > > > > release process for the plugins?
>> > > > > >
>> > > > > > On Mon, Mar 16, 2015 at 11:17 PM, Ian Clelland <
>> > > iclelland@chromium.org
>> > > > >
>> > > > > > wrote:
>> > > > > >
>> > > > > > > +1 -- Let's get this out the door :)
>> > > > > > > I'll see what I can get done to move it in that direction.
>> > > > > > >
>> > > > > > > On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <
>> > > agrieve@chromium.org
>> > > > >
>> > > > > > > wrote:
>> > > > > > >
>> > > > > > >> Everything's ready afaik (minus upgrade guide, publishing
>> > > whitelist
>> > > > > > >> plugins, and making it so that the default project template
>> > > includes
>> > > > > > >> <plugin name="cordova-plugin-whitelist" />). Maybe let's do
>> a RC
>> > > > while
>> > > > > > we
>> > > > > > >> wait on these things being finished up?
>> > > > > > >>
>> > > > > > >> If anyone wants to take on any of these tasks, that would be
>> > > > awesome.
>> > > > > > >>
>> > > > > > >> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <sh...@gmail.com>
>> > > wrote:
>> > > > > > >>
>> > > > > > >> > +1 for vote thread, let's get this thing out so people
>> (that
>> > are
>> > > > not
>> > > > > > >> > us) can test...
>> > > > > > >> >
>> > > > > > >> >
>> > > > > > >> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <
>> > bowserj@gmail.com>
>> > > > > > wrote:
>> > > > > > >> > > OK, this is a three month old thread, and we're waiting
>> on a
>> > > > > > >> discussion
>> > > > > > >> > > before we release something? I really think we should go
>> to
>> > a
>> > > > vote
>> > > > > > >> thread
>> > > > > > >> > > now that we have a legacy whitelist plugin and a new
>> style
>> > > > > whitelist
>> > > > > > >> > > plugin. We shouldn't keep constantly delaying this
>> release
>> > > > > because
>> > > > > > of
>> > > > > > >> > > what's happening on other platforms, especially since we
>> > > already
>> > > > > > >> > pluginized
>> > > > > > >> > > the whitelist.
>> > > > > > >> > >
>> > > > > > >> > > Can we please release soon?
>> > > > > > >> > >
>> > > > > > >> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil Khandelwal <
>> > > > > > >> > nikhilkh@microsoft.com>
>> > > > > > >> > > wrote:
>> > > > > > >> > >
>> > > > > > >> > >> I know we discussed a couple of approaches implementing
>> the
>> > > > > default
>> > > > > > >> > >> whitelist policy for Android/iOS - either every app
>> would
>> > be
>> > > > > > >> required to
>> > > > > > >> > >> include the whitelist plugin or have it have smart
>> defaults
>> > > in
>> > > > > the
>> > > > > > >> > platform
>> > > > > > >> > >> implementation and the plugin being able to override
>> them.
>> > > > > > >> > >>
>> > > > > > >> > >> I don’t think that thread closed with any conclusions.
>> > > > > > >> > >>
>> > > > > > >> > >> Thanks,
>> > > > > > >> > >> Nikhil
>> > > > > > >> > >>
>> > > > > > >> > >>
>> > > > > > >> > >> -----Original Message-----
>> > > > > > >> > >> From: Joe Bowser [mailto:bowserj@gmail.com]
>> > > > > > >> > >> Sent: Thursday, March 12, 2015 11:23 AM
>> > > > > > >> > >> To: dev
>> > > > > > >> > >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
>> > > > > > >> > >>
>> > > > > > >> > >> OK, so right now it's just docs? How soon can we get a
>> VOTE
>> > > > > thread
>> > > > > > >> > started
>> > > > > > >> > >> for 4.0.0?
>> > > > > > >> > >>
>> > > > > > >> > >> On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <
>> > > > > > agrieve@chromium.org>
>> > > > > > >> > >> wrote:
>> > > > > > >> > >>
>> > > > > > >> > >> > mobilespec is now working again... Took longer than I
>> > would
>> > > > > have
>> > > > > > >> > >> > liked, but did you know that on Android FileReader
>> > triggers
>> > > > > > >> > >> > shouldInterceptRequest() with Blob URLs!?
>> > > > > > >> > >> >
>> > > > > > >> > >> > Separate thread is already happening re: whitelists,
>> so
>> > > once
>> > > > > > that's
>> > > > > > >> > >> > figured out, it's just docs afaict.
>> > > > > > >> > >> >
>> > > > > > >> > >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian Clelland <
>> > > > > > >> iclelland@chromium.org
>> > > > > > >> > >
>> > > > > > >> > >> > wrote:
>> > > > > > >> > >> >
>> > > > > > >> > >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <
>> > > > > purplecabbage@gmail.com
>> > > > > > >
>> > > > > > >> > wrote:
>> > > > > > >> > >> > >
>> > > > > > >> > >> > > > We should start a new whitelist plugin related
>> > thread.
>> > > > > > >> > >> > > >
>> > > > > > >> > >> > > > Why is a plugin blocking a release? Default (aka
>> > > > > no-plugin)
>> > > > > > >> > >> > > > behavior should be to allow all network requests
>> > > > shouldn't
>> > > > > > it?
>> > > > > > >> > >> > >
>> > > > > > >> > >> > >
>> > > > > > >> > >> > > Well, that just might be a blacklist then :)
>> > > > > > >> > >> > >
>> > > > > > >> > >> > >
>> > > > > > >> > >> > > > This thread is a
>> > > > > > >> > >> > > > month long, and not the first discussion of 4.0.0
>> for
>> > > > > > Android.
>> > > > > > >> > >> > > >
>> > > > > > >> > >> > >
>> > > > > > >> > >> > > Seriously, though -- the whitelist discussion is
>> much
>> > > > longer
>> > > > > > than
>> > > > > > >> > >> > > that,
>> > > > > > >> > >> > and
>> > > > > > >> > >> > > this isn't the first time that the default
>> > > > no-network-access
>> > > > > > >> policy
>> > > > > > >> > >> > > has been brought up:
>> > > > > > >> > >> > >
>> > > > > > >> > >> > > (Here's the first question, from *July*:
>> > > > > > >> > >> > > http://markmail.org/message/t4vj4saisem2mcgw
>> > > > > > >> > >> > > Here's where I mentioned what the implemented policy
>> > was:
>> > > > > > >> > >> > > http://markmail.org/message/s4necfnh4hnblpjm
>> > > > > > >> > >> > > And in another discussion:
>> > > > > > >> > >> > > http://markmail.org/message/ap7syhqysizmsvrz)
>> > > > > > >> > >> > >
>> > > > > > >> > >> > > If we want to reconsider that decision, then we
>> should
>> > > > > > certainly
>> > > > > > >> do
>> > > > > > >> > >> > > so before we cut a release. I think it would be a
>> real
>> > > > > problem
>> > > > > > to
>> > > > > > >> > >> > > change it afterwards, so let's get it right.
>> > > > > > >> > >> > >
>> > > > > > >> > >> > > Also, it's not the plugin itself that's blocking the
>> > > > release,
>> > > > > > >> it's
>> > > > > > >> > >> > > us making sure that we've implemented the core hooks
>> > > > > correctly
>> > > > > > so
>> > > > > > >> > >> > > that the plugin can actually do its job, and that
>> > people
>> > > > who
>> > > > > > >> don't
>> > > > > > >> > >> > > want that particular plugin can make a better one.
>> > > > > > >> > >> > >
>> > > > > > >> > >> > > (It is also an issue that a plugin, required for
>> > > > > > cordova-android
>> > > > > > >> > >> > > 4.0.0, breaks apps which are also building for
>> > > cordova-ios
>> > > > > > 3.8.0.
>> > > > > > >> > >> > > I'll take a
>> > > > > > >> > >> > look
>> > > > > > >> > >> > > at that, and either remove the ios-native portions
>> of
>> > the
>> > > > > > >> whitelist
>> > > > > > >> > >> > plugin,
>> > > > > > >> > >> > > or neuter it so that it doesn't interfere with an
>> ios
>> > app
>> > > > if
>> > > > > > it's
>> > > > > > >> > >> > > not on the unplug-whitelist branch of that repo.)
>> > > > > > >> > >> > >
>> > > > > > >> > >> > > Ian
>> > > > > > >> > >> > >
>> > > > > > >> > >> > >
>> > > > > > >> > >> > > > @purplecabbage
>> > > > > > >> > >> > > > risingj.com
>> > > > > > >> > >> > > >
>> > > > > > >> > >> > > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <
>> > > > shazron@gmail.com
>> > > > > >
>> > > > > > >> > wrote:
>> > > > > > >> > >> > > >
>> > > > > > >> > >> > > > > legacy-whitelist-plugin should be fixed so that
>> it
>> > > > > compiles
>> > > > > > >> on
>> > > > > > >> > >> > > > > cordova-ios@3.8.0. It shouldn't be a problem to
>> > fix
>> > > > this
>> > > > > > at
>> > > > > > >> > >> > > > > compile
>> > > > > > >> > >> > or
>> > > > > > >> > >> > > > > run-time (whichever is applicable here related
>> to
>> > the
>> > > > > > compile
>> > > > > > >> > >> > > > > error)
>> > > > > > >> > >> > > > >
>> > > > > > >> > >> > > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue
>> > > > > > >> > >> > > > > <dv...@gmail.com>
>> > > > > > >> > >> > > > wrote:
>> > > > > > >> > >> > > > > > On 2 March 2015 at 13:37, Joe Bowser <
>> > > > > bowserj@gmail.com>
>> > > > > > >> > wrote:
>> > > > > > >> > >> > > > > >> So, right now the whitelist changes are
>> what's
>> > > > holding
>> > > > > > up
>> > > > > > >> the
>> > > > > > >> > >> > 4.0.0
>> > > > > > >> > >> > > > > release
>> > > > > > >> > >> > > > > >> now? Is this really the only thing that's
>> > holding
>> > > > up
>> > > > > > this
>> > > > > > >> > >> > release?
>> > > > > > >> > >> > > > > >>
>> > > > > > >> > >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM Andrew
>> Grieve <
>> > > > > > >> > >> > > agrieve@chromium.org>
>> > > > > > >> > >> > > > > wrote:
>> > > > > > >> > >> > > > > >>
>> > > > > > >> > >> > > > > >>> I think we'll also need to finish with the
>> > > > whitelist
>> > > > > > >> changes
>> > > > > > >> > >> > > > > >>> &
>> > > > > > >> > >> > have
>> > > > > > >> > >> > > > > both
>> > > > > > >> > >> > > > > >>> the legacy and new-way whitelist plugins
>> > released
>> > > > > > before
>> > > > > > >> we
>> > > > > > >> > >> > > > > >>> can
>> > > > > > >> > >> > do
>> > > > > > >> > >> > > a
>> > > > > > >> > >> > > > > 4.0.0
>> > > > > > >> > >> > > > > >>> release (otherwise you wouldn't be able to
>> > write
>> > > an
>> > > > > app
>> > > > > > >> that
>> > > > > > >> > >> > > > > >>> hits
>> > > > > > >> > >> > > the
>> > > > > > >> > >> > > > > >>> network)
>> > > > > > >> > >> > > > > >>>
>> > > > > > >> > >> > > > > >
>> > > > > > >> > >> > > > > > Just FYI, the whitelist stuff is proving to
>> be a
>> > > bit
>> > > > > of a
>> > > > > > >> pain
>> > > > > > >> > >> > point.
>> > > > > > >> > >> > > > > > I'm using cordova-android@master, and need to
>> > > > install
>> > > > > > the
>> > > > > > >> > >> > > > > > legacy-whitelist plugin in order to make
>> network
>> > > > > > requests.
>> > > > > > >> > >> > > > > > Once the plugin is installed, everything
>> seems to
>> > > > work.
>> > > > > > >> > >> > > > > >
>> > > > > > >> > >> > > > > > The problem is that the legacy-whitelist
>> plugin
>> > > > > generates
>> > > > > > >> > >> > > > > > compile errors with cordova-ios@3.8.0, so
>> now I
>> > > > can't
>> > > > > > just
>> > > > > > >> > run
>> > > > > > >> > >> > > > > > `cordova build`, I need to split the
>> platforms up
>> > > and
>> > > > > > >> > >> > > > > > install/uninstall the plugin in between. If
>> > someone
>> > > > > > makes a
>> > > > > > >> > >> > > > > > dev build for Android and forgets the plugin,
>> it
>> > > will
>> > > > > > >> appear
>> > > > > > >> > >> > > > > > to build successfully but not actually
>> function
>> > > > > properly
>> > > > > > >> due
>> > > > > > >> > to
>> > > > > > >> > >> the whitelist.
>> > > > > > >> > >> > > > > >
>> > > > > > >> > >> > > > > > I know, this is all pre-release, so pain is
>> > > somewhat
>> > > > > > >> expected
>> > > > > > >> > >> > > > > > right now. I'm worried about the case where
>> > > > > > >> > >> > > > > > cordova-android@4.0.0 is released and
>> > > > > cordova-ios@3.8.0
>> > > > > > is
>> > > > > > >> > >> > > > > > still current, and how people
>> > > > > > >> > >> > can
>> > > > > > >> > >> > > > > > avoid whitelist breakage there.
>> > > > > > >> > >> > > > > >
>> > > > > > >> > >> > > > > >
>> > > > > > >> ------------------------------------------------------------
>> > > > > > >> > >> > ---------
>> > > > > > >> > >> > > > > > To unsubscribe, e-mail:
>> > > > > > dev-unsubscribe@cordova.apache.org
>> > > > > > >> > >> > > > > > For additional commands, e-mail:
>> > > > > > >> dev-help@cordova.apache.org
>> > > > > > >> > >> > > > > >
>> > > > > > >> > >> > > > >
>> > > > > > >> > >> > > > >
>> > > > > > ------------------------------------------------------------
>> > > > > > >> > >> > ---------
>> > > > > > >> > >> > > > > To unsubscribe, e-mail:
>> > > > > dev-unsubscribe@cordova.apache.org
>> > > > > > >> > >> > > > > For additional commands, e-mail:
>> > > > > > dev-help@cordova.apache.org
>> > > > > > >> > >> > > > >
>> > > > > > >> > >> > > > >
>> > > > > > >> > >> > > >
>> > > > > > >> > >> > >
>> > > > > > >> > >> >
>> > > > > > >> > >>
>> > > > > > >> >
>> > > > > > >> >
>> > > > >
>> ---------------------------------------------------------------------
>> > > > > > >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> > > > > > >> > For additional commands, e-mail:
>> dev-help@cordova.apache.org
>> > > > > > >> >
>> > > > > > >> >
>> > > > > > >>
>> > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > > --
>> > > > > Carlos Santana
>> > > > > <cs...@gmail.com>
>> > > > >
>> > > >
>> > >
>> >
>>
>
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Andrew Grieve <ag...@chromium.org>.
merged. thanks!
On Thu, Apr 9, 2015 at 3:01 PM, Nikhil Khandelwal <ni...@microsoft.com>
wrote:
> I have another small PR to the blog post for the release:
> https://github.com/cordova/apache-blog-posts/pull/36/commits
>
> Thanks,
> Nikhil
>
>
> -----Original Message-----
> From: Serge Huijben [mailto:s.huijben@gmail.com]
> Sent: Thursday, April 9, 2015 11:47 AM
> To: Ian Clelland; dev@cordova.apache.org
> Cc: leo.treggiari@intel.com
> Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
>
> Then, it seems strange to me that it logs an error and repeated warnings
> if the meta tag is missing. Perhaps we should remove that from the plugin.
>
> Op do 9 apr. 2015 om 20:21 schreef Ian Clelland <ic...@chromium.org>
>
> > Moving from [VOTE] thread:
> >
> > On Thu, Apr 9, 2015 at 1:44 PM, Serge Huijben <s....@gmail.com>
> wrote:
> >
> >> But why is the meta csp tag required?
> >
> >
> > It's not required, only recommended. It's more secure, as it can
> > restrict more network access than the whitelist itself is capable of.
> > (streaming <audio> and <video> tags, for instance).
> >
> > On Thu, Apr 9, 2015 at 1:44 PM, Treggiari, Leo
> > <le...@intel.com>
> > wrote:
> >
> >> Another question, based upon my understanding, which must be wrong!
> >
> >
> >>
> >> The 4.0.0 Android Release will require the cordova-plugin-whitelist
> >> in order to get a whitelist implemented correctly.
> >>
> >> Given its name (dash-style) it is only available as an node component.
> >>
> >> The is no released CLI that knows how to fetch from npm?
> >> Or does 4.3, even though I don't see it in the release notes?
> >> Even so, there are many previous CLI releases which will not work?
> >>
> >
> > This is at least partly resolved by the fact that no released CLI
> > points to cordova-android 4.0.0. Once 4.0.0 is released. we will be
> > able to release a version of the CLI which downloads it by default.
> >
> > The whitelist plugins are published already, and discussion is
> > underway about voting/releasing cordova-lib (and accompanying tools),
> > so I think there are only two possible timelines:
> >
> > A) whitelist plugins released, then cordova-android 4 released, then
> > tools released (supports NPM plugins and Android 4).
> >
> > B) plugins released, then tools released (supports NPM plugins), then
> > cordova-android 4 released, then a small bump of tools is released (to
> > pin to cordova-android 4)
> >
> > In either case, users of the released CLI always have a version which
> > works.
> >
> >
> >> It would be good for the release notes to explain the situation.
> >>
> >> Leo
> >>
> >
> > On Thu, Apr 9, 2015 at 1:24 PM, Michal Mocny <mm...@chromium.org>
> wrote:
> >
> >> Splashscreens was mentioned, icons was not. I don't think there is
> >> an icons change?
> >>
> >> On Thu, Apr 9, 2015 at 1:17 PM, Joe Bowser <bo...@gmail.com> wrote:
> >>
> >> > So, wasn't there a change regarding icons and spashscreens being
> moved?
> >> I
> >> > have no idea if we want to add that, or if adding that should
> >> > happen
> >> after
> >> > the release?
> >> >
> >> > On Wed, Apr 8, 2015 at 7:09 PM Andrew Grieve <ag...@chromium.org>
> >> wrote:
> >> >
> >> > > CB-8684 is now merged and I've updated the targetSdk (and made a
> >> couple
> >> > > other changes).
> >> > >
> >> > > I'll start the release process in the morning as long as there no
> >> > > objections.
> >> > >
> >> > >
> >> > > On Tue, Apr 7, 2015 at 2:20 PM, Andrew Grieve
> >> > > <ag...@chromium.org>
> >> > > wrote:
> >> > >
> >> > > > I'll start on it once CB-8684 lands (Tony - assuming you'll
> >> > > > have
> >> this
> >> > > done
> >> > > > shortly and would prefer it lands?)
> >> > > >
> >> > > > On Tue, Apr 7, 2015 at 1:33 PM, Jesse <pu...@gmail.com>
> >> wrote:
> >> > > >
> >> > > >> Sweet!
> >> > > >>
> >> > > >> @purplecabbage
> >> > > >> risingj.com
> >> > > >>
> >> > > >> On Tue, Apr 7, 2015 at 8:35 AM, Andrew Grieve <
> >> agrieve@chromium.org>
> >> > > >> wrote:
> >> > > >>
> >> > > >> > Let's do it!
> >> > > >> >
> >> > > >> > On Mon, Apr 6, 2015 at 7:33 PM, Joe Bowser
> >> > > >> > <bo...@gmail.com>
> >> > wrote:
> >> > > >> >
> >> > > >> > > So, I think we should put off the embedder's guide until
> >> > > >> > > after
> >> the
> >> > > >> > > release. A lot of it has changed, and since we're still
> >> > technically
> >> > > >> > > obligated to support the 3.x release tree for six months,
> >> > > >> > > that
> >> > > should
> >> > > >> buy
> >> > > >> > > us some time to figure out how that is going to work.
> >> > > >> > > Getting
> >> > > >> Cordova to
> >> > > >> > > work with a vanilla Android Studio project is a
> >> > > >> > > non-trivial
> >> task.
> >> > > >> > >
> >> > > >> > > Given that everything else appears to be done, should we
> >> > > >> > > start
> >> > > voting
> >> > > >> on
> >> > > >> > an
> >> > > >> > > RC for this? What do people think?
> >> > > >> > >
> >> > > >> > >
> >> > > >> > >
> >> > > >> > > On Thu, Mar 19, 2015 at 10:31 AM Andrew Grieve <
> >> > > agrieve@chromium.org>
> >> > > >> > > wrote:
> >> > > >> > >
> >> > > >> > > > Here's issues:
> >> > > >> > > > https://issues.apache.org/jira/browse/CB-8715 (docs)
> >> > > >> > > > https://issues.apache.org/jira/browse/CB-8716
> >> > > >> > > > (whitelist)
> >> > > >> > > > https://issues.apache.org/jira/browse/CB-8717 (write
> >> > > >> RELEASENOTES.md)
> >> > > >> > > >
> >> > > >> > > > On Tue, Mar 17, 2015 at 10:15 AM, Carlos Santana <
> >> > > >> csantana23@gmail.com
> >> > > >> > >
> >> > > >> > > > wrote:
> >> > > >> > > >
> >> > > >> > > > > I would say let's start RC testing and voting, But not
> >> > > >> > > > > pin
> >> the
> >> > > >> > version
> >> > > >> > > in
> >> > > >> > > > > Cordova CLI until the tasks that Andrew mentioned are
> done.
> >> > > >> > > > > Andrew can you create the JIRA Items for the tasks
> >> > > >> > > > > that
> >> need
> >> > to
> >> > > be
> >> > > >> > > done.
> >> > > >> > > > I
> >> > > >> > > > > thought there was a discussion about creating JIRA
> >> > > >> > > > > Items to
> >> > help
> >> > > >> > track
> >> > > >> > > > and
> >> > > >> > > > > know what's left for release something.
> >> > > >> > > > >
> >> > > >> > > > > - upgrade guide,
> >> > > >> > > > > - publishing whitelist plugins,
> >> > > >> > > > > - and making it so that the default project template
> >> includes
> >> > > >> <plugin
> >> > > >> > > > > name="cordova-plugin-whitelist" />)
> >> > > >> > > > >
> >> > > >> > > > >
> >> > > >> > > > > On Mon, Mar 16, 2015 at 11:21 PM, Ian Clelland <
> >> > > >> > iclelland@chromium.org
> >> > > >> > > >
> >> > > >> > > > > wrote:
> >> > > >> > > > >
> >> > > >> > > > > > We'll probably need at least an RC for the whitelist
> >> plugin,
> >> > > if
> >> > > >> > not a
> >> > > >> > > > > vote,
> >> > > >> > > > > > to be able to vote on this.
> >> > > >> > > > > >
> >> > > >> > > > > > Or can we just include instructions like "Use
> >> > > >> > > > > > cordova-plugin-whitelist@f70b1bc for testing" while
> >> > > >> > > > > > we
> >> > start
> >> > > >> the
> >> > > >> > > > > official
> >> > > >> > > > > > release process for the plugins?
> >> > > >> > > > > >
> >> > > >> > > > > > On Mon, Mar 16, 2015 at 11:17 PM, Ian Clelland <
> >> > > >> > > iclelland@chromium.org
> >> > > >> > > > >
> >> > > >> > > > > > wrote:
> >> > > >> > > > > >
> >> > > >> > > > > > > +1 -- Let's get this out the door :)
> >> > > >> > > > > > > I'll see what I can get done to move it in that
> >> direction.
> >> > > >> > > > > > >
> >> > > >> > > > > > > On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <
> >> > > >> > > agrieve@chromium.org
> >> > > >> > > > >
> >> > > >> > > > > > > wrote:
> >> > > >> > > > > > >
> >> > > >> > > > > > >> Everything's ready afaik (minus upgrade guide,
> >> publishing
> >> > > >> > > whitelist
> >> > > >> > > > > > >> plugins, and making it so that the default
> >> > > >> > > > > > >> project
> >> > template
> >> > > >> > > includes
> >> > > >> > > > > > >> <plugin name="cordova-plugin-whitelist" />).
> >> > > >> > > > > > >> Maybe
> >> let's
> >> > > do
> >> > > >> a RC
> >> > > >> > > > while
> >> > > >> > > > > > we
> >> > > >> > > > > > >> wait on these things being finished up?
> >> > > >> > > > > > >>
> >> > > >> > > > > > >> If anyone wants to take on any of these tasks,
> >> > > >> > > > > > >> that
> >> would
> >> > > be
> >> > > >> > > > awesome.
> >> > > >> > > > > > >>
> >> > > >> > > > > > >> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <
> >> > > shazron@gmail.com>
> >> > > >> > > wrote:
> >> > > >> > > > > > >>
> >> > > >> > > > > > >> > +1 for vote thread, let's get this thing out so
> >> people
> >> > > >> (that
> >> > > >> > are
> >> > > >> > > > not
> >> > > >> > > > > > >> > us) can test...
> >> > > >> > > > > > >> >
> >> > > >> > > > > > >> >
> >> > > >> > > > > > >> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <
> >> > > >> > bowserj@gmail.com>
> >> > > >> > > > > > wrote:
> >> > > >> > > > > > >> > > OK, this is a three month old thread, and
> >> > > >> > > > > > >> > > we're
> >> > waiting
> >> > > >> on a
> >> > > >> > > > > > >> discussion
> >> > > >> > > > > > >> > > before we release something? I really think
> >> > > >> > > > > > >> > > we
> >> should
> >> > > go
> >> > > >> to
> >> > > >> > a
> >> > > >> > > > vote
> >> > > >> > > > > > >> thread
> >> > > >> > > > > > >> > > now that we have a legacy whitelist plugin
> >> > > >> > > > > > >> > > and a
> >> new
> >> > > >> style
> >> > > >> > > > > whitelist
> >> > > >> > > > > > >> > > plugin. We shouldn't keep constantly
> >> > > >> > > > > > >> > > delaying
> >> this
> >> > > >> release
> >> > > >> > > > > because
> >> > > >> > > > > > of
> >> > > >> > > > > > >> > > what's happening on other platforms,
> >> > > >> > > > > > >> > > especially
> >> since
> >> > > we
> >> > > >> > > already
> >> > > >> > > > > > >> > pluginized
> >> > > >> > > > > > >> > > the whitelist.
> >> > > >> > > > > > >> > >
> >> > > >> > > > > > >> > > Can we please release soon?
> >> > > >> > > > > > >> > >
> >> > > >> > > > > > >> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil
> >> > > >> > > > > > >> > > Khandelwal
> >> <
> >> > > >> > > > > > >> > nikhilkh@microsoft.com>
> >> > > >> > > > > > >> > > wrote:
> >> > > >> > > > > > >> > >
> >> > > >> > > > > > >> > >> I know we discussed a couple of approaches
> >> > > implementing
> >> > > >> the
> >> > > >> > > > > default
> >> > > >> > > > > > >> > >> whitelist policy for Android/iOS - either
> >> > > >> > > > > > >> > >> every
> >> app
> >> > > >> would
> >> > > >> > be
> >> > > >> > > > > > >> required to
> >> > > >> > > > > > >> > >> include the whitelist plugin or have it have
> >> smart
> >> > > >> defaults
> >> > > >> > > in
> >> > > >> > > > > the
> >> > > >> > > > > > >> > platform
> >> > > >> > > > > > >> > >> implementation and the plugin being able to
> >> override
> >> > > >> them.
> >> > > >> > > > > > >> > >>
> >> > > >> > > > > > >> > >> I don’t think that thread closed with any
> >> > conclusions.
> >> > > >> > > > > > >> > >>
> >> > > >> > > > > > >> > >> Thanks,
> >> > > >> > > > > > >> > >> Nikhil
> >> > > >> > > > > > >> > >>
> >> > > >> > > > > > >> > >>
> >> > > >> > > > > > >> > >> -----Original Message-----
> >> > > >> > > > > > >> > >> From: Joe Bowser [mailto:bowserj@gmail.com]
> >> > > >> > > > > > >> > >> Sent: Thursday, March 12, 2015 11:23 AM
> >> > > >> > > > > > >> > >> To: dev
> >> > > >> > > > > > >> > >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0
> >> Release
> >> > > >> > > > > > >> > >>
> >> > > >> > > > > > >> > >> OK, so right now it's just docs? How soon
> >> > > >> > > > > > >> > >> can we
> >> > get a
> >> > > >> VOTE
> >> > > >> > > > > thread
> >> > > >> > > > > > >> > started
> >> > > >> > > > > > >> > >> for 4.0.0?
> >> > > >> > > > > > >> > >>
> >> > > >> > > > > > >> > >> On Wed, Mar 4, 2015 at 10:47 AM Andrew
> >> > > >> > > > > > >> > >> Grieve <
> >> > > >> > > > > > agrieve@chromium.org>
> >> > > >> > > > > > >> > >> wrote:
> >> > > >> > > > > > >> > >>
> >> > > >> > > > > > >> > >> > mobilespec is now working again... Took
> >> > > >> > > > > > >> > >> > longer
> >> > than
> >> > > I
> >> > > >> > would
> >> > > >> > > > > have
> >> > > >> > > > > > >> > >> > liked, but did you know that on Android
> >> FileReader
> >> > > >> > triggers
> >> > > >> > > > > > >> > >> > shouldInterceptRequest() with Blob URLs!?
> >> > > >> > > > > > >> > >> >
> >> > > >> > > > > > >> > >> > Separate thread is already happening re:
> >> > whitelists,
> >> > > >> so
> >> > > >> > > once
> >> > > >> > > > > > that's
> >> > > >> > > > > > >> > >> > figured out, it's just docs afaict.
> >> > > >> > > > > > >> > >> >
> >> > > >> > > > > > >> > >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian
> >> > > >> > > > > > >> > >> > Clelland <
> >> > > >> > > > > > >> iclelland@chromium.org
> >> > > >> > > > > > >> > >
> >> > > >> > > > > > >> > >> > wrote:
> >> > > >> > > > > > >> > >> >
> >> > > >> > > > > > >> > >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <
> >> > > >> > > > > purplecabbage@gmail.com
> >> > > >> > > > > > >
> >> > > >> > > > > > >> > wrote:
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > > > We should start a new whitelist plugin
> >> related
> >> > > >> > thread.
> >> > > >> > > > > > >> > >> > > >
> >> > > >> > > > > > >> > >> > > > Why is a plugin blocking a release?
> >> Default
> >> > > (aka
> >> > > >> > > > > no-plugin)
> >> > > >> > > > > > >> > >> > > > behavior should be to allow all
> >> > > >> > > > > > >> > >> > > > network
> >> > requests
> >> > > >> > > > shouldn't
> >> > > >> > > > > > it?
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > > Well, that just might be a blacklist
> >> > > >> > > > > > >> > >> > > then :)
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > > > This thread is a month long, and not
> >> > > >> > > > > > >> > >> > > > the first discussion of
> >> > > 4.0.0
> >> > > >> for
> >> > > >> > > > > > Android.
> >> > > >> > > > > > >> > >> > > >
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > > Seriously, though -- the whitelist
> >> discussion is
> >> > > >> much
> >> > > >> > > > longer
> >> > > >> > > > > > than
> >> > > >> > > > > > >> > >> > > that,
> >> > > >> > > > > > >> > >> > and
> >> > > >> > > > > > >> > >> > > this isn't the first time that the
> >> > > >> > > > > > >> > >> > > default
> >> > > >> > > > no-network-access
> >> > > >> > > > > > >> policy
> >> > > >> > > > > > >> > >> > > has been brought up:
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > > (Here's the first question, from *July*:
> >> > > >> > > > > > >> > >> > > http://markmail.org/message/t4vj4saisem2
> >> > > >> > > > > > >> > >> > > mcgw Here's where I mentioned what the
> >> > > >> > > > > > >> > >> > > implemented
> >> > > policy
> >> > > >> > was:
> >> > > >> > > > > > >> > >> > > http://markmail.org/message/s4necfnh4hnb
> >> > > >> > > > > > >> > >> > > lpjm And in another discussion:
> >> > > >> > > > > > >> > >> > > http://markmail.org/message/ap7syhqysizm
> >> > > >> > > > > > >> > >> > > svrz
> >> )
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > > If we want to reconsider that decision,
> >> > > >> > > > > > >> > >> > > then
> >> we
> >> > > >> should
> >> > > >> > > > > > certainly
> >> > > >> > > > > > >> do
> >> > > >> > > > > > >> > >> > > so before we cut a release. I think it
> >> > > >> > > > > > >> > >> > > would
> >> be
> >> > a
> >> > > >> real
> >> > > >> > > > > problem
> >> > > >> > > > > > to
> >> > > >> > > > > > >> > >> > > change it afterwards, so let's get it
> right.
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > > Also, it's not the plugin itself that's
> >> blocking
> >> > > the
> >> > > >> > > > release,
> >> > > >> > > > > > >> it's
> >> > > >> > > > > > >> > >> > > us making sure that we've implemented
> >> > > >> > > > > > >> > >> > > the
> >> core
> >> > > hooks
> >> > > >> > > > > correctly
> >> > > >> > > > > > so
> >> > > >> > > > > > >> > >> > > that the plugin can actually do its job,
> >> > > >> > > > > > >> > >> > > and
> >> > that
> >> > > >> > people
> >> > > >> > > > who
> >> > > >> > > > > > >> don't
> >> > > >> > > > > > >> > >> > > want that particular plugin can make a
> >> > > >> > > > > > >> > >> > > better
> >> > one.
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > > (It is also an issue that a plugin,
> >> > > >> > > > > > >> > >> > > required
> >> for
> >> > > >> > > > > > cordova-android
> >> > > >> > > > > > >> > >> > > 4.0.0, breaks apps which are also
> >> > > >> > > > > > >> > >> > > building
> >> for
> >> > > >> > > cordova-ios
> >> > > >> > > > > > 3.8.0.
> >> > > >> > > > > > >> > >> > > I'll take a
> >> > > >> > > > > > >> > >> > look
> >> > > >> > > > > > >> > >> > > at that, and either remove the
> >> > > >> > > > > > >> > >> > > ios-native
> >> > portions
> >> > > >> of
> >> > > >> > the
> >> > > >> > > > > > >> whitelist
> >> > > >> > > > > > >> > >> > plugin,
> >> > > >> > > > > > >> > >> > > or neuter it so that it doesn't
> >> > > >> > > > > > >> > >> > > interfere
> >> with
> >> > an
> >> > > >> ios
> >> > > >> > app
> >> > > >> > > > if
> >> > > >> > > > > > it's
> >> > > >> > > > > > >> > >> > > not on the unplug-whitelist branch of
> >> > > >> > > > > > >> > >> > > that
> >> > repo.)
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > > Ian
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > > > @purplecabbage risingj.com
> >> > > >> > > > > > >> > >> > > >
> >> > > >> > > > > > >> > >> > > > On Mon, Mar 2, 2015 at 2:02 PM,
> >> > > >> > > > > > >> > >> > > > Shazron <
> >> > > >> > > > shazron@gmail.com
> >> > > >> > > > > >
> >> > > >> > > > > > >> > wrote:
> >> > > >> > > > > > >> > >> > > >
> >> > > >> > > > > > >> > >> > > > > legacy-whitelist-plugin should be
> >> > > >> > > > > > >> > >> > > > > fixed
> >> so
> >> > > that
> >> > > >> it
> >> > > >> > > > > compiles
> >> > > >> > > > > > >> on
> >> > > >> > > > > > >> > >> > > > > cordova-ios@3.8.0. It shouldn't be a
> >> > problem
> >> > > to
> >> > > >> > fix
> >> > > >> > > > this
> >> > > >> > > > > > at
> >> > > >> > > > > > >> > >> > > > > compile
> >> > > >> > > > > > >> > >> > or
> >> > > >> > > > > > >> > >> > > > > run-time (whichever is applicable
> >> > > >> > > > > > >> > >> > > > > here
> >> > related
> >> > > >> to
> >> > > >> > the
> >> > > >> > > > > > compile
> >> > > >> > > > > > >> > >> > > > > error)
> >> > > >> > > > > > >> > >> > > > >
> >> > > >> > > > > > >> > >> > > > > On Mon, Mar 2, 2015 at 1:47 PM,
> >> > > >> > > > > > >> > >> > > > > Darryl
> >> Pogue
> >> > > >> > > > > > >> > >> > > > > <dv...@gmail.com>
> >> > > >> > > > > > >> > >> > > > wrote:
> >> > > >> > > > > > >> > >> > > > > > On 2 March 2015 at 13:37, Joe
> >> > > >> > > > > > >> > >> > > > > > Bowser <
> >> > > >> > > > > bowserj@gmail.com>
> >> > > >> > > > > > >> > wrote:
> >> > > >> > > > > > >> > >> > > > > >> So, right now the whitelist
> >> > > >> > > > > > >> > >> > > > > >> changes
> >> are
> >> > > >> what's
> >> > > >> > > > holding
> >> > > >> > > > > > up
> >> > > >> > > > > > >> the
> >> > > >> > > > > > >> > >> > 4.0.0
> >> > > >> > > > > > >> > >> > > > > release
> >> > > >> > > > > > >> > >> > > > > >> now? Is this really the only
> >> > > >> > > > > > >> > >> > > > > >> thing
> >> > that's
> >> > > >> > holding
> >> > > >> > > > up
> >> > > >> > > > > > this
> >> > > >> > > > > > >> > >> > release?
> >> > > >> > > > > > >> > >> > > > > >>
> >> > > >> > > > > > >> > >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM
> >> Andrew
> >> > > >> Grieve <
> >> > > >> > > > > > >> > >> > > agrieve@chromium.org>
> >> > > >> > > > > > >> > >> > > > > wrote:
> >> > > >> > > > > > >> > >> > > > > >>
> >> > > >> > > > > > >> > >> > > > > >>> I think we'll also need to
> >> > > >> > > > > > >> > >> > > > > >>> finish
> >> with
> >> > the
> >> > > >> > > > whitelist
> >> > > >> > > > > > >> changes
> >> > > >> > > > > > >> > >> > > > > >>> &
> >> > > >> > > > > > >> > >> > have
> >> > > >> > > > > > >> > >> > > > > both
> >> > > >> > > > > > >> > >> > > > > >>> the legacy and new-way whitelist
> >> plugins
> >> > > >> > released
> >> > > >> > > > > > before
> >> > > >> > > > > > >> we
> >> > > >> > > > > > >> > >> > > > > >>> can
> >> > > >> > > > > > >> > >> > do
> >> > > >> > > > > > >> > >> > > a
> >> > > >> > > > > > >> > >> > > > > 4.0.0
> >> > > >> > > > > > >> > >> > > > > >>> release (otherwise you wouldn't
> >> > > >> > > > > > >> > >> > > > > >>> be
> >> able
> >> > to
> >> > > >> > write
> >> > > >> > > an
> >> > > >> > > > > app
> >> > > >> > > > > > >> that
> >> > > >> > > > > > >> > >> > > > > >>> hits
> >> > > >> > > > > > >> > >> > > the
> >> > > >> > > > > > >> > >> > > > > >>> network)
> >> > > >> > > > > > >> > >> > > > > >>>
> >> > > >> > > > > > >> > >> > > > > >
> >> > > >> > > > > > >> > >> > > > > > Just FYI, the whitelist stuff is
> >> proving
> >> > to
> >> > > >> be a
> >> > > >> > > bit
> >> > > >> > > > > of a
> >> > > >> > > > > > >> pain
> >> > > >> > > > > > >> > >> > point.
> >> > > >> > > > > > >> > >> > > > > > I'm using cordova-android@master,
> >> > > >> > > > > > >> > >> > > > > > and
> >> > need
> >> > > to
> >> > > >> > > > install
> >> > > >> > > > > > the
> >> > > >> > > > > > >> > >> > > > > > legacy-whitelist plugin in order
> >> > > >> > > > > > >> > >> > > > > > to
> >> make
> >> > > >> network
> >> > > >> > > > > > requests.
> >> > > >> > > > > > >> > >> > > > > > Once the plugin is installed,
> >> everything
> >> > > >> seems to
> >> > > >> > > > work.
> >> > > >> > > > > > >> > >> > > > > >
> >> > > >> > > > > > >> > >> > > > > > The problem is that the
> >> legacy-whitelist
> >> > > >> plugin
> >> > > >> > > > > generates
> >> > > >> > > > > > >> > >> > > > > > compile errors with
> >> > > >> > > > > > >> > >> > > > > > cordova-ios@3.8.0,
> >> so
> >> > > >> now I
> >> > > >> > > > can't
> >> > > >> > > > > > just
> >> > > >> > > > > > >> > run
> >> > > >> > > > > > >> > >> > > > > > `cordova build`, I need to split
> >> > > >> > > > > > >> > >> > > > > > the
> >> > > >> platforms up
> >> > > >> > > and
> >> > > >> > > > > > >> > >> > > > > > install/uninstall the plugin in
> >> between.
> >> > If
> >> > > >> > someone
> >> > > >> > > > > > makes a
> >> > > >> > > > > > >> > >> > > > > > dev build for Android and forgets
> >> > > >> > > > > > >> > >> > > > > > the
> >> > > plugin,
> >> > > >> it
> >> > > >> > > will
> >> > > >> > > > > > >> appear
> >> > > >> > > > > > >> > >> > > > > > to build successfully but not
> >> > > >> > > > > > >> > >> > > > > > actually
> >> > > >> function
> >> > > >> > > > > properly
> >> > > >> > > > > > >> due
> >> > > >> > > > > > >> > to
> >> > > >> > > > > > >> > >> the whitelist.
> >> > > >> > > > > > >> > >> > > > > >
> >> > > >> > > > > > >> > >> > > > > > I know, this is all pre-release,
> >> > > >> > > > > > >> > >> > > > > > so
> >> pain
> >> > is
> >> > > >> > > somewhat
> >> > > >> > > > > > >> expected
> >> > > >> > > > > > >> > >> > > > > > right now. I'm worried about the
> >> > > >> > > > > > >> > >> > > > > > case
> >> > where
> >> > > >> > > > > > >> > >> > > > > > cordova-android@4.0.0 is released
> >> > > >> > > > > > >> > >> > > > > > and
> >> > > >> > > > > cordova-ios@3.8.0
> >> > > >> > > > > > is
> >> > > >> > > > > > >> > >> > > > > > still current, and how people
> >> > > >> > > > > > >> > >> > can
> >> > > >> > > > > > >> > >> > > > > > avoid whitelist breakage there.
> >> > > >> > > > > > >> > >> > > > > >
> >> > > >> > > > > > >> > >> > > > > >
> >> > > >> > > > > > >> ------------------------------
> >> > > ------------------------------
> >> > > >> > > > > > >> > >> > ---------
> >> > > >> > > > > > >> > >> > > > > > To unsubscribe, e-mail:
> >> > > >> > > > > > dev-unsubscribe@cordova.apache.org
> >> > > >> > > > > > >> > >> > > > > > For additional commands, e-mail:
> >> > > >> > > > > > >> dev-help@cordova.apache.org
> >> > > >> > > > > > >> > >> > > > > >
> >> > > >> > > > > > >> > >> > > > >
> >> > > >> > > > > > >> > >> > > > >
> >> > > >> > > > > >
> >> ------------------------------------------------------------
> >> > > >> > > > > > >> > >> > ---------
> >> > > >> > > > > > >> > >> > > > > To unsubscribe, e-mail:
> >> > > >> > > > > dev-unsubscribe@cordova.apache.org
> >> > > >> > > > > > >> > >> > > > > For additional commands, e-mail:
> >> > > >> > > > > > dev-help@cordova.apache.org
> >> > > >> > > > > > >> > >> > > > >
> >> > > >> > > > > > >> > >> > > > >
> >> > > >> > > > > > >> > >> > > >
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> >
> >> > > >> > > > > > >> > >>
> >> > > >> > > > > > >> >
> >> > > >> > > > > > >> >
> >> > > >> > > > >
> >> > > >>
> >> ---------------------------------------------------------------------
> >> > > >> > > > > > >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.
> >> > > apache.org
> >> > > >> > > > > > >> > For additional commands, e-mail:
> >> > > >> dev-help@cordova.apache.org
> >> > > >> > > > > > >> >
> >> > > >> > > > > > >> >
> >> > > >> > > > > > >>
> >> > > >> > > > > > >
> >> > > >> > > > > > >
> >> > > >> > > > > >
> >> > > >> > > > >
> >> > > >> > > > >
> >> > > >> > > > >
> >> > > >> > > > > --
> >> > > >> > > > > Carlos Santana
> >> > > >> > > > > <cs...@gmail.com>
> >> > > >> > > > >
> >> > > >> > > >
> >> > > >> > >
> >> > > >> >
> >> > > >>
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
RE: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Nikhil Khandelwal <ni...@microsoft.com>.
I have another small PR to the blog post for the release: https://github.com/cordova/apache-blog-posts/pull/36/commits
Thanks,
Nikhil
-----Original Message-----
From: Serge Huijben [mailto:s.huijben@gmail.com]
Sent: Thursday, April 9, 2015 11:47 AM
To: Ian Clelland; dev@cordova.apache.org
Cc: leo.treggiari@intel.com
Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
Then, it seems strange to me that it logs an error and repeated warnings if the meta tag is missing. Perhaps we should remove that from the plugin.
Op do 9 apr. 2015 om 20:21 schreef Ian Clelland <ic...@chromium.org>
> Moving from [VOTE] thread:
>
> On Thu, Apr 9, 2015 at 1:44 PM, Serge Huijben <s....@gmail.com> wrote:
>
>> But why is the meta csp tag required?
>
>
> It's not required, only recommended. It's more secure, as it can
> restrict more network access than the whitelist itself is capable of.
> (streaming <audio> and <video> tags, for instance).
>
> On Thu, Apr 9, 2015 at 1:44 PM, Treggiari, Leo
> <le...@intel.com>
> wrote:
>
>> Another question, based upon my understanding, which must be wrong!
>
>
>>
>> The 4.0.0 Android Release will require the cordova-plugin-whitelist
>> in order to get a whitelist implemented correctly.
>>
>> Given its name (dash-style) it is only available as an node component.
>>
>> The is no released CLI that knows how to fetch from npm?
>> Or does 4.3, even though I don't see it in the release notes?
>> Even so, there are many previous CLI releases which will not work?
>>
>
> This is at least partly resolved by the fact that no released CLI
> points to cordova-android 4.0.0. Once 4.0.0 is released. we will be
> able to release a version of the CLI which downloads it by default.
>
> The whitelist plugins are published already, and discussion is
> underway about voting/releasing cordova-lib (and accompanying tools),
> so I think there are only two possible timelines:
>
> A) whitelist plugins released, then cordova-android 4 released, then
> tools released (supports NPM plugins and Android 4).
>
> B) plugins released, then tools released (supports NPM plugins), then
> cordova-android 4 released, then a small bump of tools is released (to
> pin to cordova-android 4)
>
> In either case, users of the released CLI always have a version which
> works.
>
>
>> It would be good for the release notes to explain the situation.
>>
>> Leo
>>
>
> On Thu, Apr 9, 2015 at 1:24 PM, Michal Mocny <mm...@chromium.org> wrote:
>
>> Splashscreens was mentioned, icons was not. I don't think there is
>> an icons change?
>>
>> On Thu, Apr 9, 2015 at 1:17 PM, Joe Bowser <bo...@gmail.com> wrote:
>>
>> > So, wasn't there a change regarding icons and spashscreens being moved?
>> I
>> > have no idea if we want to add that, or if adding that should
>> > happen
>> after
>> > the release?
>> >
>> > On Wed, Apr 8, 2015 at 7:09 PM Andrew Grieve <ag...@chromium.org>
>> wrote:
>> >
>> > > CB-8684 is now merged and I've updated the targetSdk (and made a
>> couple
>> > > other changes).
>> > >
>> > > I'll start the release process in the morning as long as there no
>> > > objections.
>> > >
>> > >
>> > > On Tue, Apr 7, 2015 at 2:20 PM, Andrew Grieve
>> > > <ag...@chromium.org>
>> > > wrote:
>> > >
>> > > > I'll start on it once CB-8684 lands (Tony - assuming you'll
>> > > > have
>> this
>> > > done
>> > > > shortly and would prefer it lands?)
>> > > >
>> > > > On Tue, Apr 7, 2015 at 1:33 PM, Jesse <pu...@gmail.com>
>> wrote:
>> > > >
>> > > >> Sweet!
>> > > >>
>> > > >> @purplecabbage
>> > > >> risingj.com
>> > > >>
>> > > >> On Tue, Apr 7, 2015 at 8:35 AM, Andrew Grieve <
>> agrieve@chromium.org>
>> > > >> wrote:
>> > > >>
>> > > >> > Let's do it!
>> > > >> >
>> > > >> > On Mon, Apr 6, 2015 at 7:33 PM, Joe Bowser
>> > > >> > <bo...@gmail.com>
>> > wrote:
>> > > >> >
>> > > >> > > So, I think we should put off the embedder's guide until
>> > > >> > > after
>> the
>> > > >> > > release. A lot of it has changed, and since we're still
>> > technically
>> > > >> > > obligated to support the 3.x release tree for six months,
>> > > >> > > that
>> > > should
>> > > >> buy
>> > > >> > > us some time to figure out how that is going to work.
>> > > >> > > Getting
>> > > >> Cordova to
>> > > >> > > work with a vanilla Android Studio project is a
>> > > >> > > non-trivial
>> task.
>> > > >> > >
>> > > >> > > Given that everything else appears to be done, should we
>> > > >> > > start
>> > > voting
>> > > >> on
>> > > >> > an
>> > > >> > > RC for this? What do people think?
>> > > >> > >
>> > > >> > >
>> > > >> > >
>> > > >> > > On Thu, Mar 19, 2015 at 10:31 AM Andrew Grieve <
>> > > agrieve@chromium.org>
>> > > >> > > wrote:
>> > > >> > >
>> > > >> > > > Here's issues:
>> > > >> > > > https://issues.apache.org/jira/browse/CB-8715 (docs)
>> > > >> > > > https://issues.apache.org/jira/browse/CB-8716
>> > > >> > > > (whitelist)
>> > > >> > > > https://issues.apache.org/jira/browse/CB-8717 (write
>> > > >> RELEASENOTES.md)
>> > > >> > > >
>> > > >> > > > On Tue, Mar 17, 2015 at 10:15 AM, Carlos Santana <
>> > > >> csantana23@gmail.com
>> > > >> > >
>> > > >> > > > wrote:
>> > > >> > > >
>> > > >> > > > > I would say let's start RC testing and voting, But not
>> > > >> > > > > pin
>> the
>> > > >> > version
>> > > >> > > in
>> > > >> > > > > Cordova CLI until the tasks that Andrew mentioned are done.
>> > > >> > > > > Andrew can you create the JIRA Items for the tasks
>> > > >> > > > > that
>> need
>> > to
>> > > be
>> > > >> > > done.
>> > > >> > > > I
>> > > >> > > > > thought there was a discussion about creating JIRA
>> > > >> > > > > Items to
>> > help
>> > > >> > track
>> > > >> > > > and
>> > > >> > > > > know what's left for release something.
>> > > >> > > > >
>> > > >> > > > > - upgrade guide,
>> > > >> > > > > - publishing whitelist plugins,
>> > > >> > > > > - and making it so that the default project template
>> includes
>> > > >> <plugin
>> > > >> > > > > name="cordova-plugin-whitelist" />)
>> > > >> > > > >
>> > > >> > > > >
>> > > >> > > > > On Mon, Mar 16, 2015 at 11:21 PM, Ian Clelland <
>> > > >> > iclelland@chromium.org
>> > > >> > > >
>> > > >> > > > > wrote:
>> > > >> > > > >
>> > > >> > > > > > We'll probably need at least an RC for the whitelist
>> plugin,
>> > > if
>> > > >> > not a
>> > > >> > > > > vote,
>> > > >> > > > > > to be able to vote on this.
>> > > >> > > > > >
>> > > >> > > > > > Or can we just include instructions like "Use
>> > > >> > > > > > cordova-plugin-whitelist@f70b1bc for testing" while
>> > > >> > > > > > we
>> > start
>> > > >> the
>> > > >> > > > > official
>> > > >> > > > > > release process for the plugins?
>> > > >> > > > > >
>> > > >> > > > > > On Mon, Mar 16, 2015 at 11:17 PM, Ian Clelland <
>> > > >> > > iclelland@chromium.org
>> > > >> > > > >
>> > > >> > > > > > wrote:
>> > > >> > > > > >
>> > > >> > > > > > > +1 -- Let's get this out the door :)
>> > > >> > > > > > > I'll see what I can get done to move it in that
>> direction.
>> > > >> > > > > > >
>> > > >> > > > > > > On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <
>> > > >> > > agrieve@chromium.org
>> > > >> > > > >
>> > > >> > > > > > > wrote:
>> > > >> > > > > > >
>> > > >> > > > > > >> Everything's ready afaik (minus upgrade guide,
>> publishing
>> > > >> > > whitelist
>> > > >> > > > > > >> plugins, and making it so that the default
>> > > >> > > > > > >> project
>> > template
>> > > >> > > includes
>> > > >> > > > > > >> <plugin name="cordova-plugin-whitelist" />).
>> > > >> > > > > > >> Maybe
>> let's
>> > > do
>> > > >> a RC
>> > > >> > > > while
>> > > >> > > > > > we
>> > > >> > > > > > >> wait on these things being finished up?
>> > > >> > > > > > >>
>> > > >> > > > > > >> If anyone wants to take on any of these tasks,
>> > > >> > > > > > >> that
>> would
>> > > be
>> > > >> > > > awesome.
>> > > >> > > > > > >>
>> > > >> > > > > > >> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <
>> > > shazron@gmail.com>
>> > > >> > > wrote:
>> > > >> > > > > > >>
>> > > >> > > > > > >> > +1 for vote thread, let's get this thing out so
>> people
>> > > >> (that
>> > > >> > are
>> > > >> > > > not
>> > > >> > > > > > >> > us) can test...
>> > > >> > > > > > >> >
>> > > >> > > > > > >> >
>> > > >> > > > > > >> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <
>> > > >> > bowserj@gmail.com>
>> > > >> > > > > > wrote:
>> > > >> > > > > > >> > > OK, this is a three month old thread, and
>> > > >> > > > > > >> > > we're
>> > waiting
>> > > >> on a
>> > > >> > > > > > >> discussion
>> > > >> > > > > > >> > > before we release something? I really think
>> > > >> > > > > > >> > > we
>> should
>> > > go
>> > > >> to
>> > > >> > a
>> > > >> > > > vote
>> > > >> > > > > > >> thread
>> > > >> > > > > > >> > > now that we have a legacy whitelist plugin
>> > > >> > > > > > >> > > and a
>> new
>> > > >> style
>> > > >> > > > > whitelist
>> > > >> > > > > > >> > > plugin. We shouldn't keep constantly
>> > > >> > > > > > >> > > delaying
>> this
>> > > >> release
>> > > >> > > > > because
>> > > >> > > > > > of
>> > > >> > > > > > >> > > what's happening on other platforms,
>> > > >> > > > > > >> > > especially
>> since
>> > > we
>> > > >> > > already
>> > > >> > > > > > >> > pluginized
>> > > >> > > > > > >> > > the whitelist.
>> > > >> > > > > > >> > >
>> > > >> > > > > > >> > > Can we please release soon?
>> > > >> > > > > > >> > >
>> > > >> > > > > > >> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil
>> > > >> > > > > > >> > > Khandelwal
>> <
>> > > >> > > > > > >> > nikhilkh@microsoft.com>
>> > > >> > > > > > >> > > wrote:
>> > > >> > > > > > >> > >
>> > > >> > > > > > >> > >> I know we discussed a couple of approaches
>> > > implementing
>> > > >> the
>> > > >> > > > > default
>> > > >> > > > > > >> > >> whitelist policy for Android/iOS - either
>> > > >> > > > > > >> > >> every
>> app
>> > > >> would
>> > > >> > be
>> > > >> > > > > > >> required to
>> > > >> > > > > > >> > >> include the whitelist plugin or have it have
>> smart
>> > > >> defaults
>> > > >> > > in
>> > > >> > > > > the
>> > > >> > > > > > >> > platform
>> > > >> > > > > > >> > >> implementation and the plugin being able to
>> override
>> > > >> them.
>> > > >> > > > > > >> > >>
>> > > >> > > > > > >> > >> I don’t think that thread closed with any
>> > conclusions.
>> > > >> > > > > > >> > >>
>> > > >> > > > > > >> > >> Thanks,
>> > > >> > > > > > >> > >> Nikhil
>> > > >> > > > > > >> > >>
>> > > >> > > > > > >> > >>
>> > > >> > > > > > >> > >> -----Original Message-----
>> > > >> > > > > > >> > >> From: Joe Bowser [mailto:bowserj@gmail.com]
>> > > >> > > > > > >> > >> Sent: Thursday, March 12, 2015 11:23 AM
>> > > >> > > > > > >> > >> To: dev
>> > > >> > > > > > >> > >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0
>> Release
>> > > >> > > > > > >> > >>
>> > > >> > > > > > >> > >> OK, so right now it's just docs? How soon
>> > > >> > > > > > >> > >> can we
>> > get a
>> > > >> VOTE
>> > > >> > > > > thread
>> > > >> > > > > > >> > started
>> > > >> > > > > > >> > >> for 4.0.0?
>> > > >> > > > > > >> > >>
>> > > >> > > > > > >> > >> On Wed, Mar 4, 2015 at 10:47 AM Andrew
>> > > >> > > > > > >> > >> Grieve <
>> > > >> > > > > > agrieve@chromium.org>
>> > > >> > > > > > >> > >> wrote:
>> > > >> > > > > > >> > >>
>> > > >> > > > > > >> > >> > mobilespec is now working again... Took
>> > > >> > > > > > >> > >> > longer
>> > than
>> > > I
>> > > >> > would
>> > > >> > > > > have
>> > > >> > > > > > >> > >> > liked, but did you know that on Android
>> FileReader
>> > > >> > triggers
>> > > >> > > > > > >> > >> > shouldInterceptRequest() with Blob URLs!?
>> > > >> > > > > > >> > >> >
>> > > >> > > > > > >> > >> > Separate thread is already happening re:
>> > whitelists,
>> > > >> so
>> > > >> > > once
>> > > >> > > > > > that's
>> > > >> > > > > > >> > >> > figured out, it's just docs afaict.
>> > > >> > > > > > >> > >> >
>> > > >> > > > > > >> > >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian
>> > > >> > > > > > >> > >> > Clelland <
>> > > >> > > > > > >> iclelland@chromium.org
>> > > >> > > > > > >> > >
>> > > >> > > > > > >> > >> > wrote:
>> > > >> > > > > > >> > >> >
>> > > >> > > > > > >> > >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <
>> > > >> > > > > purplecabbage@gmail.com
>> > > >> > > > > > >
>> > > >> > > > > > >> > wrote:
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > > > We should start a new whitelist plugin
>> related
>> > > >> > thread.
>> > > >> > > > > > >> > >> > > >
>> > > >> > > > > > >> > >> > > > Why is a plugin blocking a release?
>> Default
>> > > (aka
>> > > >> > > > > no-plugin)
>> > > >> > > > > > >> > >> > > > behavior should be to allow all
>> > > >> > > > > > >> > >> > > > network
>> > requests
>> > > >> > > > shouldn't
>> > > >> > > > > > it?
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > > Well, that just might be a blacklist
>> > > >> > > > > > >> > >> > > then :)
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > > > This thread is a month long, and not
>> > > >> > > > > > >> > >> > > > the first discussion of
>> > > 4.0.0
>> > > >> for
>> > > >> > > > > > Android.
>> > > >> > > > > > >> > >> > > >
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > > Seriously, though -- the whitelist
>> discussion is
>> > > >> much
>> > > >> > > > longer
>> > > >> > > > > > than
>> > > >> > > > > > >> > >> > > that,
>> > > >> > > > > > >> > >> > and
>> > > >> > > > > > >> > >> > > this isn't the first time that the
>> > > >> > > > > > >> > >> > > default
>> > > >> > > > no-network-access
>> > > >> > > > > > >> policy
>> > > >> > > > > > >> > >> > > has been brought up:
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > > (Here's the first question, from *July*:
>> > > >> > > > > > >> > >> > > http://markmail.org/message/t4vj4saisem2
>> > > >> > > > > > >> > >> > > mcgw Here's where I mentioned what the
>> > > >> > > > > > >> > >> > > implemented
>> > > policy
>> > > >> > was:
>> > > >> > > > > > >> > >> > > http://markmail.org/message/s4necfnh4hnb
>> > > >> > > > > > >> > >> > > lpjm And in another discussion:
>> > > >> > > > > > >> > >> > > http://markmail.org/message/ap7syhqysizm
>> > > >> > > > > > >> > >> > > svrz
>> )
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > > If we want to reconsider that decision,
>> > > >> > > > > > >> > >> > > then
>> we
>> > > >> should
>> > > >> > > > > > certainly
>> > > >> > > > > > >> do
>> > > >> > > > > > >> > >> > > so before we cut a release. I think it
>> > > >> > > > > > >> > >> > > would
>> be
>> > a
>> > > >> real
>> > > >> > > > > problem
>> > > >> > > > > > to
>> > > >> > > > > > >> > >> > > change it afterwards, so let's get it right.
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > > Also, it's not the plugin itself that's
>> blocking
>> > > the
>> > > >> > > > release,
>> > > >> > > > > > >> it's
>> > > >> > > > > > >> > >> > > us making sure that we've implemented
>> > > >> > > > > > >> > >> > > the
>> core
>> > > hooks
>> > > >> > > > > correctly
>> > > >> > > > > > so
>> > > >> > > > > > >> > >> > > that the plugin can actually do its job,
>> > > >> > > > > > >> > >> > > and
>> > that
>> > > >> > people
>> > > >> > > > who
>> > > >> > > > > > >> don't
>> > > >> > > > > > >> > >> > > want that particular plugin can make a
>> > > >> > > > > > >> > >> > > better
>> > one.
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > > (It is also an issue that a plugin,
>> > > >> > > > > > >> > >> > > required
>> for
>> > > >> > > > > > cordova-android
>> > > >> > > > > > >> > >> > > 4.0.0, breaks apps which are also
>> > > >> > > > > > >> > >> > > building
>> for
>> > > >> > > cordova-ios
>> > > >> > > > > > 3.8.0.
>> > > >> > > > > > >> > >> > > I'll take a
>> > > >> > > > > > >> > >> > look
>> > > >> > > > > > >> > >> > > at that, and either remove the
>> > > >> > > > > > >> > >> > > ios-native
>> > portions
>> > > >> of
>> > > >> > the
>> > > >> > > > > > >> whitelist
>> > > >> > > > > > >> > >> > plugin,
>> > > >> > > > > > >> > >> > > or neuter it so that it doesn't
>> > > >> > > > > > >> > >> > > interfere
>> with
>> > an
>> > > >> ios
>> > > >> > app
>> > > >> > > > if
>> > > >> > > > > > it's
>> > > >> > > > > > >> > >> > > not on the unplug-whitelist branch of
>> > > >> > > > > > >> > >> > > that
>> > repo.)
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > > Ian
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > > > @purplecabbage risingj.com
>> > > >> > > > > > >> > >> > > >
>> > > >> > > > > > >> > >> > > > On Mon, Mar 2, 2015 at 2:02 PM,
>> > > >> > > > > > >> > >> > > > Shazron <
>> > > >> > > > shazron@gmail.com
>> > > >> > > > > >
>> > > >> > > > > > >> > wrote:
>> > > >> > > > > > >> > >> > > >
>> > > >> > > > > > >> > >> > > > > legacy-whitelist-plugin should be
>> > > >> > > > > > >> > >> > > > > fixed
>> so
>> > > that
>> > > >> it
>> > > >> > > > > compiles
>> > > >> > > > > > >> on
>> > > >> > > > > > >> > >> > > > > cordova-ios@3.8.0. It shouldn't be a
>> > problem
>> > > to
>> > > >> > fix
>> > > >> > > > this
>> > > >> > > > > > at
>> > > >> > > > > > >> > >> > > > > compile
>> > > >> > > > > > >> > >> > or
>> > > >> > > > > > >> > >> > > > > run-time (whichever is applicable
>> > > >> > > > > > >> > >> > > > > here
>> > related
>> > > >> to
>> > > >> > the
>> > > >> > > > > > compile
>> > > >> > > > > > >> > >> > > > > error)
>> > > >> > > > > > >> > >> > > > >
>> > > >> > > > > > >> > >> > > > > On Mon, Mar 2, 2015 at 1:47 PM,
>> > > >> > > > > > >> > >> > > > > Darryl
>> Pogue
>> > > >> > > > > > >> > >> > > > > <dv...@gmail.com>
>> > > >> > > > > > >> > >> > > > wrote:
>> > > >> > > > > > >> > >> > > > > > On 2 March 2015 at 13:37, Joe
>> > > >> > > > > > >> > >> > > > > > Bowser <
>> > > >> > > > > bowserj@gmail.com>
>> > > >> > > > > > >> > wrote:
>> > > >> > > > > > >> > >> > > > > >> So, right now the whitelist
>> > > >> > > > > > >> > >> > > > > >> changes
>> are
>> > > >> what's
>> > > >> > > > holding
>> > > >> > > > > > up
>> > > >> > > > > > >> the
>> > > >> > > > > > >> > >> > 4.0.0
>> > > >> > > > > > >> > >> > > > > release
>> > > >> > > > > > >> > >> > > > > >> now? Is this really the only
>> > > >> > > > > > >> > >> > > > > >> thing
>> > that's
>> > > >> > holding
>> > > >> > > > up
>> > > >> > > > > > this
>> > > >> > > > > > >> > >> > release?
>> > > >> > > > > > >> > >> > > > > >>
>> > > >> > > > > > >> > >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM
>> Andrew
>> > > >> Grieve <
>> > > >> > > > > > >> > >> > > agrieve@chromium.org>
>> > > >> > > > > > >> > >> > > > > wrote:
>> > > >> > > > > > >> > >> > > > > >>
>> > > >> > > > > > >> > >> > > > > >>> I think we'll also need to
>> > > >> > > > > > >> > >> > > > > >>> finish
>> with
>> > the
>> > > >> > > > whitelist
>> > > >> > > > > > >> changes
>> > > >> > > > > > >> > >> > > > > >>> &
>> > > >> > > > > > >> > >> > have
>> > > >> > > > > > >> > >> > > > > both
>> > > >> > > > > > >> > >> > > > > >>> the legacy and new-way whitelist
>> plugins
>> > > >> > released
>> > > >> > > > > > before
>> > > >> > > > > > >> we
>> > > >> > > > > > >> > >> > > > > >>> can
>> > > >> > > > > > >> > >> > do
>> > > >> > > > > > >> > >> > > a
>> > > >> > > > > > >> > >> > > > > 4.0.0
>> > > >> > > > > > >> > >> > > > > >>> release (otherwise you wouldn't
>> > > >> > > > > > >> > >> > > > > >>> be
>> able
>> > to
>> > > >> > write
>> > > >> > > an
>> > > >> > > > > app
>> > > >> > > > > > >> that
>> > > >> > > > > > >> > >> > > > > >>> hits
>> > > >> > > > > > >> > >> > > the
>> > > >> > > > > > >> > >> > > > > >>> network)
>> > > >> > > > > > >> > >> > > > > >>>
>> > > >> > > > > > >> > >> > > > > >
>> > > >> > > > > > >> > >> > > > > > Just FYI, the whitelist stuff is
>> proving
>> > to
>> > > >> be a
>> > > >> > > bit
>> > > >> > > > > of a
>> > > >> > > > > > >> pain
>> > > >> > > > > > >> > >> > point.
>> > > >> > > > > > >> > >> > > > > > I'm using cordova-android@master,
>> > > >> > > > > > >> > >> > > > > > and
>> > need
>> > > to
>> > > >> > > > install
>> > > >> > > > > > the
>> > > >> > > > > > >> > >> > > > > > legacy-whitelist plugin in order
>> > > >> > > > > > >> > >> > > > > > to
>> make
>> > > >> network
>> > > >> > > > > > requests.
>> > > >> > > > > > >> > >> > > > > > Once the plugin is installed,
>> everything
>> > > >> seems to
>> > > >> > > > work.
>> > > >> > > > > > >> > >> > > > > >
>> > > >> > > > > > >> > >> > > > > > The problem is that the
>> legacy-whitelist
>> > > >> plugin
>> > > >> > > > > generates
>> > > >> > > > > > >> > >> > > > > > compile errors with
>> > > >> > > > > > >> > >> > > > > > cordova-ios@3.8.0,
>> so
>> > > >> now I
>> > > >> > > > can't
>> > > >> > > > > > just
>> > > >> > > > > > >> > run
>> > > >> > > > > > >> > >> > > > > > `cordova build`, I need to split
>> > > >> > > > > > >> > >> > > > > > the
>> > > >> platforms up
>> > > >> > > and
>> > > >> > > > > > >> > >> > > > > > install/uninstall the plugin in
>> between.
>> > If
>> > > >> > someone
>> > > >> > > > > > makes a
>> > > >> > > > > > >> > >> > > > > > dev build for Android and forgets
>> > > >> > > > > > >> > >> > > > > > the
>> > > plugin,
>> > > >> it
>> > > >> > > will
>> > > >> > > > > > >> appear
>> > > >> > > > > > >> > >> > > > > > to build successfully but not
>> > > >> > > > > > >> > >> > > > > > actually
>> > > >> function
>> > > >> > > > > properly
>> > > >> > > > > > >> due
>> > > >> > > > > > >> > to
>> > > >> > > > > > >> > >> the whitelist.
>> > > >> > > > > > >> > >> > > > > >
>> > > >> > > > > > >> > >> > > > > > I know, this is all pre-release,
>> > > >> > > > > > >> > >> > > > > > so
>> pain
>> > is
>> > > >> > > somewhat
>> > > >> > > > > > >> expected
>> > > >> > > > > > >> > >> > > > > > right now. I'm worried about the
>> > > >> > > > > > >> > >> > > > > > case
>> > where
>> > > >> > > > > > >> > >> > > > > > cordova-android@4.0.0 is released
>> > > >> > > > > > >> > >> > > > > > and
>> > > >> > > > > cordova-ios@3.8.0
>> > > >> > > > > > is
>> > > >> > > > > > >> > >> > > > > > still current, and how people
>> > > >> > > > > > >> > >> > can
>> > > >> > > > > > >> > >> > > > > > avoid whitelist breakage there.
>> > > >> > > > > > >> > >> > > > > >
>> > > >> > > > > > >> > >> > > > > >
>> > > >> > > > > > >> ------------------------------
>> > > ------------------------------
>> > > >> > > > > > >> > >> > ---------
>> > > >> > > > > > >> > >> > > > > > To unsubscribe, e-mail:
>> > > >> > > > > > dev-unsubscribe@cordova.apache.org
>> > > >> > > > > > >> > >> > > > > > For additional commands, e-mail:
>> > > >> > > > > > >> dev-help@cordova.apache.org
>> > > >> > > > > > >> > >> > > > > >
>> > > >> > > > > > >> > >> > > > >
>> > > >> > > > > > >> > >> > > > >
>> > > >> > > > > >
>> ------------------------------------------------------------
>> > > >> > > > > > >> > >> > ---------
>> > > >> > > > > > >> > >> > > > > To unsubscribe, e-mail:
>> > > >> > > > > dev-unsubscribe@cordova.apache.org
>> > > >> > > > > > >> > >> > > > > For additional commands, e-mail:
>> > > >> > > > > > dev-help@cordova.apache.org
>> > > >> > > > > > >> > >> > > > >
>> > > >> > > > > > >> > >> > > > >
>> > > >> > > > > > >> > >> > > >
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> >
>> > > >> > > > > > >> > >>
>> > > >> > > > > > >> >
>> > > >> > > > > > >> >
>> > > >> > > > >
>> > > >>
>> ---------------------------------------------------------------------
>> > > >> > > > > > >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.
>> > > apache.org
>> > > >> > > > > > >> > For additional commands, e-mail:
>> > > >> dev-help@cordova.apache.org
>> > > >> > > > > > >> >
>> > > >> > > > > > >> >
>> > > >> > > > > > >>
>> > > >> > > > > > >
>> > > >> > > > > > >
>> > > >> > > > > >
>> > > >> > > > >
>> > > >> > > > >
>> > > >> > > > >
>> > > >> > > > > --
>> > > >> > > > > Carlos Santana
>> > > >> > > > > <cs...@gmail.com>
>> > > >> > > > >
>> > > >> > > >
>> > > >> > >
>> > > >> >
>> > > >>
>> > > >
>> > > >
>> > >
>> >
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Certainly makes you notice though. You're free to have an empty CSP tag,
and the plugin docs are full of copy/pastable examples:
https://github.com/apache/cordova-plugin-whitelist/blob/master/README.md
I do think that since CSP is our main way of enforcing whitelists going
forward, that we should be loud in raising awareness of them.
On Thu, Apr 9, 2015 at 2:47 PM, Serge Huijben <s....@gmail.com> wrote:
> Then, it seems strange to me that it logs an error and repeated warnings if
> the meta tag is missing. Perhaps we should remove that from the plugin.
>
> Op do 9 apr. 2015 om 20:21 schreef Ian Clelland <ic...@chromium.org>
>
> > Moving from [VOTE] thread:
> >
> > On Thu, Apr 9, 2015 at 1:44 PM, Serge Huijben <s....@gmail.com>
> wrote:
> >
> >> But why is the meta csp tag required?
> >
> >
> > It's not required, only recommended. It's more secure, as it can restrict
> > more network access than the whitelist itself is capable of. (streaming
> > <audio> and <video> tags, for instance).
> >
> > On Thu, Apr 9, 2015 at 1:44 PM, Treggiari, Leo <le...@intel.com>
> > wrote:
> >
> >> Another question, based upon my understanding, which must be wrong!
> >
> >
> >>
> >> The 4.0.0 Android Release will require the cordova-plugin-whitelist in
> >> order
> >> to get a whitelist implemented correctly.
> >>
> >> Given its name (dash-style) it is only available as an node component.
> >>
> >> The is no released CLI that knows how to fetch from npm?
> >> Or does 4.3, even though I don't see it in the release notes?
> >> Even so, there are many previous CLI releases which will not work?
> >>
> >
> > This is at least partly resolved by the fact that no released CLI points
> > to cordova-android 4.0.0. Once 4.0.0 is released. we will be able to
> > release a version of the CLI which downloads it by default.
> >
> > The whitelist plugins are published already, and discussion is underway
> > about voting/releasing cordova-lib (and accompanying tools), so I think
> > there are only two possible timelines:
> >
> > A) whitelist plugins released, then cordova-android 4 released, then
> tools
> > released (supports NPM plugins and Android 4).
> >
> > B) plugins released, then tools released (supports NPM plugins), then
> > cordova-android 4 released, then a small bump of tools is released (to
> pin
> > to cordova-android 4)
> >
> > In either case, users of the released CLI always have a version which
> > works.
> >
> >
> >> It would be good for the release notes to explain the situation.
> >>
> >> Leo
> >>
> >
> > On Thu, Apr 9, 2015 at 1:24 PM, Michal Mocny <mm...@chromium.org>
> wrote:
> >
> >> Splashscreens was mentioned, icons was not. I don't think there is an
> >> icons change?
> >>
> >> On Thu, Apr 9, 2015 at 1:17 PM, Joe Bowser <bo...@gmail.com> wrote:
> >>
> >> > So, wasn't there a change regarding icons and spashscreens being
> moved?
> >> I
> >> > have no idea if we want to add that, or if adding that should happen
> >> after
> >> > the release?
> >> >
> >> > On Wed, Apr 8, 2015 at 7:09 PM Andrew Grieve <ag...@chromium.org>
> >> wrote:
> >> >
> >> > > CB-8684 is now merged and I've updated the targetSdk (and made a
> >> couple
> >> > > other changes).
> >> > >
> >> > > I'll start the release process in the morning as long as there no
> >> > > objections.
> >> > >
> >> > >
> >> > > On Tue, Apr 7, 2015 at 2:20 PM, Andrew Grieve <agrieve@chromium.org
> >
> >> > > wrote:
> >> > >
> >> > > > I'll start on it once CB-8684 lands (Tony - assuming you'll have
> >> this
> >> > > done
> >> > > > shortly and would prefer it lands?)
> >> > > >
> >> > > > On Tue, Apr 7, 2015 at 1:33 PM, Jesse <pu...@gmail.com>
> >> wrote:
> >> > > >
> >> > > >> Sweet!
> >> > > >>
> >> > > >> @purplecabbage
> >> > > >> risingj.com
> >> > > >>
> >> > > >> On Tue, Apr 7, 2015 at 8:35 AM, Andrew Grieve <
> >> agrieve@chromium.org>
> >> > > >> wrote:
> >> > > >>
> >> > > >> > Let's do it!
> >> > > >> >
> >> > > >> > On Mon, Apr 6, 2015 at 7:33 PM, Joe Bowser <bo...@gmail.com>
> >> > wrote:
> >> > > >> >
> >> > > >> > > So, I think we should put off the embedder's guide until
> after
> >> the
> >> > > >> > > release. A lot of it has changed, and since we're still
> >> > technically
> >> > > >> > > obligated to support the 3.x release tree for six months,
> that
> >> > > should
> >> > > >> buy
> >> > > >> > > us some time to figure out how that is going to work.
> Getting
> >> > > >> Cordova to
> >> > > >> > > work with a vanilla Android Studio project is a non-trivial
> >> task.
> >> > > >> > >
> >> > > >> > > Given that everything else appears to be done, should we
> start
> >> > > voting
> >> > > >> on
> >> > > >> > an
> >> > > >> > > RC for this? What do people think?
> >> > > >> > >
> >> > > >> > >
> >> > > >> > >
> >> > > >> > > On Thu, Mar 19, 2015 at 10:31 AM Andrew Grieve <
> >> > > agrieve@chromium.org>
> >> > > >> > > wrote:
> >> > > >> > >
> >> > > >> > > > Here's issues:
> >> > > >> > > > https://issues.apache.org/jira/browse/CB-8715 (docs)
> >> > > >> > > > https://issues.apache.org/jira/browse/CB-8716 (whitelist)
> >> > > >> > > > https://issues.apache.org/jira/browse/CB-8717 (write
> >> > > >> RELEASENOTES.md)
> >> > > >> > > >
> >> > > >> > > > On Tue, Mar 17, 2015 at 10:15 AM, Carlos Santana <
> >> > > >> csantana23@gmail.com
> >> > > >> > >
> >> > > >> > > > wrote:
> >> > > >> > > >
> >> > > >> > > > > I would say let's start RC testing and voting, But not
> pin
> >> the
> >> > > >> > version
> >> > > >> > > in
> >> > > >> > > > > Cordova CLI until the tasks that Andrew mentioned are
> done.
> >> > > >> > > > > Andrew can you create the JIRA Items for the tasks that
> >> need
> >> > to
> >> > > be
> >> > > >> > > done.
> >> > > >> > > > I
> >> > > >> > > > > thought there was a discussion about creating JIRA Items
> to
> >> > help
> >> > > >> > track
> >> > > >> > > > and
> >> > > >> > > > > know what's left for release something.
> >> > > >> > > > >
> >> > > >> > > > > - upgrade guide,
> >> > > >> > > > > - publishing whitelist plugins,
> >> > > >> > > > > - and making it so that the default project template
> >> includes
> >> > > >> <plugin
> >> > > >> > > > > name="cordova-plugin-whitelist" />)
> >> > > >> > > > >
> >> > > >> > > > >
> >> > > >> > > > > On Mon, Mar 16, 2015 at 11:21 PM, Ian Clelland <
> >> > > >> > iclelland@chromium.org
> >> > > >> > > >
> >> > > >> > > > > wrote:
> >> > > >> > > > >
> >> > > >> > > > > > We'll probably need at least an RC for the whitelist
> >> plugin,
> >> > > if
> >> > > >> > not a
> >> > > >> > > > > vote,
> >> > > >> > > > > > to be able to vote on this.
> >> > > >> > > > > >
> >> > > >> > > > > > Or can we just include instructions like "Use
> >> > > >> > > > > > cordova-plugin-whitelist@f70b1bc for testing" while we
> >> > start
> >> > > >> the
> >> > > >> > > > > official
> >> > > >> > > > > > release process for the plugins?
> >> > > >> > > > > >
> >> > > >> > > > > > On Mon, Mar 16, 2015 at 11:17 PM, Ian Clelland <
> >> > > >> > > iclelland@chromium.org
> >> > > >> > > > >
> >> > > >> > > > > > wrote:
> >> > > >> > > > > >
> >> > > >> > > > > > > +1 -- Let's get this out the door :)
> >> > > >> > > > > > > I'll see what I can get done to move it in that
> >> direction.
> >> > > >> > > > > > >
> >> > > >> > > > > > > On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <
> >> > > >> > > agrieve@chromium.org
> >> > > >> > > > >
> >> > > >> > > > > > > wrote:
> >> > > >> > > > > > >
> >> > > >> > > > > > >> Everything's ready afaik (minus upgrade guide,
> >> publishing
> >> > > >> > > whitelist
> >> > > >> > > > > > >> plugins, and making it so that the default project
> >> > template
> >> > > >> > > includes
> >> > > >> > > > > > >> <plugin name="cordova-plugin-whitelist" />). Maybe
> >> let's
> >> > > do
> >> > > >> a RC
> >> > > >> > > > while
> >> > > >> > > > > > we
> >> > > >> > > > > > >> wait on these things being finished up?
> >> > > >> > > > > > >>
> >> > > >> > > > > > >> If anyone wants to take on any of these tasks, that
> >> would
> >> > > be
> >> > > >> > > > awesome.
> >> > > >> > > > > > >>
> >> > > >> > > > > > >> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <
> >> > > shazron@gmail.com>
> >> > > >> > > wrote:
> >> > > >> > > > > > >>
> >> > > >> > > > > > >> > +1 for vote thread, let's get this thing out so
> >> people
> >> > > >> (that
> >> > > >> > are
> >> > > >> > > > not
> >> > > >> > > > > > >> > us) can test...
> >> > > >> > > > > > >> >
> >> > > >> > > > > > >> >
> >> > > >> > > > > > >> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <
> >> > > >> > bowserj@gmail.com>
> >> > > >> > > > > > wrote:
> >> > > >> > > > > > >> > > OK, this is a three month old thread, and we're
> >> > waiting
> >> > > >> on a
> >> > > >> > > > > > >> discussion
> >> > > >> > > > > > >> > > before we release something? I really think we
> >> should
> >> > > go
> >> > > >> to
> >> > > >> > a
> >> > > >> > > > vote
> >> > > >> > > > > > >> thread
> >> > > >> > > > > > >> > > now that we have a legacy whitelist plugin and a
> >> new
> >> > > >> style
> >> > > >> > > > > whitelist
> >> > > >> > > > > > >> > > plugin. We shouldn't keep constantly delaying
> >> this
> >> > > >> release
> >> > > >> > > > > because
> >> > > >> > > > > > of
> >> > > >> > > > > > >> > > what's happening on other platforms, especially
> >> since
> >> > > we
> >> > > >> > > already
> >> > > >> > > > > > >> > pluginized
> >> > > >> > > > > > >> > > the whitelist.
> >> > > >> > > > > > >> > >
> >> > > >> > > > > > >> > > Can we please release soon?
> >> > > >> > > > > > >> > >
> >> > > >> > > > > > >> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil
> Khandelwal
> >> <
> >> > > >> > > > > > >> > nikhilkh@microsoft.com>
> >> > > >> > > > > > >> > > wrote:
> >> > > >> > > > > > >> > >
> >> > > >> > > > > > >> > >> I know we discussed a couple of approaches
> >> > > implementing
> >> > > >> the
> >> > > >> > > > > default
> >> > > >> > > > > > >> > >> whitelist policy for Android/iOS - either every
> >> app
> >> > > >> would
> >> > > >> > be
> >> > > >> > > > > > >> required to
> >> > > >> > > > > > >> > >> include the whitelist plugin or have it have
> >> smart
> >> > > >> defaults
> >> > > >> > > in
> >> > > >> > > > > the
> >> > > >> > > > > > >> > platform
> >> > > >> > > > > > >> > >> implementation and the plugin being able to
> >> override
> >> > > >> them.
> >> > > >> > > > > > >> > >>
> >> > > >> > > > > > >> > >> I don’t think that thread closed with any
> >> > conclusions.
> >> > > >> > > > > > >> > >>
> >> > > >> > > > > > >> > >> Thanks,
> >> > > >> > > > > > >> > >> Nikhil
> >> > > >> > > > > > >> > >>
> >> > > >> > > > > > >> > >>
> >> > > >> > > > > > >> > >> -----Original Message-----
> >> > > >> > > > > > >> > >> From: Joe Bowser [mailto:bowserj@gmail.com]
> >> > > >> > > > > > >> > >> Sent: Thursday, March 12, 2015 11:23 AM
> >> > > >> > > > > > >> > >> To: dev
> >> > > >> > > > > > >> > >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0
> >> Release
> >> > > >> > > > > > >> > >>
> >> > > >> > > > > > >> > >> OK, so right now it's just docs? How soon can
> we
> >> > get a
> >> > > >> VOTE
> >> > > >> > > > > thread
> >> > > >> > > > > > >> > started
> >> > > >> > > > > > >> > >> for 4.0.0?
> >> > > >> > > > > > >> > >>
> >> > > >> > > > > > >> > >> On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <
> >> > > >> > > > > > agrieve@chromium.org>
> >> > > >> > > > > > >> > >> wrote:
> >> > > >> > > > > > >> > >>
> >> > > >> > > > > > >> > >> > mobilespec is now working again... Took
> longer
> >> > than
> >> > > I
> >> > > >> > would
> >> > > >> > > > > have
> >> > > >> > > > > > >> > >> > liked, but did you know that on Android
> >> FileReader
> >> > > >> > triggers
> >> > > >> > > > > > >> > >> > shouldInterceptRequest() with Blob URLs!?
> >> > > >> > > > > > >> > >> >
> >> > > >> > > > > > >> > >> > Separate thread is already happening re:
> >> > whitelists,
> >> > > >> so
> >> > > >> > > once
> >> > > >> > > > > > that's
> >> > > >> > > > > > >> > >> > figured out, it's just docs afaict.
> >> > > >> > > > > > >> > >> >
> >> > > >> > > > > > >> > >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian
> Clelland <
> >> > > >> > > > > > >> iclelland@chromium.org
> >> > > >> > > > > > >> > >
> >> > > >> > > > > > >> > >> > wrote:
> >> > > >> > > > > > >> > >> >
> >> > > >> > > > > > >> > >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <
> >> > > >> > > > > purplecabbage@gmail.com
> >> > > >> > > > > > >
> >> > > >> > > > > > >> > wrote:
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > > > We should start a new whitelist plugin
> >> related
> >> > > >> > thread.
> >> > > >> > > > > > >> > >> > > >
> >> > > >> > > > > > >> > >> > > > Why is a plugin blocking a release?
> >> Default
> >> > > (aka
> >> > > >> > > > > no-plugin)
> >> > > >> > > > > > >> > >> > > > behavior should be to allow all network
> >> > requests
> >> > > >> > > > shouldn't
> >> > > >> > > > > > it?
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > > Well, that just might be a blacklist then
> :)
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > > > This thread is a
> >> > > >> > > > > > >> > >> > > > month long, and not the first discussion
> of
> >> > > 4.0.0
> >> > > >> for
> >> > > >> > > > > > Android.
> >> > > >> > > > > > >> > >> > > >
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > > Seriously, though -- the whitelist
> >> discussion is
> >> > > >> much
> >> > > >> > > > longer
> >> > > >> > > > > > than
> >> > > >> > > > > > >> > >> > > that,
> >> > > >> > > > > > >> > >> > and
> >> > > >> > > > > > >> > >> > > this isn't the first time that the default
> >> > > >> > > > no-network-access
> >> > > >> > > > > > >> policy
> >> > > >> > > > > > >> > >> > > has been brought up:
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > > (Here's the first question, from *July*:
> >> > > >> > > > > > >> > >> > >
> http://markmail.org/message/t4vj4saisem2mcgw
> >> > > >> > > > > > >> > >> > > Here's where I mentioned what the
> implemented
> >> > > policy
> >> > > >> > was:
> >> > > >> > > > > > >> > >> > >
> http://markmail.org/message/s4necfnh4hnblpjm
> >> > > >> > > > > > >> > >> > > And in another discussion:
> >> > > >> > > > > > >> > >> > >
> http://markmail.org/message/ap7syhqysizmsvrz
> >> )
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > > If we want to reconsider that decision,
> then
> >> we
> >> > > >> should
> >> > > >> > > > > > certainly
> >> > > >> > > > > > >> do
> >> > > >> > > > > > >> > >> > > so before we cut a release. I think it
> would
> >> be
> >> > a
> >> > > >> real
> >> > > >> > > > > problem
> >> > > >> > > > > > to
> >> > > >> > > > > > >> > >> > > change it afterwards, so let's get it
> right.
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > > Also, it's not the plugin itself that's
> >> blocking
> >> > > the
> >> > > >> > > > release,
> >> > > >> > > > > > >> it's
> >> > > >> > > > > > >> > >> > > us making sure that we've implemented the
> >> core
> >> > > hooks
> >> > > >> > > > > correctly
> >> > > >> > > > > > so
> >> > > >> > > > > > >> > >> > > that the plugin can actually do its job,
> and
> >> > that
> >> > > >> > people
> >> > > >> > > > who
> >> > > >> > > > > > >> don't
> >> > > >> > > > > > >> > >> > > want that particular plugin can make a
> better
> >> > one.
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > > (It is also an issue that a plugin,
> required
> >> for
> >> > > >> > > > > > cordova-android
> >> > > >> > > > > > >> > >> > > 4.0.0, breaks apps which are also building
> >> for
> >> > > >> > > cordova-ios
> >> > > >> > > > > > 3.8.0.
> >> > > >> > > > > > >> > >> > > I'll take a
> >> > > >> > > > > > >> > >> > look
> >> > > >> > > > > > >> > >> > > at that, and either remove the ios-native
> >> > portions
> >> > > >> of
> >> > > >> > the
> >> > > >> > > > > > >> whitelist
> >> > > >> > > > > > >> > >> > plugin,
> >> > > >> > > > > > >> > >> > > or neuter it so that it doesn't interfere
> >> with
> >> > an
> >> > > >> ios
> >> > > >> > app
> >> > > >> > > > if
> >> > > >> > > > > > it's
> >> > > >> > > > > > >> > >> > > not on the unplug-whitelist branch of that
> >> > repo.)
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > > Ian
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> > > > @purplecabbage
> >> > > >> > > > > > >> > >> > > > risingj.com
> >> > > >> > > > > > >> > >> > > >
> >> > > >> > > > > > >> > >> > > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <
> >> > > >> > > > shazron@gmail.com
> >> > > >> > > > > >
> >> > > >> > > > > > >> > wrote:
> >> > > >> > > > > > >> > >> > > >
> >> > > >> > > > > > >> > >> > > > > legacy-whitelist-plugin should be fixed
> >> so
> >> > > that
> >> > > >> it
> >> > > >> > > > > compiles
> >> > > >> > > > > > >> on
> >> > > >> > > > > > >> > >> > > > > cordova-ios@3.8.0. It shouldn't be a
> >> > problem
> >> > > to
> >> > > >> > fix
> >> > > >> > > > this
> >> > > >> > > > > > at
> >> > > >> > > > > > >> > >> > > > > compile
> >> > > >> > > > > > >> > >> > or
> >> > > >> > > > > > >> > >> > > > > run-time (whichever is applicable here
> >> > related
> >> > > >> to
> >> > > >> > the
> >> > > >> > > > > > compile
> >> > > >> > > > > > >> > >> > > > > error)
> >> > > >> > > > > > >> > >> > > > >
> >> > > >> > > > > > >> > >> > > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl
> >> Pogue
> >> > > >> > > > > > >> > >> > > > > <dv...@gmail.com>
> >> > > >> > > > > > >> > >> > > > wrote:
> >> > > >> > > > > > >> > >> > > > > > On 2 March 2015 at 13:37, Joe Bowser
> <
> >> > > >> > > > > bowserj@gmail.com>
> >> > > >> > > > > > >> > wrote:
> >> > > >> > > > > > >> > >> > > > > >> So, right now the whitelist changes
> >> are
> >> > > >> what's
> >> > > >> > > > holding
> >> > > >> > > > > > up
> >> > > >> > > > > > >> the
> >> > > >> > > > > > >> > >> > 4.0.0
> >> > > >> > > > > > >> > >> > > > > release
> >> > > >> > > > > > >> > >> > > > > >> now? Is this really the only thing
> >> > that's
> >> > > >> > holding
> >> > > >> > > > up
> >> > > >> > > > > > this
> >> > > >> > > > > > >> > >> > release?
> >> > > >> > > > > > >> > >> > > > > >>
> >> > > >> > > > > > >> > >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM
> >> Andrew
> >> > > >> Grieve <
> >> > > >> > > > > > >> > >> > > agrieve@chromium.org>
> >> > > >> > > > > > >> > >> > > > > wrote:
> >> > > >> > > > > > >> > >> > > > > >>
> >> > > >> > > > > > >> > >> > > > > >>> I think we'll also need to finish
> >> with
> >> > the
> >> > > >> > > > whitelist
> >> > > >> > > > > > >> changes
> >> > > >> > > > > > >> > >> > > > > >>> &
> >> > > >> > > > > > >> > >> > have
> >> > > >> > > > > > >> > >> > > > > both
> >> > > >> > > > > > >> > >> > > > > >>> the legacy and new-way whitelist
> >> plugins
> >> > > >> > released
> >> > > >> > > > > > before
> >> > > >> > > > > > >> we
> >> > > >> > > > > > >> > >> > > > > >>> can
> >> > > >> > > > > > >> > >> > do
> >> > > >> > > > > > >> > >> > > a
> >> > > >> > > > > > >> > >> > > > > 4.0.0
> >> > > >> > > > > > >> > >> > > > > >>> release (otherwise you wouldn't be
> >> able
> >> > to
> >> > > >> > write
> >> > > >> > > an
> >> > > >> > > > > app
> >> > > >> > > > > > >> that
> >> > > >> > > > > > >> > >> > > > > >>> hits
> >> > > >> > > > > > >> > >> > > the
> >> > > >> > > > > > >> > >> > > > > >>> network)
> >> > > >> > > > > > >> > >> > > > > >>>
> >> > > >> > > > > > >> > >> > > > > >
> >> > > >> > > > > > >> > >> > > > > > Just FYI, the whitelist stuff is
> >> proving
> >> > to
> >> > > >> be a
> >> > > >> > > bit
> >> > > >> > > > > of a
> >> > > >> > > > > > >> pain
> >> > > >> > > > > > >> > >> > point.
> >> > > >> > > > > > >> > >> > > > > > I'm using cordova-android@master,
> and
> >> > need
> >> > > to
> >> > > >> > > > install
> >> > > >> > > > > > the
> >> > > >> > > > > > >> > >> > > > > > legacy-whitelist plugin in order to
> >> make
> >> > > >> network
> >> > > >> > > > > > requests.
> >> > > >> > > > > > >> > >> > > > > > Once the plugin is installed,
> >> everything
> >> > > >> seems to
> >> > > >> > > > work.
> >> > > >> > > > > > >> > >> > > > > >
> >> > > >> > > > > > >> > >> > > > > > The problem is that the
> >> legacy-whitelist
> >> > > >> plugin
> >> > > >> > > > > generates
> >> > > >> > > > > > >> > >> > > > > > compile errors with cordova-ios@3.8.0
> ,
> >> so
> >> > > >> now I
> >> > > >> > > > can't
> >> > > >> > > > > > just
> >> > > >> > > > > > >> > run
> >> > > >> > > > > > >> > >> > > > > > `cordova build`, I need to split the
> >> > > >> platforms up
> >> > > >> > > and
> >> > > >> > > > > > >> > >> > > > > > install/uninstall the plugin in
> >> between.
> >> > If
> >> > > >> > someone
> >> > > >> > > > > > makes a
> >> > > >> > > > > > >> > >> > > > > > dev build for Android and forgets the
> >> > > plugin,
> >> > > >> it
> >> > > >> > > will
> >> > > >> > > > > > >> appear
> >> > > >> > > > > > >> > >> > > > > > to build successfully but not
> actually
> >> > > >> function
> >> > > >> > > > > properly
> >> > > >> > > > > > >> due
> >> > > >> > > > > > >> > to
> >> > > >> > > > > > >> > >> the whitelist.
> >> > > >> > > > > > >> > >> > > > > >
> >> > > >> > > > > > >> > >> > > > > > I know, this is all pre-release, so
> >> pain
> >> > is
> >> > > >> > > somewhat
> >> > > >> > > > > > >> expected
> >> > > >> > > > > > >> > >> > > > > > right now. I'm worried about the case
> >> > where
> >> > > >> > > > > > >> > >> > > > > > cordova-android@4.0.0 is released
> and
> >> > > >> > > > > cordova-ios@3.8.0
> >> > > >> > > > > > is
> >> > > >> > > > > > >> > >> > > > > > still current, and how people
> >> > > >> > > > > > >> > >> > can
> >> > > >> > > > > > >> > >> > > > > > avoid whitelist breakage there.
> >> > > >> > > > > > >> > >> > > > > >
> >> > > >> > > > > > >> > >> > > > > >
> >> > > >> > > > > > >> ------------------------------
> >> > > ------------------------------
> >> > > >> > > > > > >> > >> > ---------
> >> > > >> > > > > > >> > >> > > > > > To unsubscribe, e-mail:
> >> > > >> > > > > > dev-unsubscribe@cordova.apache.org
> >> > > >> > > > > > >> > >> > > > > > For additional commands, e-mail:
> >> > > >> > > > > > >> dev-help@cordova.apache.org
> >> > > >> > > > > > >> > >> > > > > >
> >> > > >> > > > > > >> > >> > > > >
> >> > > >> > > > > > >> > >> > > > >
> >> > > >> > > > > >
> >> ------------------------------------------------------------
> >> > > >> > > > > > >> > >> > ---------
> >> > > >> > > > > > >> > >> > > > > To unsubscribe, e-mail:
> >> > > >> > > > > dev-unsubscribe@cordova.apache.org
> >> > > >> > > > > > >> > >> > > > > For additional commands, e-mail:
> >> > > >> > > > > > dev-help@cordova.apache.org
> >> > > >> > > > > > >> > >> > > > >
> >> > > >> > > > > > >> > >> > > > >
> >> > > >> > > > > > >> > >> > > >
> >> > > >> > > > > > >> > >> > >
> >> > > >> > > > > > >> > >> >
> >> > > >> > > > > > >> > >>
> >> > > >> > > > > > >> >
> >> > > >> > > > > > >> >
> >> > > >> > > > >
> >> > > >>
> >> ---------------------------------------------------------------------
> >> > > >> > > > > > >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.
> >> > > apache.org
> >> > > >> > > > > > >> > For additional commands, e-mail:
> >> > > >> dev-help@cordova.apache.org
> >> > > >> > > > > > >> >
> >> > > >> > > > > > >> >
> >> > > >> > > > > > >>
> >> > > >> > > > > > >
> >> > > >> > > > > > >
> >> > > >> > > > > >
> >> > > >> > > > >
> >> > > >> > > > >
> >> > > >> > > > >
> >> > > >> > > > > --
> >> > > >> > > > > Carlos Santana
> >> > > >> > > > > <cs...@gmail.com>
> >> > > >> > > > >
> >> > > >> > > >
> >> > > >> > >
> >> > > >> >
> >> > > >>
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Serge Huijben <s....@gmail.com>.
Then, it seems strange to me that it logs an error and repeated warnings if
the meta tag is missing. Perhaps we should remove that from the plugin.
Op do 9 apr. 2015 om 20:21 schreef Ian Clelland <ic...@chromium.org>
> Moving from [VOTE] thread:
>
> On Thu, Apr 9, 2015 at 1:44 PM, Serge Huijben <s....@gmail.com> wrote:
>
>> But why is the meta csp tag required?
>
>
> It's not required, only recommended. It's more secure, as it can restrict
> more network access than the whitelist itself is capable of. (streaming
> <audio> and <video> tags, for instance).
>
> On Thu, Apr 9, 2015 at 1:44 PM, Treggiari, Leo <le...@intel.com>
> wrote:
>
>> Another question, based upon my understanding, which must be wrong!
>
>
>>
>> The 4.0.0 Android Release will require the cordova-plugin-whitelist in
>> order
>> to get a whitelist implemented correctly.
>>
>> Given its name (dash-style) it is only available as an node component.
>>
>> The is no released CLI that knows how to fetch from npm?
>> Or does 4.3, even though I don't see it in the release notes?
>> Even so, there are many previous CLI releases which will not work?
>>
>
> This is at least partly resolved by the fact that no released CLI points
> to cordova-android 4.0.0. Once 4.0.0 is released. we will be able to
> release a version of the CLI which downloads it by default.
>
> The whitelist plugins are published already, and discussion is underway
> about voting/releasing cordova-lib (and accompanying tools), so I think
> there are only two possible timelines:
>
> A) whitelist plugins released, then cordova-android 4 released, then tools
> released (supports NPM plugins and Android 4).
>
> B) plugins released, then tools released (supports NPM plugins), then
> cordova-android 4 released, then a small bump of tools is released (to pin
> to cordova-android 4)
>
> In either case, users of the released CLI always have a version which
> works.
>
>
>> It would be good for the release notes to explain the situation.
>>
>> Leo
>>
>
> On Thu, Apr 9, 2015 at 1:24 PM, Michal Mocny <mm...@chromium.org> wrote:
>
>> Splashscreens was mentioned, icons was not. I don't think there is an
>> icons change?
>>
>> On Thu, Apr 9, 2015 at 1:17 PM, Joe Bowser <bo...@gmail.com> wrote:
>>
>> > So, wasn't there a change regarding icons and spashscreens being moved?
>> I
>> > have no idea if we want to add that, or if adding that should happen
>> after
>> > the release?
>> >
>> > On Wed, Apr 8, 2015 at 7:09 PM Andrew Grieve <ag...@chromium.org>
>> wrote:
>> >
>> > > CB-8684 is now merged and I've updated the targetSdk (and made a
>> couple
>> > > other changes).
>> > >
>> > > I'll start the release process in the morning as long as there no
>> > > objections.
>> > >
>> > >
>> > > On Tue, Apr 7, 2015 at 2:20 PM, Andrew Grieve <ag...@chromium.org>
>> > > wrote:
>> > >
>> > > > I'll start on it once CB-8684 lands (Tony - assuming you'll have
>> this
>> > > done
>> > > > shortly and would prefer it lands?)
>> > > >
>> > > > On Tue, Apr 7, 2015 at 1:33 PM, Jesse <pu...@gmail.com>
>> wrote:
>> > > >
>> > > >> Sweet!
>> > > >>
>> > > >> @purplecabbage
>> > > >> risingj.com
>> > > >>
>> > > >> On Tue, Apr 7, 2015 at 8:35 AM, Andrew Grieve <
>> agrieve@chromium.org>
>> > > >> wrote:
>> > > >>
>> > > >> > Let's do it!
>> > > >> >
>> > > >> > On Mon, Apr 6, 2015 at 7:33 PM, Joe Bowser <bo...@gmail.com>
>> > wrote:
>> > > >> >
>> > > >> > > So, I think we should put off the embedder's guide until after
>> the
>> > > >> > > release. A lot of it has changed, and since we're still
>> > technically
>> > > >> > > obligated to support the 3.x release tree for six months, that
>> > > should
>> > > >> buy
>> > > >> > > us some time to figure out how that is going to work. Getting
>> > > >> Cordova to
>> > > >> > > work with a vanilla Android Studio project is a non-trivial
>> task.
>> > > >> > >
>> > > >> > > Given that everything else appears to be done, should we start
>> > > voting
>> > > >> on
>> > > >> > an
>> > > >> > > RC for this? What do people think?
>> > > >> > >
>> > > >> > >
>> > > >> > >
>> > > >> > > On Thu, Mar 19, 2015 at 10:31 AM Andrew Grieve <
>> > > agrieve@chromium.org>
>> > > >> > > wrote:
>> > > >> > >
>> > > >> > > > Here's issues:
>> > > >> > > > https://issues.apache.org/jira/browse/CB-8715 (docs)
>> > > >> > > > https://issues.apache.org/jira/browse/CB-8716 (whitelist)
>> > > >> > > > https://issues.apache.org/jira/browse/CB-8717 (write
>> > > >> RELEASENOTES.md)
>> > > >> > > >
>> > > >> > > > On Tue, Mar 17, 2015 at 10:15 AM, Carlos Santana <
>> > > >> csantana23@gmail.com
>> > > >> > >
>> > > >> > > > wrote:
>> > > >> > > >
>> > > >> > > > > I would say let's start RC testing and voting, But not pin
>> the
>> > > >> > version
>> > > >> > > in
>> > > >> > > > > Cordova CLI until the tasks that Andrew mentioned are done.
>> > > >> > > > > Andrew can you create the JIRA Items for the tasks that
>> need
>> > to
>> > > be
>> > > >> > > done.
>> > > >> > > > I
>> > > >> > > > > thought there was a discussion about creating JIRA Items to
>> > help
>> > > >> > track
>> > > >> > > > and
>> > > >> > > > > know what's left for release something.
>> > > >> > > > >
>> > > >> > > > > - upgrade guide,
>> > > >> > > > > - publishing whitelist plugins,
>> > > >> > > > > - and making it so that the default project template
>> includes
>> > > >> <plugin
>> > > >> > > > > name="cordova-plugin-whitelist" />)
>> > > >> > > > >
>> > > >> > > > >
>> > > >> > > > > On Mon, Mar 16, 2015 at 11:21 PM, Ian Clelland <
>> > > >> > iclelland@chromium.org
>> > > >> > > >
>> > > >> > > > > wrote:
>> > > >> > > > >
>> > > >> > > > > > We'll probably need at least an RC for the whitelist
>> plugin,
>> > > if
>> > > >> > not a
>> > > >> > > > > vote,
>> > > >> > > > > > to be able to vote on this.
>> > > >> > > > > >
>> > > >> > > > > > Or can we just include instructions like "Use
>> > > >> > > > > > cordova-plugin-whitelist@f70b1bc for testing" while we
>> > start
>> > > >> the
>> > > >> > > > > official
>> > > >> > > > > > release process for the plugins?
>> > > >> > > > > >
>> > > >> > > > > > On Mon, Mar 16, 2015 at 11:17 PM, Ian Clelland <
>> > > >> > > iclelland@chromium.org
>> > > >> > > > >
>> > > >> > > > > > wrote:
>> > > >> > > > > >
>> > > >> > > > > > > +1 -- Let's get this out the door :)
>> > > >> > > > > > > I'll see what I can get done to move it in that
>> direction.
>> > > >> > > > > > >
>> > > >> > > > > > > On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <
>> > > >> > > agrieve@chromium.org
>> > > >> > > > >
>> > > >> > > > > > > wrote:
>> > > >> > > > > > >
>> > > >> > > > > > >> Everything's ready afaik (minus upgrade guide,
>> publishing
>> > > >> > > whitelist
>> > > >> > > > > > >> plugins, and making it so that the default project
>> > template
>> > > >> > > includes
>> > > >> > > > > > >> <plugin name="cordova-plugin-whitelist" />). Maybe
>> let's
>> > > do
>> > > >> a RC
>> > > >> > > > while
>> > > >> > > > > > we
>> > > >> > > > > > >> wait on these things being finished up?
>> > > >> > > > > > >>
>> > > >> > > > > > >> If anyone wants to take on any of these tasks, that
>> would
>> > > be
>> > > >> > > > awesome.
>> > > >> > > > > > >>
>> > > >> > > > > > >> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <
>> > > shazron@gmail.com>
>> > > >> > > wrote:
>> > > >> > > > > > >>
>> > > >> > > > > > >> > +1 for vote thread, let's get this thing out so
>> people
>> > > >> (that
>> > > >> > are
>> > > >> > > > not
>> > > >> > > > > > >> > us) can test...
>> > > >> > > > > > >> >
>> > > >> > > > > > >> >
>> > > >> > > > > > >> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <
>> > > >> > bowserj@gmail.com>
>> > > >> > > > > > wrote:
>> > > >> > > > > > >> > > OK, this is a three month old thread, and we're
>> > waiting
>> > > >> on a
>> > > >> > > > > > >> discussion
>> > > >> > > > > > >> > > before we release something? I really think we
>> should
>> > > go
>> > > >> to
>> > > >> > a
>> > > >> > > > vote
>> > > >> > > > > > >> thread
>> > > >> > > > > > >> > > now that we have a legacy whitelist plugin and a
>> new
>> > > >> style
>> > > >> > > > > whitelist
>> > > >> > > > > > >> > > plugin. We shouldn't keep constantly delaying
>> this
>> > > >> release
>> > > >> > > > > because
>> > > >> > > > > > of
>> > > >> > > > > > >> > > what's happening on other platforms, especially
>> since
>> > > we
>> > > >> > > already
>> > > >> > > > > > >> > pluginized
>> > > >> > > > > > >> > > the whitelist.
>> > > >> > > > > > >> > >
>> > > >> > > > > > >> > > Can we please release soon?
>> > > >> > > > > > >> > >
>> > > >> > > > > > >> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil Khandelwal
>> <
>> > > >> > > > > > >> > nikhilkh@microsoft.com>
>> > > >> > > > > > >> > > wrote:
>> > > >> > > > > > >> > >
>> > > >> > > > > > >> > >> I know we discussed a couple of approaches
>> > > implementing
>> > > >> the
>> > > >> > > > > default
>> > > >> > > > > > >> > >> whitelist policy for Android/iOS - either every
>> app
>> > > >> would
>> > > >> > be
>> > > >> > > > > > >> required to
>> > > >> > > > > > >> > >> include the whitelist plugin or have it have
>> smart
>> > > >> defaults
>> > > >> > > in
>> > > >> > > > > the
>> > > >> > > > > > >> > platform
>> > > >> > > > > > >> > >> implementation and the plugin being able to
>> override
>> > > >> them.
>> > > >> > > > > > >> > >>
>> > > >> > > > > > >> > >> I don’t think that thread closed with any
>> > conclusions.
>> > > >> > > > > > >> > >>
>> > > >> > > > > > >> > >> Thanks,
>> > > >> > > > > > >> > >> Nikhil
>> > > >> > > > > > >> > >>
>> > > >> > > > > > >> > >>
>> > > >> > > > > > >> > >> -----Original Message-----
>> > > >> > > > > > >> > >> From: Joe Bowser [mailto:bowserj@gmail.com]
>> > > >> > > > > > >> > >> Sent: Thursday, March 12, 2015 11:23 AM
>> > > >> > > > > > >> > >> To: dev
>> > > >> > > > > > >> > >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0
>> Release
>> > > >> > > > > > >> > >>
>> > > >> > > > > > >> > >> OK, so right now it's just docs? How soon can we
>> > get a
>> > > >> VOTE
>> > > >> > > > > thread
>> > > >> > > > > > >> > started
>> > > >> > > > > > >> > >> for 4.0.0?
>> > > >> > > > > > >> > >>
>> > > >> > > > > > >> > >> On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <
>> > > >> > > > > > agrieve@chromium.org>
>> > > >> > > > > > >> > >> wrote:
>> > > >> > > > > > >> > >>
>> > > >> > > > > > >> > >> > mobilespec is now working again... Took longer
>> > than
>> > > I
>> > > >> > would
>> > > >> > > > > have
>> > > >> > > > > > >> > >> > liked, but did you know that on Android
>> FileReader
>> > > >> > triggers
>> > > >> > > > > > >> > >> > shouldInterceptRequest() with Blob URLs!?
>> > > >> > > > > > >> > >> >
>> > > >> > > > > > >> > >> > Separate thread is already happening re:
>> > whitelists,
>> > > >> so
>> > > >> > > once
>> > > >> > > > > > that's
>> > > >> > > > > > >> > >> > figured out, it's just docs afaict.
>> > > >> > > > > > >> > >> >
>> > > >> > > > > > >> > >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian Clelland <
>> > > >> > > > > > >> iclelland@chromium.org
>> > > >> > > > > > >> > >
>> > > >> > > > > > >> > >> > wrote:
>> > > >> > > > > > >> > >> >
>> > > >> > > > > > >> > >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <
>> > > >> > > > > purplecabbage@gmail.com
>> > > >> > > > > > >
>> > > >> > > > > > >> > wrote:
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > > > We should start a new whitelist plugin
>> related
>> > > >> > thread.
>> > > >> > > > > > >> > >> > > >
>> > > >> > > > > > >> > >> > > > Why is a plugin blocking a release?
>> Default
>> > > (aka
>> > > >> > > > > no-plugin)
>> > > >> > > > > > >> > >> > > > behavior should be to allow all network
>> > requests
>> > > >> > > > shouldn't
>> > > >> > > > > > it?
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > > Well, that just might be a blacklist then :)
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > > > This thread is a
>> > > >> > > > > > >> > >> > > > month long, and not the first discussion of
>> > > 4.0.0
>> > > >> for
>> > > >> > > > > > Android.
>> > > >> > > > > > >> > >> > > >
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > > Seriously, though -- the whitelist
>> discussion is
>> > > >> much
>> > > >> > > > longer
>> > > >> > > > > > than
>> > > >> > > > > > >> > >> > > that,
>> > > >> > > > > > >> > >> > and
>> > > >> > > > > > >> > >> > > this isn't the first time that the default
>> > > >> > > > no-network-access
>> > > >> > > > > > >> policy
>> > > >> > > > > > >> > >> > > has been brought up:
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > > (Here's the first question, from *July*:
>> > > >> > > > > > >> > >> > > http://markmail.org/message/t4vj4saisem2mcgw
>> > > >> > > > > > >> > >> > > Here's where I mentioned what the implemented
>> > > policy
>> > > >> > was:
>> > > >> > > > > > >> > >> > > http://markmail.org/message/s4necfnh4hnblpjm
>> > > >> > > > > > >> > >> > > And in another discussion:
>> > > >> > > > > > >> > >> > > http://markmail.org/message/ap7syhqysizmsvrz
>> )
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > > If we want to reconsider that decision, then
>> we
>> > > >> should
>> > > >> > > > > > certainly
>> > > >> > > > > > >> do
>> > > >> > > > > > >> > >> > > so before we cut a release. I think it would
>> be
>> > a
>> > > >> real
>> > > >> > > > > problem
>> > > >> > > > > > to
>> > > >> > > > > > >> > >> > > change it afterwards, so let's get it right.
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > > Also, it's not the plugin itself that's
>> blocking
>> > > the
>> > > >> > > > release,
>> > > >> > > > > > >> it's
>> > > >> > > > > > >> > >> > > us making sure that we've implemented the
>> core
>> > > hooks
>> > > >> > > > > correctly
>> > > >> > > > > > so
>> > > >> > > > > > >> > >> > > that the plugin can actually do its job, and
>> > that
>> > > >> > people
>> > > >> > > > who
>> > > >> > > > > > >> don't
>> > > >> > > > > > >> > >> > > want that particular plugin can make a better
>> > one.
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > > (It is also an issue that a plugin, required
>> for
>> > > >> > > > > > cordova-android
>> > > >> > > > > > >> > >> > > 4.0.0, breaks apps which are also building
>> for
>> > > >> > > cordova-ios
>> > > >> > > > > > 3.8.0.
>> > > >> > > > > > >> > >> > > I'll take a
>> > > >> > > > > > >> > >> > look
>> > > >> > > > > > >> > >> > > at that, and either remove the ios-native
>> > portions
>> > > >> of
>> > > >> > the
>> > > >> > > > > > >> whitelist
>> > > >> > > > > > >> > >> > plugin,
>> > > >> > > > > > >> > >> > > or neuter it so that it doesn't interfere
>> with
>> > an
>> > > >> ios
>> > > >> > app
>> > > >> > > > if
>> > > >> > > > > > it's
>> > > >> > > > > > >> > >> > > not on the unplug-whitelist branch of that
>> > repo.)
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > > Ian
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> > > > @purplecabbage
>> > > >> > > > > > >> > >> > > > risingj.com
>> > > >> > > > > > >> > >> > > >
>> > > >> > > > > > >> > >> > > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <
>> > > >> > > > shazron@gmail.com
>> > > >> > > > > >
>> > > >> > > > > > >> > wrote:
>> > > >> > > > > > >> > >> > > >
>> > > >> > > > > > >> > >> > > > > legacy-whitelist-plugin should be fixed
>> so
>> > > that
>> > > >> it
>> > > >> > > > > compiles
>> > > >> > > > > > >> on
>> > > >> > > > > > >> > >> > > > > cordova-ios@3.8.0. It shouldn't be a
>> > problem
>> > > to
>> > > >> > fix
>> > > >> > > > this
>> > > >> > > > > > at
>> > > >> > > > > > >> > >> > > > > compile
>> > > >> > > > > > >> > >> > or
>> > > >> > > > > > >> > >> > > > > run-time (whichever is applicable here
>> > related
>> > > >> to
>> > > >> > the
>> > > >> > > > > > compile
>> > > >> > > > > > >> > >> > > > > error)
>> > > >> > > > > > >> > >> > > > >
>> > > >> > > > > > >> > >> > > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl
>> Pogue
>> > > >> > > > > > >> > >> > > > > <dv...@gmail.com>
>> > > >> > > > > > >> > >> > > > wrote:
>> > > >> > > > > > >> > >> > > > > > On 2 March 2015 at 13:37, Joe Bowser <
>> > > >> > > > > bowserj@gmail.com>
>> > > >> > > > > > >> > wrote:
>> > > >> > > > > > >> > >> > > > > >> So, right now the whitelist changes
>> are
>> > > >> what's
>> > > >> > > > holding
>> > > >> > > > > > up
>> > > >> > > > > > >> the
>> > > >> > > > > > >> > >> > 4.0.0
>> > > >> > > > > > >> > >> > > > > release
>> > > >> > > > > > >> > >> > > > > >> now? Is this really the only thing
>> > that's
>> > > >> > holding
>> > > >> > > > up
>> > > >> > > > > > this
>> > > >> > > > > > >> > >> > release?
>> > > >> > > > > > >> > >> > > > > >>
>> > > >> > > > > > >> > >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM
>> Andrew
>> > > >> Grieve <
>> > > >> > > > > > >> > >> > > agrieve@chromium.org>
>> > > >> > > > > > >> > >> > > > > wrote:
>> > > >> > > > > > >> > >> > > > > >>
>> > > >> > > > > > >> > >> > > > > >>> I think we'll also need to finish
>> with
>> > the
>> > > >> > > > whitelist
>> > > >> > > > > > >> changes
>> > > >> > > > > > >> > >> > > > > >>> &
>> > > >> > > > > > >> > >> > have
>> > > >> > > > > > >> > >> > > > > both
>> > > >> > > > > > >> > >> > > > > >>> the legacy and new-way whitelist
>> plugins
>> > > >> > released
>> > > >> > > > > > before
>> > > >> > > > > > >> we
>> > > >> > > > > > >> > >> > > > > >>> can
>> > > >> > > > > > >> > >> > do
>> > > >> > > > > > >> > >> > > a
>> > > >> > > > > > >> > >> > > > > 4.0.0
>> > > >> > > > > > >> > >> > > > > >>> release (otherwise you wouldn't be
>> able
>> > to
>> > > >> > write
>> > > >> > > an
>> > > >> > > > > app
>> > > >> > > > > > >> that
>> > > >> > > > > > >> > >> > > > > >>> hits
>> > > >> > > > > > >> > >> > > the
>> > > >> > > > > > >> > >> > > > > >>> network)
>> > > >> > > > > > >> > >> > > > > >>>
>> > > >> > > > > > >> > >> > > > > >
>> > > >> > > > > > >> > >> > > > > > Just FYI, the whitelist stuff is
>> proving
>> > to
>> > > >> be a
>> > > >> > > bit
>> > > >> > > > > of a
>> > > >> > > > > > >> pain
>> > > >> > > > > > >> > >> > point.
>> > > >> > > > > > >> > >> > > > > > I'm using cordova-android@master, and
>> > need
>> > > to
>> > > >> > > > install
>> > > >> > > > > > the
>> > > >> > > > > > >> > >> > > > > > legacy-whitelist plugin in order to
>> make
>> > > >> network
>> > > >> > > > > > requests.
>> > > >> > > > > > >> > >> > > > > > Once the plugin is installed,
>> everything
>> > > >> seems to
>> > > >> > > > work.
>> > > >> > > > > > >> > >> > > > > >
>> > > >> > > > > > >> > >> > > > > > The problem is that the
>> legacy-whitelist
>> > > >> plugin
>> > > >> > > > > generates
>> > > >> > > > > > >> > >> > > > > > compile errors with cordova-ios@3.8.0,
>> so
>> > > >> now I
>> > > >> > > > can't
>> > > >> > > > > > just
>> > > >> > > > > > >> > run
>> > > >> > > > > > >> > >> > > > > > `cordova build`, I need to split the
>> > > >> platforms up
>> > > >> > > and
>> > > >> > > > > > >> > >> > > > > > install/uninstall the plugin in
>> between.
>> > If
>> > > >> > someone
>> > > >> > > > > > makes a
>> > > >> > > > > > >> > >> > > > > > dev build for Android and forgets the
>> > > plugin,
>> > > >> it
>> > > >> > > will
>> > > >> > > > > > >> appear
>> > > >> > > > > > >> > >> > > > > > to build successfully but not actually
>> > > >> function
>> > > >> > > > > properly
>> > > >> > > > > > >> due
>> > > >> > > > > > >> > to
>> > > >> > > > > > >> > >> the whitelist.
>> > > >> > > > > > >> > >> > > > > >
>> > > >> > > > > > >> > >> > > > > > I know, this is all pre-release, so
>> pain
>> > is
>> > > >> > > somewhat
>> > > >> > > > > > >> expected
>> > > >> > > > > > >> > >> > > > > > right now. I'm worried about the case
>> > where
>> > > >> > > > > > >> > >> > > > > > cordova-android@4.0.0 is released and
>> > > >> > > > > cordova-ios@3.8.0
>> > > >> > > > > > is
>> > > >> > > > > > >> > >> > > > > > still current, and how people
>> > > >> > > > > > >> > >> > can
>> > > >> > > > > > >> > >> > > > > > avoid whitelist breakage there.
>> > > >> > > > > > >> > >> > > > > >
>> > > >> > > > > > >> > >> > > > > >
>> > > >> > > > > > >> ------------------------------
>> > > ------------------------------
>> > > >> > > > > > >> > >> > ---------
>> > > >> > > > > > >> > >> > > > > > To unsubscribe, e-mail:
>> > > >> > > > > > dev-unsubscribe@cordova.apache.org
>> > > >> > > > > > >> > >> > > > > > For additional commands, e-mail:
>> > > >> > > > > > >> dev-help@cordova.apache.org
>> > > >> > > > > > >> > >> > > > > >
>> > > >> > > > > > >> > >> > > > >
>> > > >> > > > > > >> > >> > > > >
>> > > >> > > > > >
>> ------------------------------------------------------------
>> > > >> > > > > > >> > >> > ---------
>> > > >> > > > > > >> > >> > > > > To unsubscribe, e-mail:
>> > > >> > > > > dev-unsubscribe@cordova.apache.org
>> > > >> > > > > > >> > >> > > > > For additional commands, e-mail:
>> > > >> > > > > > dev-help@cordova.apache.org
>> > > >> > > > > > >> > >> > > > >
>> > > >> > > > > > >> > >> > > > >
>> > > >> > > > > > >> > >> > > >
>> > > >> > > > > > >> > >> > >
>> > > >> > > > > > >> > >> >
>> > > >> > > > > > >> > >>
>> > > >> > > > > > >> >
>> > > >> > > > > > >> >
>> > > >> > > > >
>> > > >>
>> ---------------------------------------------------------------------
>> > > >> > > > > > >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.
>> > > apache.org
>> > > >> > > > > > >> > For additional commands, e-mail:
>> > > >> dev-help@cordova.apache.org
>> > > >> > > > > > >> >
>> > > >> > > > > > >> >
>> > > >> > > > > > >>
>> > > >> > > > > > >
>> > > >> > > > > > >
>> > > >> > > > > >
>> > > >> > > > >
>> > > >> > > > >
>> > > >> > > > >
>> > > >> > > > > --
>> > > >> > > > > Carlos Santana
>> > > >> > > > > <cs...@gmail.com>
>> > > >> > > > >
>> > > >> > > >
>> > > >> > >
>> > > >> >
>> > > >>
>> > > >
>> > > >
>> > >
>> >
>>
>
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Sounds good Steve!
Tools release should also make sure to update app-hello-world to include
whitelist plugin by default since that's clearly going to be a source of
confusion.
On Thu, Apr 9, 2015 at 4:56 PM, Steven Gill <st...@gmail.com> wrote:
> I am going to start a discuss thread for plugins release later today.
>
> I'm thinking:
>
> 1) Android release
> 2) Plugins release
> 3) Tools release 5.0.0 with cordova-wp8, cordova-windows and
> cordova-android all updated, npm fetching, fixed --save workflow, etc.
>
> Whitelist plugins have both been released already. So they won't be
> included in the plugins release unless we have made changes to them and
> want to release updated versions.
>
>
> On Thu, Apr 9, 2015 at 12:58 PM, Andrew Grieve <ag...@chromium.org>
> wrote:
>
>> Michal - Good point about npm vs github for links. We tend to tweak docs
>> post npm publish, so I've changed the blog post links to github ones.
>>
>> On Thu, Apr 9, 2015 at 3:55 PM, Andrew Grieve <ag...@chromium.org>
>> wrote:
>>
>> > The plugins being on npm will likely be a bump. Perhaps we should
>> mention
>> > that it requires the latest CLI (not yet release one), and defer the
>> blog
>> > post until CLI is released?
>> >
>> > On Thu, Apr 9, 2015 at 2:20 PM, Ian Clelland <ic...@chromium.org>
>> > wrote:
>> >
>> >> Moving from [VOTE] thread:
>> >>
>> >> On Thu, Apr 9, 2015 at 1:44 PM, Serge Huijben <s....@gmail.com>
>> >> wrote:
>> >>
>> >> > But why is the meta csp tag required?
>> >>
>> >>
>> >> It's not required, only recommended. It's more secure, as it can
>> restrict
>> >> more network access than the whitelist itself is capable of. (streaming
>> >> <audio> and <video> tags, for instance).
>> >>
>> >> On Thu, Apr 9, 2015 at 1:44 PM, Treggiari, Leo <
>> leo.treggiari@intel.com>
>> >> wrote:
>> >>
>> >> > Another question, based upon my understanding, which must be wrong!
>> >> >
>> >> > The 4.0.0 Android Release will require the cordova-plugin-whitelist
>> in
>> >> > order
>> >> > to get a whitelist implemented correctly.
>> >> >
>> >> > Given its name (dash-style) it is only available as an node
>> component.
>> >> >
>> >> > The is no released CLI that knows how to fetch from npm?
>> >> > Or does 4.3, even though I don't see it in the release notes?
>> >> > Even so, there are many previous CLI releases which will not work?
>> >> >
>> >>
>> >> This is at least partly resolved by the fact that no released CLI
>> points
>> >> to
>> >> cordova-android 4.0.0. Once 4.0.0 is released. we will be able to
>> release
>> >> a
>> >> version of the CLI which downloads it by default.
>> >>
>> >> The whitelist plugins are published already, and discussion is underway
>> >> about voting/releasing cordova-lib (and accompanying tools), so I think
>> >> there are only two possible timelines:
>> >>
>> >> A) whitelist plugins released, then cordova-android 4 released, then
>> tools
>> >> released (supports NPM plugins and Android 4).
>> >>
>> >> B) plugins released, then tools released (supports NPM plugins), then
>> >> cordova-android 4 released, then a small bump of tools is released (to
>> pin
>> >> to cordova-android 4)
>> >>
>> >> In either case, users of the released CLI always have a version which
>> >> works.
>> >>
>> >>
>> >> > It would be good for the release notes to explain the situation.
>> >> >
>> >> > Leo
>> >> >
>> >>
>> >>
>> >> On Thu, Apr 9, 2015 at 1:24 PM, Michal Mocny <mm...@chromium.org>
>> wrote:
>> >>
>> >> > Splashscreens was mentioned, icons was not. I don't think there is
>> an
>> >> > icons change?
>> >> >
>> >> > On Thu, Apr 9, 2015 at 1:17 PM, Joe Bowser <bo...@gmail.com>
>> wrote:
>> >> >
>> >> > > So, wasn't there a change regarding icons and spashscreens being
>> >> moved? I
>> >> > > have no idea if we want to add that, or if adding that should
>> happen
>> >> > after
>> >> > > the release?
>> >> > >
>> >> > > On Wed, Apr 8, 2015 at 7:09 PM Andrew Grieve <agrieve@chromium.org
>> >
>> >> > wrote:
>> >> > >
>> >> > > > CB-8684 is now merged and I've updated the targetSdk (and made a
>> >> couple
>> >> > > > other changes).
>> >> > > >
>> >> > > > I'll start the release process in the morning as long as there no
>> >> > > > objections.
>> >> > > >
>> >> > > >
>> >> > > > On Tue, Apr 7, 2015 at 2:20 PM, Andrew Grieve <
>> agrieve@chromium.org
>> >> >
>> >> > > > wrote:
>> >> > > >
>> >> > > > > I'll start on it once CB-8684 lands (Tony - assuming you'll
>> have
>> >> this
>> >> > > > done
>> >> > > > > shortly and would prefer it lands?)
>> >> > > > >
>> >> > > > > On Tue, Apr 7, 2015 at 1:33 PM, Jesse <purplecabbage@gmail.com
>> >
>> >> > wrote:
>> >> > > > >
>> >> > > > >> Sweet!
>> >> > > > >>
>> >> > > > >> @purplecabbage
>> >> > > > >> risingj.com
>> >> > > > >>
>> >> > > > >> On Tue, Apr 7, 2015 at 8:35 AM, Andrew Grieve <
>> >> agrieve@chromium.org
>> >> > >
>> >> > > > >> wrote:
>> >> > > > >>
>> >> > > > >> > Let's do it!
>> >> > > > >> >
>> >> > > > >> > On Mon, Apr 6, 2015 at 7:33 PM, Joe Bowser <
>> bowserj@gmail.com>
>> >> > > wrote:
>> >> > > > >> >
>> >> > > > >> > > So, I think we should put off the embedder's guide until
>> >> after
>> >> > the
>> >> > > > >> > > release. A lot of it has changed, and since we're still
>> >> > > technically
>> >> > > > >> > > obligated to support the 3.x release tree for six months,
>> >> that
>> >> > > > should
>> >> > > > >> buy
>> >> > > > >> > > us some time to figure out how that is going to work.
>> >> Getting
>> >> > > > >> Cordova to
>> >> > > > >> > > work with a vanilla Android Studio project is a
>> non-trivial
>> >> > task.
>> >> > > > >> > >
>> >> > > > >> > > Given that everything else appears to be done, should we
>> >> start
>> >> > > > voting
>> >> > > > >> on
>> >> > > > >> > an
>> >> > > > >> > > RC for this? What do people think?
>> >> > > > >> > >
>> >> > > > >> > >
>> >> > > > >> > >
>> >> > > > >> > > On Thu, Mar 19, 2015 at 10:31 AM Andrew Grieve <
>> >> > > > agrieve@chromium.org>
>> >> > > > >> > > wrote:
>> >> > > > >> > >
>> >> > > > >> > > > Here's issues:
>> >> > > > >> > > > https://issues.apache.org/jira/browse/CB-8715 (docs)
>> >> > > > >> > > > https://issues.apache.org/jira/browse/CB-8716
>> (whitelist)
>> >> > > > >> > > > https://issues.apache.org/jira/browse/CB-8717 (write
>> >> > > > >> RELEASENOTES.md)
>> >> > > > >> > > >
>> >> > > > >> > > > On Tue, Mar 17, 2015 at 10:15 AM, Carlos Santana <
>> >> > > > >> csantana23@gmail.com
>> >> > > > >> > >
>> >> > > > >> > > > wrote:
>> >> > > > >> > > >
>> >> > > > >> > > > > I would say let's start RC testing and voting, But not
>> >> pin
>> >> > the
>> >> > > > >> > version
>> >> > > > >> > > in
>> >> > > > >> > > > > Cordova CLI until the tasks that Andrew mentioned are
>> >> done.
>> >> > > > >> > > > > Andrew can you create the JIRA Items for the tasks
>> that
>> >> need
>> >> > > to
>> >> > > > be
>> >> > > > >> > > done.
>> >> > > > >> > > > I
>> >> > > > >> > > > > thought there was a discussion about creating JIRA
>> Items
>> >> to
>> >> > > help
>> >> > > > >> > track
>> >> > > > >> > > > and
>> >> > > > >> > > > > know what's left for release something.
>> >> > > > >> > > > >
>> >> > > > >> > > > > - upgrade guide,
>> >> > > > >> > > > > - publishing whitelist plugins,
>> >> > > > >> > > > > - and making it so that the default project template
>> >> > includes
>> >> > > > >> <plugin
>> >> > > > >> > > > > name="cordova-plugin-whitelist" />)
>> >> > > > >> > > > >
>> >> > > > >> > > > >
>> >> > > > >> > > > > On Mon, Mar 16, 2015 at 11:21 PM, Ian Clelland <
>> >> > > > >> > iclelland@chromium.org
>> >> > > > >> > > >
>> >> > > > >> > > > > wrote:
>> >> > > > >> > > > >
>> >> > > > >> > > > > > We'll probably need at least an RC for the whitelist
>> >> > plugin,
>> >> > > > if
>> >> > > > >> > not a
>> >> > > > >> > > > > vote,
>> >> > > > >> > > > > > to be able to vote on this.
>> >> > > > >> > > > > >
>> >> > > > >> > > > > > Or can we just include instructions like "Use
>> >> > > > >> > > > > > cordova-plugin-whitelist@f70b1bc for testing"
>> while we
>> >> > > start
>> >> > > > >> the
>> >> > > > >> > > > > official
>> >> > > > >> > > > > > release process for the plugins?
>> >> > > > >> > > > > >
>> >> > > > >> > > > > > On Mon, Mar 16, 2015 at 11:17 PM, Ian Clelland <
>> >> > > > >> > > iclelland@chromium.org
>> >> > > > >> > > > >
>> >> > > > >> > > > > > wrote:
>> >> > > > >> > > > > >
>> >> > > > >> > > > > > > +1 -- Let's get this out the door :)
>> >> > > > >> > > > > > > I'll see what I can get done to move it in that
>> >> > direction.
>> >> > > > >> > > > > > >
>> >> > > > >> > > > > > > On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <
>> >> > > > >> > > agrieve@chromium.org
>> >> > > > >> > > > >
>> >> > > > >> > > > > > > wrote:
>> >> > > > >> > > > > > >
>> >> > > > >> > > > > > >> Everything's ready afaik (minus upgrade guide,
>> >> > publishing
>> >> > > > >> > > whitelist
>> >> > > > >> > > > > > >> plugins, and making it so that the default
>> project
>> >> > > template
>> >> > > > >> > > includes
>> >> > > > >> > > > > > >> <plugin name="cordova-plugin-whitelist" />).
>> Maybe
>> >> > let's
>> >> > > > do
>> >> > > > >> a RC
>> >> > > > >> > > > while
>> >> > > > >> > > > > > we
>> >> > > > >> > > > > > >> wait on these things being finished up?
>> >> > > > >> > > > > > >>
>> >> > > > >> > > > > > >> If anyone wants to take on any of these tasks,
>> that
>> >> > would
>> >> > > > be
>> >> > > > >> > > > awesome.
>> >> > > > >> > > > > > >>
>> >> > > > >> > > > > > >> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <
>> >> > > > shazron@gmail.com>
>> >> > > > >> > > wrote:
>> >> > > > >> > > > > > >>
>> >> > > > >> > > > > > >> > +1 for vote thread, let's get this thing out so
>> >> > people
>> >> > > > >> (that
>> >> > > > >> > are
>> >> > > > >> > > > not
>> >> > > > >> > > > > > >> > us) can test...
>> >> > > > >> > > > > > >> >
>> >> > > > >> > > > > > >> >
>> >> > > > >> > > > > > >> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <
>> >> > > > >> > bowserj@gmail.com>
>> >> > > > >> > > > > > wrote:
>> >> > > > >> > > > > > >> > > OK, this is a three month old thread, and
>> we're
>> >> > > waiting
>> >> > > > >> on a
>> >> > > > >> > > > > > >> discussion
>> >> > > > >> > > > > > >> > > before we release something? I really think
>> we
>> >> > should
>> >> > > > go
>> >> > > > >> to
>> >> > > > >> > a
>> >> > > > >> > > > vote
>> >> > > > >> > > > > > >> thread
>> >> > > > >> > > > > > >> > > now that we have a legacy whitelist plugin
>> and a
>> >> > new
>> >> > > > >> style
>> >> > > > >> > > > > whitelist
>> >> > > > >> > > > > > >> > > plugin. We shouldn't keep constantly
>> delaying
>> >> this
>> >> > > > >> release
>> >> > > > >> > > > > because
>> >> > > > >> > > > > > of
>> >> > > > >> > > > > > >> > > what's happening on other platforms,
>> especially
>> >> > since
>> >> > > > we
>> >> > > > >> > > already
>> >> > > > >> > > > > > >> > pluginized
>> >> > > > >> > > > > > >> > > the whitelist.
>> >> > > > >> > > > > > >> > >
>> >> > > > >> > > > > > >> > > Can we please release soon?
>> >> > > > >> > > > > > >> > >
>> >> > > > >> > > > > > >> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil
>> >> Khandelwal <
>> >> > > > >> > > > > > >> > nikhilkh@microsoft.com>
>> >> > > > >> > > > > > >> > > wrote:
>> >> > > > >> > > > > > >> > >
>> >> > > > >> > > > > > >> > >> I know we discussed a couple of approaches
>> >> > > > implementing
>> >> > > > >> the
>> >> > > > >> > > > > default
>> >> > > > >> > > > > > >> > >> whitelist policy for Android/iOS - either
>> every
>> >> > app
>> >> > > > >> would
>> >> > > > >> > be
>> >> > > > >> > > > > > >> required to
>> >> > > > >> > > > > > >> > >> include the whitelist plugin or have it have
>> >> smart
>> >> > > > >> defaults
>> >> > > > >> > > in
>> >> > > > >> > > > > the
>> >> > > > >> > > > > > >> > platform
>> >> > > > >> > > > > > >> > >> implementation and the plugin being able to
>> >> > override
>> >> > > > >> them.
>> >> > > > >> > > > > > >> > >>
>> >> > > > >> > > > > > >> > >> I don’t think that thread closed with any
>> >> > > conclusions.
>> >> > > > >> > > > > > >> > >>
>> >> > > > >> > > > > > >> > >> Thanks,
>> >> > > > >> > > > > > >> > >> Nikhil
>> >> > > > >> > > > > > >> > >>
>> >> > > > >> > > > > > >> > >>
>> >> > > > >> > > > > > >> > >> -----Original Message-----
>> >> > > > >> > > > > > >> > >> From: Joe Bowser [mailto:bowserj@gmail.com]
>> >> > > > >> > > > > > >> > >> Sent: Thursday, March 12, 2015 11:23 AM
>> >> > > > >> > > > > > >> > >> To: dev
>> >> > > > >> > > > > > >> > >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0
>> >> > Release
>> >> > > > >> > > > > > >> > >>
>> >> > > > >> > > > > > >> > >> OK, so right now it's just docs? How soon
>> can
>> >> we
>> >> > > get a
>> >> > > > >> VOTE
>> >> > > > >> > > > > thread
>> >> > > > >> > > > > > >> > started
>> >> > > > >> > > > > > >> > >> for 4.0.0?
>> >> > > > >> > > > > > >> > >>
>> >> > > > >> > > > > > >> > >> On Wed, Mar 4, 2015 at 10:47 AM Andrew
>> Grieve <
>> >> > > > >> > > > > > agrieve@chromium.org>
>> >> > > > >> > > > > > >> > >> wrote:
>> >> > > > >> > > > > > >> > >>
>> >> > > > >> > > > > > >> > >> > mobilespec is now working again... Took
>> >> longer
>> >> > > than
>> >> > > > I
>> >> > > > >> > would
>> >> > > > >> > > > > have
>> >> > > > >> > > > > > >> > >> > liked, but did you know that on Android
>> >> > FileReader
>> >> > > > >> > triggers
>> >> > > > >> > > > > > >> > >> > shouldInterceptRequest() with Blob URLs!?
>> >> > > > >> > > > > > >> > >> >
>> >> > > > >> > > > > > >> > >> > Separate thread is already happening re:
>> >> > > whitelists,
>> >> > > > >> so
>> >> > > > >> > > once
>> >> > > > >> > > > > > that's
>> >> > > > >> > > > > > >> > >> > figured out, it's just docs afaict.
>> >> > > > >> > > > > > >> > >> >
>> >> > > > >> > > > > > >> > >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian
>> >> Clelland <
>> >> > > > >> > > > > > >> iclelland@chromium.org
>> >> > > > >> > > > > > >> > >
>> >> > > > >> > > > > > >> > >> > wrote:
>> >> > > > >> > > > > > >> > >> >
>> >> > > > >> > > > > > >> > >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <
>> >> > > > >> > > > > purplecabbage@gmail.com
>> >> > > > >> > > > > > >
>> >> > > > >> > > > > > >> > wrote:
>> >> > > > >> > > > > > >> > >> > >
>> >> > > > >> > > > > > >> > >> > > > We should start a new whitelist plugin
>> >> > related
>> >> > > > >> > thread.
>> >> > > > >> > > > > > >> > >> > > >
>> >> > > > >> > > > > > >> > >> > > > Why is a plugin blocking a release?
>> >> Default
>> >> > > > (aka
>> >> > > > >> > > > > no-plugin)
>> >> > > > >> > > > > > >> > >> > > > behavior should be to allow all
>> network
>> >> > > requests
>> >> > > > >> > > > shouldn't
>> >> > > > >> > > > > > it?
>> >> > > > >> > > > > > >> > >> > >
>> >> > > > >> > > > > > >> > >> > >
>> >> > > > >> > > > > > >> > >> > > Well, that just might be a blacklist
>> then
>> >> :)
>> >> > > > >> > > > > > >> > >> > >
>> >> > > > >> > > > > > >> > >> > >
>> >> > > > >> > > > > > >> > >> > > > This thread is a
>> >> > > > >> > > > > > >> > >> > > > month long, and not the first
>> discussion
>> >> of
>> >> > > > 4.0.0
>> >> > > > >> for
>> >> > > > >> > > > > > Android.
>> >> > > > >> > > > > > >> > >> > > >
>> >> > > > >> > > > > > >> > >> > >
>> >> > > > >> > > > > > >> > >> > > Seriously, though -- the whitelist
>> >> discussion
>> >> > is
>> >> > > > >> much
>> >> > > > >> > > > longer
>> >> > > > >> > > > > > than
>> >> > > > >> > > > > > >> > >> > > that,
>> >> > > > >> > > > > > >> > >> > and
>> >> > > > >> > > > > > >> > >> > > this isn't the first time that the
>> default
>> >> > > > >> > > > no-network-access
>> >> > > > >> > > > > > >> policy
>> >> > > > >> > > > > > >> > >> > > has been brought up:
>> >> > > > >> > > > > > >> > >> > >
>> >> > > > >> > > > > > >> > >> > > (Here's the first question, from *July*:
>> >> > > > >> > > > > > >> > >> > >
>> >> http://markmail.org/message/t4vj4saisem2mcgw
>> >> > > > >> > > > > > >> > >> > > Here's where I mentioned what the
>> >> implemented
>> >> > > > policy
>> >> > > > >> > was:
>> >> > > > >> > > > > > >> > >> > >
>> >> http://markmail.org/message/s4necfnh4hnblpjm
>> >> > > > >> > > > > > >> > >> > > And in another discussion:
>> >> > > > >> > > > > > >> > >> > >
>> >> http://markmail.org/message/ap7syhqysizmsvrz)
>> >> > > > >> > > > > > >> > >> > >
>> >> > > > >> > > > > > >> > >> > > If we want to reconsider that decision,
>> >> then
>> >> > we
>> >> > > > >> should
>> >> > > > >> > > > > > certainly
>> >> > > > >> > > > > > >> do
>> >> > > > >> > > > > > >> > >> > > so before we cut a release. I think it
>> >> would
>> >> > be
>> >> > > a
>> >> > > > >> real
>> >> > > > >> > > > > problem
>> >> > > > >> > > > > > to
>> >> > > > >> > > > > > >> > >> > > change it afterwards, so let's get it
>> >> right.
>> >> > > > >> > > > > > >> > >> > >
>> >> > > > >> > > > > > >> > >> > > Also, it's not the plugin itself that's
>> >> > blocking
>> >> > > > the
>> >> > > > >> > > > release,
>> >> > > > >> > > > > > >> it's
>> >> > > > >> > > > > > >> > >> > > us making sure that we've implemented
>> the
>> >> core
>> >> > > > hooks
>> >> > > > >> > > > > correctly
>> >> > > > >> > > > > > so
>> >> > > > >> > > > > > >> > >> > > that the plugin can actually do its job,
>> >> and
>> >> > > that
>> >> > > > >> > people
>> >> > > > >> > > > who
>> >> > > > >> > > > > > >> don't
>> >> > > > >> > > > > > >> > >> > > want that particular plugin can make a
>> >> better
>> >> > > one.
>> >> > > > >> > > > > > >> > >> > >
>> >> > > > >> > > > > > >> > >> > > (It is also an issue that a plugin,
>> >> required
>> >> > for
>> >> > > > >> > > > > > cordova-android
>> >> > > > >> > > > > > >> > >> > > 4.0.0, breaks apps which are also
>> building
>> >> for
>> >> > > > >> > > cordova-ios
>> >> > > > >> > > > > > 3.8.0.
>> >> > > > >> > > > > > >> > >> > > I'll take a
>> >> > > > >> > > > > > >> > >> > look
>> >> > > > >> > > > > > >> > >> > > at that, and either remove the
>> ios-native
>> >> > > portions
>> >> > > > >> of
>> >> > > > >> > the
>> >> > > > >> > > > > > >> whitelist
>> >> > > > >> > > > > > >> > >> > plugin,
>> >> > > > >> > > > > > >> > >> > > or neuter it so that it doesn't
>> interfere
>> >> with
>> >> > > an
>> >> > > > >> ios
>> >> > > > >> > app
>> >> > > > >> > > > if
>> >> > > > >> > > > > > it's
>> >> > > > >> > > > > > >> > >> > > not on the unplug-whitelist branch of
>> that
>> >> > > repo.)
>> >> > > > >> > > > > > >> > >> > >
>> >> > > > >> > > > > > >> > >> > > Ian
>> >> > > > >> > > > > > >> > >> > >
>> >> > > > >> > > > > > >> > >> > >
>> >> > > > >> > > > > > >> > >> > > > @purplecabbage
>> >> > > > >> > > > > > >> > >> > > > risingj.com
>> >> > > > >> > > > > > >> > >> > > >
>> >> > > > >> > > > > > >> > >> > > > On Mon, Mar 2, 2015 at 2:02 PM,
>> Shazron <
>> >> > > > >> > > > shazron@gmail.com
>> >> > > > >> > > > > >
>> >> > > > >> > > > > > >> > wrote:
>> >> > > > >> > > > > > >> > >> > > >
>> >> > > > >> > > > > > >> > >> > > > > legacy-whitelist-plugin should be
>> >> fixed so
>> >> > > > that
>> >> > > > >> it
>> >> > > > >> > > > > compiles
>> >> > > > >> > > > > > >> on
>> >> > > > >> > > > > > >> > >> > > > > cordova-ios@3.8.0. It shouldn't be
>> a
>> >> > > problem
>> >> > > > to
>> >> > > > >> > fix
>> >> > > > >> > > > this
>> >> > > > >> > > > > > at
>> >> > > > >> > > > > > >> > >> > > > > compile
>> >> > > > >> > > > > > >> > >> > or
>> >> > > > >> > > > > > >> > >> > > > > run-time (whichever is applicable
>> here
>> >> > > related
>> >> > > > >> to
>> >> > > > >> > the
>> >> > > > >> > > > > > compile
>> >> > > > >> > > > > > >> > >> > > > > error)
>> >> > > > >> > > > > > >> > >> > > > >
>> >> > > > >> > > > > > >> > >> > > > > On Mon, Mar 2, 2015 at 1:47 PM,
>> Darryl
>> >> > Pogue
>> >> > > > >> > > > > > >> > >> > > > > <dv...@gmail.com>
>> >> > > > >> > > > > > >> > >> > > > wrote:
>> >> > > > >> > > > > > >> > >> > > > > > On 2 March 2015 at 13:37, Joe
>> Bowser
>> >> <
>> >> > > > >> > > > > bowserj@gmail.com>
>> >> > > > >> > > > > > >> > wrote:
>> >> > > > >> > > > > > >> > >> > > > > >> So, right now the whitelist
>> changes
>> >> are
>> >> > > > >> what's
>> >> > > > >> > > > holding
>> >> > > > >> > > > > > up
>> >> > > > >> > > > > > >> the
>> >> > > > >> > > > > > >> > >> > 4.0.0
>> >> > > > >> > > > > > >> > >> > > > > release
>> >> > > > >> > > > > > >> > >> > > > > >> now? Is this really the only
>> thing
>> >> > > that's
>> >> > > > >> > holding
>> >> > > > >> > > > up
>> >> > > > >> > > > > > this
>> >> > > > >> > > > > > >> > >> > release?
>> >> > > > >> > > > > > >> > >> > > > > >>
>> >> > > > >> > > > > > >> > >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM
>> >> Andrew
>> >> > > > >> Grieve <
>> >> > > > >> > > > > > >> > >> > > agrieve@chromium.org>
>> >> > > > >> > > > > > >> > >> > > > > wrote:
>> >> > > > >> > > > > > >> > >> > > > > >>
>> >> > > > >> > > > > > >> > >> > > > > >>> I think we'll also need to
>> finish
>> >> with
>> >> > > the
>> >> > > > >> > > > whitelist
>> >> > > > >> > > > > > >> changes
>> >> > > > >> > > > > > >> > >> > > > > >>> &
>> >> > > > >> > > > > > >> > >> > have
>> >> > > > >> > > > > > >> > >> > > > > both
>> >> > > > >> > > > > > >> > >> > > > > >>> the legacy and new-way whitelist
>> >> > plugins
>> >> > > > >> > released
>> >> > > > >> > > > > > before
>> >> > > > >> > > > > > >> we
>> >> > > > >> > > > > > >> > >> > > > > >>> can
>> >> > > > >> > > > > > >> > >> > do
>> >> > > > >> > > > > > >> > >> > > a
>> >> > > > >> > > > > > >> > >> > > > > 4.0.0
>> >> > > > >> > > > > > >> > >> > > > > >>> release (otherwise you wouldn't
>> be
>> >> > able
>> >> > > to
>> >> > > > >> > write
>> >> > > > >> > > an
>> >> > > > >> > > > > app
>> >> > > > >> > > > > > >> that
>> >> > > > >> > > > > > >> > >> > > > > >>> hits
>> >> > > > >> > > > > > >> > >> > > the
>> >> > > > >> > > > > > >> > >> > > > > >>> network)
>> >> > > > >> > > > > > >> > >> > > > > >>>
>> >> > > > >> > > > > > >> > >> > > > > >
>> >> > > > >> > > > > > >> > >> > > > > > Just FYI, the whitelist stuff is
>> >> proving
>> >> > > to
>> >> > > > >> be a
>> >> > > > >> > > bit
>> >> > > > >> > > > > of a
>> >> > > > >> > > > > > >> pain
>> >> > > > >> > > > > > >> > >> > point.
>> >> > > > >> > > > > > >> > >> > > > > > I'm using cordova-android@master,
>> >> and
>> >> > > need
>> >> > > > to
>> >> > > > >> > > > install
>> >> > > > >> > > > > > the
>> >> > > > >> > > > > > >> > >> > > > > > legacy-whitelist plugin in order
>> to
>> >> make
>> >> > > > >> network
>> >> > > > >> > > > > > requests.
>> >> > > > >> > > > > > >> > >> > > > > > Once the plugin is installed,
>> >> everything
>> >> > > > >> seems to
>> >> > > > >> > > > work.
>> >> > > > >> > > > > > >> > >> > > > > >
>> >> > > > >> > > > > > >> > >> > > > > > The problem is that the
>> >> legacy-whitelist
>> >> > > > >> plugin
>> >> > > > >> > > > > generates
>> >> > > > >> > > > > > >> > >> > > > > > compile errors with
>> cordova-ios@3.8.0
>> >> ,
>> >> > so
>> >> > > > >> now I
>> >> > > > >> > > > can't
>> >> > > > >> > > > > > just
>> >> > > > >> > > > > > >> > run
>> >> > > > >> > > > > > >> > >> > > > > > `cordova build`, I need to split
>> the
>> >> > > > >> platforms up
>> >> > > > >> > > and
>> >> > > > >> > > > > > >> > >> > > > > > install/uninstall the plugin in
>> >> between.
>> >> > > If
>> >> > > > >> > someone
>> >> > > > >> > > > > > makes a
>> >> > > > >> > > > > > >> > >> > > > > > dev build for Android and forgets
>> the
>> >> > > > plugin,
>> >> > > > >> it
>> >> > > > >> > > will
>> >> > > > >> > > > > > >> appear
>> >> > > > >> > > > > > >> > >> > > > > > to build successfully but not
>> >> actually
>> >> > > > >> function
>> >> > > > >> > > > > properly
>> >> > > > >> > > > > > >> due
>> >> > > > >> > > > > > >> > to
>> >> > > > >> > > > > > >> > >> the whitelist.
>> >> > > > >> > > > > > >> > >> > > > > >
>> >> > > > >> > > > > > >> > >> > > > > > I know, this is all pre-release,
>> so
>> >> pain
>> >> > > is
>> >> > > > >> > > somewhat
>> >> > > > >> > > > > > >> expected
>> >> > > > >> > > > > > >> > >> > > > > > right now. I'm worried about the
>> case
>> >> > > where
>> >> > > > >> > > > > > >> > >> > > > > > cordova-android@4.0.0 is released
>> >> and
>> >> > > > >> > > > > cordova-ios@3.8.0
>> >> > > > >> > > > > > is
>> >> > > > >> > > > > > >> > >> > > > > > still current, and how people
>> >> > > > >> > > > > > >> > >> > can
>> >> > > > >> > > > > > >> > >> > > > > > avoid whitelist breakage there.
>> >> > > > >> > > > > > >> > >> > > > > >
>> >> > > > >> > > > > > >> > >> > > > > >
>> >> > > > >> > > > > > >> ------------------------------
>> >> > > > ------------------------------
>> >> > > > >> > > > > > >> > >> > ---------
>> >> > > > >> > > > > > >> > >> > > > > > To unsubscribe, e-mail:
>> >> > > > >> > > > > > dev-unsubscribe@cordova.apache.org
>> >> > > > >> > > > > > >> > >> > > > > > For additional commands, e-mail:
>> >> > > > >> > > > > > >> dev-help@cordova.apache.org
>> >> > > > >> > > > > > >> > >> > > > > >
>> >> > > > >> > > > > > >> > >> > > > >
>> >> > > > >> > > > > > >> > >> > > > >
>> >> > > > >> > > > > >
>> >> > ------------------------------------------------------------
>> >> > > > >> > > > > > >> > >> > ---------
>> >> > > > >> > > > > > >> > >> > > > > To unsubscribe, e-mail:
>> >> > > > >> > > > > dev-unsubscribe@cordova.apache.org
>> >> > > > >> > > > > > >> > >> > > > > For additional commands, e-mail:
>> >> > > > >> > > > > > dev-help@cordova.apache.org
>> >> > > > >> > > > > > >> > >> > > > >
>> >> > > > >> > > > > > >> > >> > > > >
>> >> > > > >> > > > > > >> > >> > > >
>> >> > > > >> > > > > > >> > >> > >
>> >> > > > >> > > > > > >> > >> >
>> >> > > > >> > > > > > >> > >>
>> >> > > > >> > > > > > >> >
>> >> > > > >> > > > > > >> >
>> >> > > > >> > > > >
>> >> > > > >>
>> >> > ---------------------------------------------------------------------
>> >> > > > >> > > > > > >> > To unsubscribe, e-mail:
>> dev-unsubscribe@cordova.
>> >> > > > apache.org
>> >> > > > >> > > > > > >> > For additional commands, e-mail:
>> >> > > > >> dev-help@cordova.apache.org
>> >> > > > >> > > > > > >> >
>> >> > > > >> > > > > > >> >
>> >> > > > >> > > > > > >>
>> >> > > > >> > > > > > >
>> >> > > > >> > > > > > >
>> >> > > > >> > > > > >
>> >> > > > >> > > > >
>> >> > > > >> > > > >
>> >> > > > >> > > > >
>> >> > > > >> > > > > --
>> >> > > > >> > > > > Carlos Santana
>> >> > > > >> > > > > <cs...@gmail.com>
>> >> > > > >> > > > >
>> >> > > > >> > > >
>> >> > > > >> > >
>> >> > > > >> >
>> >> > > > >>
>> >> > > > >
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> >>
>> >
>> >
>>
>
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Steven Gill <st...@gmail.com>.
I am going to start a discuss thread for plugins release later today.
I'm thinking:
1) Android release
2) Plugins release
3) Tools release 5.0.0 with cordova-wp8, cordova-windows and
cordova-android all updated, npm fetching, fixed --save workflow, etc.
Whitelist plugins have both been released already. So they won't be
included in the plugins release unless we have made changes to them and
want to release updated versions.
On Thu, Apr 9, 2015 at 12:58 PM, Andrew Grieve <ag...@chromium.org> wrote:
> Michal - Good point about npm vs github for links. We tend to tweak docs
> post npm publish, so I've changed the blog post links to github ones.
>
> On Thu, Apr 9, 2015 at 3:55 PM, Andrew Grieve <ag...@chromium.org>
> wrote:
>
> > The plugins being on npm will likely be a bump. Perhaps we should mention
> > that it requires the latest CLI (not yet release one), and defer the blog
> > post until CLI is released?
> >
> > On Thu, Apr 9, 2015 at 2:20 PM, Ian Clelland <ic...@chromium.org>
> > wrote:
> >
> >> Moving from [VOTE] thread:
> >>
> >> On Thu, Apr 9, 2015 at 1:44 PM, Serge Huijben <s....@gmail.com>
> >> wrote:
> >>
> >> > But why is the meta csp tag required?
> >>
> >>
> >> It's not required, only recommended. It's more secure, as it can
> restrict
> >> more network access than the whitelist itself is capable of. (streaming
> >> <audio> and <video> tags, for instance).
> >>
> >> On Thu, Apr 9, 2015 at 1:44 PM, Treggiari, Leo <leo.treggiari@intel.com
> >
> >> wrote:
> >>
> >> > Another question, based upon my understanding, which must be wrong!
> >> >
> >> > The 4.0.0 Android Release will require the cordova-plugin-whitelist in
> >> > order
> >> > to get a whitelist implemented correctly.
> >> >
> >> > Given its name (dash-style) it is only available as an node component.
> >> >
> >> > The is no released CLI that knows how to fetch from npm?
> >> > Or does 4.3, even though I don't see it in the release notes?
> >> > Even so, there are many previous CLI releases which will not work?
> >> >
> >>
> >> This is at least partly resolved by the fact that no released CLI points
> >> to
> >> cordova-android 4.0.0. Once 4.0.0 is released. we will be able to
> release
> >> a
> >> version of the CLI which downloads it by default.
> >>
> >> The whitelist plugins are published already, and discussion is underway
> >> about voting/releasing cordova-lib (and accompanying tools), so I think
> >> there are only two possible timelines:
> >>
> >> A) whitelist plugins released, then cordova-android 4 released, then
> tools
> >> released (supports NPM plugins and Android 4).
> >>
> >> B) plugins released, then tools released (supports NPM plugins), then
> >> cordova-android 4 released, then a small bump of tools is released (to
> pin
> >> to cordova-android 4)
> >>
> >> In either case, users of the released CLI always have a version which
> >> works.
> >>
> >>
> >> > It would be good for the release notes to explain the situation.
> >> >
> >> > Leo
> >> >
> >>
> >>
> >> On Thu, Apr 9, 2015 at 1:24 PM, Michal Mocny <mm...@chromium.org>
> wrote:
> >>
> >> > Splashscreens was mentioned, icons was not. I don't think there is an
> >> > icons change?
> >> >
> >> > On Thu, Apr 9, 2015 at 1:17 PM, Joe Bowser <bo...@gmail.com> wrote:
> >> >
> >> > > So, wasn't there a change regarding icons and spashscreens being
> >> moved? I
> >> > > have no idea if we want to add that, or if adding that should happen
> >> > after
> >> > > the release?
> >> > >
> >> > > On Wed, Apr 8, 2015 at 7:09 PM Andrew Grieve <ag...@chromium.org>
> >> > wrote:
> >> > >
> >> > > > CB-8684 is now merged and I've updated the targetSdk (and made a
> >> couple
> >> > > > other changes).
> >> > > >
> >> > > > I'll start the release process in the morning as long as there no
> >> > > > objections.
> >> > > >
> >> > > >
> >> > > > On Tue, Apr 7, 2015 at 2:20 PM, Andrew Grieve <
> agrieve@chromium.org
> >> >
> >> > > > wrote:
> >> > > >
> >> > > > > I'll start on it once CB-8684 lands (Tony - assuming you'll have
> >> this
> >> > > > done
> >> > > > > shortly and would prefer it lands?)
> >> > > > >
> >> > > > > On Tue, Apr 7, 2015 at 1:33 PM, Jesse <pu...@gmail.com>
> >> > wrote:
> >> > > > >
> >> > > > >> Sweet!
> >> > > > >>
> >> > > > >> @purplecabbage
> >> > > > >> risingj.com
> >> > > > >>
> >> > > > >> On Tue, Apr 7, 2015 at 8:35 AM, Andrew Grieve <
> >> agrieve@chromium.org
> >> > >
> >> > > > >> wrote:
> >> > > > >>
> >> > > > >> > Let's do it!
> >> > > > >> >
> >> > > > >> > On Mon, Apr 6, 2015 at 7:33 PM, Joe Bowser <
> bowserj@gmail.com>
> >> > > wrote:
> >> > > > >> >
> >> > > > >> > > So, I think we should put off the embedder's guide until
> >> after
> >> > the
> >> > > > >> > > release. A lot of it has changed, and since we're still
> >> > > technically
> >> > > > >> > > obligated to support the 3.x release tree for six months,
> >> that
> >> > > > should
> >> > > > >> buy
> >> > > > >> > > us some time to figure out how that is going to work.
> >> Getting
> >> > > > >> Cordova to
> >> > > > >> > > work with a vanilla Android Studio project is a non-trivial
> >> > task.
> >> > > > >> > >
> >> > > > >> > > Given that everything else appears to be done, should we
> >> start
> >> > > > voting
> >> > > > >> on
> >> > > > >> > an
> >> > > > >> > > RC for this? What do people think?
> >> > > > >> > >
> >> > > > >> > >
> >> > > > >> > >
> >> > > > >> > > On Thu, Mar 19, 2015 at 10:31 AM Andrew Grieve <
> >> > > > agrieve@chromium.org>
> >> > > > >> > > wrote:
> >> > > > >> > >
> >> > > > >> > > > Here's issues:
> >> > > > >> > > > https://issues.apache.org/jira/browse/CB-8715 (docs)
> >> > > > >> > > > https://issues.apache.org/jira/browse/CB-8716
> (whitelist)
> >> > > > >> > > > https://issues.apache.org/jira/browse/CB-8717 (write
> >> > > > >> RELEASENOTES.md)
> >> > > > >> > > >
> >> > > > >> > > > On Tue, Mar 17, 2015 at 10:15 AM, Carlos Santana <
> >> > > > >> csantana23@gmail.com
> >> > > > >> > >
> >> > > > >> > > > wrote:
> >> > > > >> > > >
> >> > > > >> > > > > I would say let's start RC testing and voting, But not
> >> pin
> >> > the
> >> > > > >> > version
> >> > > > >> > > in
> >> > > > >> > > > > Cordova CLI until the tasks that Andrew mentioned are
> >> done.
> >> > > > >> > > > > Andrew can you create the JIRA Items for the tasks that
> >> need
> >> > > to
> >> > > > be
> >> > > > >> > > done.
> >> > > > >> > > > I
> >> > > > >> > > > > thought there was a discussion about creating JIRA
> Items
> >> to
> >> > > help
> >> > > > >> > track
> >> > > > >> > > > and
> >> > > > >> > > > > know what's left for release something.
> >> > > > >> > > > >
> >> > > > >> > > > > - upgrade guide,
> >> > > > >> > > > > - publishing whitelist plugins,
> >> > > > >> > > > > - and making it so that the default project template
> >> > includes
> >> > > > >> <plugin
> >> > > > >> > > > > name="cordova-plugin-whitelist" />)
> >> > > > >> > > > >
> >> > > > >> > > > >
> >> > > > >> > > > > On Mon, Mar 16, 2015 at 11:21 PM, Ian Clelland <
> >> > > > >> > iclelland@chromium.org
> >> > > > >> > > >
> >> > > > >> > > > > wrote:
> >> > > > >> > > > >
> >> > > > >> > > > > > We'll probably need at least an RC for the whitelist
> >> > plugin,
> >> > > > if
> >> > > > >> > not a
> >> > > > >> > > > > vote,
> >> > > > >> > > > > > to be able to vote on this.
> >> > > > >> > > > > >
> >> > > > >> > > > > > Or can we just include instructions like "Use
> >> > > > >> > > > > > cordova-plugin-whitelist@f70b1bc for testing" while
> we
> >> > > start
> >> > > > >> the
> >> > > > >> > > > > official
> >> > > > >> > > > > > release process for the plugins?
> >> > > > >> > > > > >
> >> > > > >> > > > > > On Mon, Mar 16, 2015 at 11:17 PM, Ian Clelland <
> >> > > > >> > > iclelland@chromium.org
> >> > > > >> > > > >
> >> > > > >> > > > > > wrote:
> >> > > > >> > > > > >
> >> > > > >> > > > > > > +1 -- Let's get this out the door :)
> >> > > > >> > > > > > > I'll see what I can get done to move it in that
> >> > direction.
> >> > > > >> > > > > > >
> >> > > > >> > > > > > > On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <
> >> > > > >> > > agrieve@chromium.org
> >> > > > >> > > > >
> >> > > > >> > > > > > > wrote:
> >> > > > >> > > > > > >
> >> > > > >> > > > > > >> Everything's ready afaik (minus upgrade guide,
> >> > publishing
> >> > > > >> > > whitelist
> >> > > > >> > > > > > >> plugins, and making it so that the default project
> >> > > template
> >> > > > >> > > includes
> >> > > > >> > > > > > >> <plugin name="cordova-plugin-whitelist" />). Maybe
> >> > let's
> >> > > > do
> >> > > > >> a RC
> >> > > > >> > > > while
> >> > > > >> > > > > > we
> >> > > > >> > > > > > >> wait on these things being finished up?
> >> > > > >> > > > > > >>
> >> > > > >> > > > > > >> If anyone wants to take on any of these tasks,
> that
> >> > would
> >> > > > be
> >> > > > >> > > > awesome.
> >> > > > >> > > > > > >>
> >> > > > >> > > > > > >> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <
> >> > > > shazron@gmail.com>
> >> > > > >> > > wrote:
> >> > > > >> > > > > > >>
> >> > > > >> > > > > > >> > +1 for vote thread, let's get this thing out so
> >> > people
> >> > > > >> (that
> >> > > > >> > are
> >> > > > >> > > > not
> >> > > > >> > > > > > >> > us) can test...
> >> > > > >> > > > > > >> >
> >> > > > >> > > > > > >> >
> >> > > > >> > > > > > >> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <
> >> > > > >> > bowserj@gmail.com>
> >> > > > >> > > > > > wrote:
> >> > > > >> > > > > > >> > > OK, this is a three month old thread, and
> we're
> >> > > waiting
> >> > > > >> on a
> >> > > > >> > > > > > >> discussion
> >> > > > >> > > > > > >> > > before we release something? I really think we
> >> > should
> >> > > > go
> >> > > > >> to
> >> > > > >> > a
> >> > > > >> > > > vote
> >> > > > >> > > > > > >> thread
> >> > > > >> > > > > > >> > > now that we have a legacy whitelist plugin
> and a
> >> > new
> >> > > > >> style
> >> > > > >> > > > > whitelist
> >> > > > >> > > > > > >> > > plugin. We shouldn't keep constantly delaying
> >> this
> >> > > > >> release
> >> > > > >> > > > > because
> >> > > > >> > > > > > of
> >> > > > >> > > > > > >> > > what's happening on other platforms,
> especially
> >> > since
> >> > > > we
> >> > > > >> > > already
> >> > > > >> > > > > > >> > pluginized
> >> > > > >> > > > > > >> > > the whitelist.
> >> > > > >> > > > > > >> > >
> >> > > > >> > > > > > >> > > Can we please release soon?
> >> > > > >> > > > > > >> > >
> >> > > > >> > > > > > >> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil
> >> Khandelwal <
> >> > > > >> > > > > > >> > nikhilkh@microsoft.com>
> >> > > > >> > > > > > >> > > wrote:
> >> > > > >> > > > > > >> > >
> >> > > > >> > > > > > >> > >> I know we discussed a couple of approaches
> >> > > > implementing
> >> > > > >> the
> >> > > > >> > > > > default
> >> > > > >> > > > > > >> > >> whitelist policy for Android/iOS - either
> every
> >> > app
> >> > > > >> would
> >> > > > >> > be
> >> > > > >> > > > > > >> required to
> >> > > > >> > > > > > >> > >> include the whitelist plugin or have it have
> >> smart
> >> > > > >> defaults
> >> > > > >> > > in
> >> > > > >> > > > > the
> >> > > > >> > > > > > >> > platform
> >> > > > >> > > > > > >> > >> implementation and the plugin being able to
> >> > override
> >> > > > >> them.
> >> > > > >> > > > > > >> > >>
> >> > > > >> > > > > > >> > >> I don't think that thread closed with any
> >> > > conclusions.
> >> > > > >> > > > > > >> > >>
> >> > > > >> > > > > > >> > >> Thanks,
> >> > > > >> > > > > > >> > >> Nikhil
> >> > > > >> > > > > > >> > >>
> >> > > > >> > > > > > >> > >>
> >> > > > >> > > > > > >> > >> -----Original Message-----
> >> > > > >> > > > > > >> > >> From: Joe Bowser [mailto:bowserj@gmail.com]
> >> > > > >> > > > > > >> > >> Sent: Thursday, March 12, 2015 11:23 AM
> >> > > > >> > > > > > >> > >> To: dev
> >> > > > >> > > > > > >> > >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0
> >> > Release
> >> > > > >> > > > > > >> > >>
> >> > > > >> > > > > > >> > >> OK, so right now it's just docs? How soon can
> >> we
> >> > > get a
> >> > > > >> VOTE
> >> > > > >> > > > > thread
> >> > > > >> > > > > > >> > started
> >> > > > >> > > > > > >> > >> for 4.0.0?
> >> > > > >> > > > > > >> > >>
> >> > > > >> > > > > > >> > >> On Wed, Mar 4, 2015 at 10:47 AM Andrew
> Grieve <
> >> > > > >> > > > > > agrieve@chromium.org>
> >> > > > >> > > > > > >> > >> wrote:
> >> > > > >> > > > > > >> > >>
> >> > > > >> > > > > > >> > >> > mobilespec is now working again... Took
> >> longer
> >> > > than
> >> > > > I
> >> > > > >> > would
> >> > > > >> > > > > have
> >> > > > >> > > > > > >> > >> > liked, but did you know that on Android
> >> > FileReader
> >> > > > >> > triggers
> >> > > > >> > > > > > >> > >> > shouldInterceptRequest() with Blob URLs!?
> >> > > > >> > > > > > >> > >> >
> >> > > > >> > > > > > >> > >> > Separate thread is already happening re:
> >> > > whitelists,
> >> > > > >> so
> >> > > > >> > > once
> >> > > > >> > > > > > that's
> >> > > > >> > > > > > >> > >> > figured out, it's just docs afaict.
> >> > > > >> > > > > > >> > >> >
> >> > > > >> > > > > > >> > >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian
> >> Clelland <
> >> > > > >> > > > > > >> iclelland@chromium.org
> >> > > > >> > > > > > >> > >
> >> > > > >> > > > > > >> > >> > wrote:
> >> > > > >> > > > > > >> > >> >
> >> > > > >> > > > > > >> > >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <
> >> > > > >> > > > > purplecabbage@gmail.com
> >> > > > >> > > > > > >
> >> > > > >> > > > > > >> > wrote:
> >> > > > >> > > > > > >> > >> > >
> >> > > > >> > > > > > >> > >> > > > We should start a new whitelist plugin
> >> > related
> >> > > > >> > thread.
> >> > > > >> > > > > > >> > >> > > >
> >> > > > >> > > > > > >> > >> > > > Why is a plugin blocking a release?
> >> Default
> >> > > > (aka
> >> > > > >> > > > > no-plugin)
> >> > > > >> > > > > > >> > >> > > > behavior should be to allow all network
> >> > > requests
> >> > > > >> > > > shouldn't
> >> > > > >> > > > > > it?
> >> > > > >> > > > > > >> > >> > >
> >> > > > >> > > > > > >> > >> > >
> >> > > > >> > > > > > >> > >> > > Well, that just might be a blacklist then
> >> :)
> >> > > > >> > > > > > >> > >> > >
> >> > > > >> > > > > > >> > >> > >
> >> > > > >> > > > > > >> > >> > > > This thread is a
> >> > > > >> > > > > > >> > >> > > > month long, and not the first
> discussion
> >> of
> >> > > > 4.0.0
> >> > > > >> for
> >> > > > >> > > > > > Android.
> >> > > > >> > > > > > >> > >> > > >
> >> > > > >> > > > > > >> > >> > >
> >> > > > >> > > > > > >> > >> > > Seriously, though -- the whitelist
> >> discussion
> >> > is
> >> > > > >> much
> >> > > > >> > > > longer
> >> > > > >> > > > > > than
> >> > > > >> > > > > > >> > >> > > that,
> >> > > > >> > > > > > >> > >> > and
> >> > > > >> > > > > > >> > >> > > this isn't the first time that the
> default
> >> > > > >> > > > no-network-access
> >> > > > >> > > > > > >> policy
> >> > > > >> > > > > > >> > >> > > has been brought up:
> >> > > > >> > > > > > >> > >> > >
> >> > > > >> > > > > > >> > >> > > (Here's the first question, from *July*:
> >> > > > >> > > > > > >> > >> > >
> >> http://markmail.org/message/t4vj4saisem2mcgw
> >> > > > >> > > > > > >> > >> > > Here's where I mentioned what the
> >> implemented
> >> > > > policy
> >> > > > >> > was:
> >> > > > >> > > > > > >> > >> > >
> >> http://markmail.org/message/s4necfnh4hnblpjm
> >> > > > >> > > > > > >> > >> > > And in another discussion:
> >> > > > >> > > > > > >> > >> > >
> >> http://markmail.org/message/ap7syhqysizmsvrz)
> >> > > > >> > > > > > >> > >> > >
> >> > > > >> > > > > > >> > >> > > If we want to reconsider that decision,
> >> then
> >> > we
> >> > > > >> should
> >> > > > >> > > > > > certainly
> >> > > > >> > > > > > >> do
> >> > > > >> > > > > > >> > >> > > so before we cut a release. I think it
> >> would
> >> > be
> >> > > a
> >> > > > >> real
> >> > > > >> > > > > problem
> >> > > > >> > > > > > to
> >> > > > >> > > > > > >> > >> > > change it afterwards, so let's get it
> >> right.
> >> > > > >> > > > > > >> > >> > >
> >> > > > >> > > > > > >> > >> > > Also, it's not the plugin itself that's
> >> > blocking
> >> > > > the
> >> > > > >> > > > release,
> >> > > > >> > > > > > >> it's
> >> > > > >> > > > > > >> > >> > > us making sure that we've implemented the
> >> core
> >> > > > hooks
> >> > > > >> > > > > correctly
> >> > > > >> > > > > > so
> >> > > > >> > > > > > >> > >> > > that the plugin can actually do its job,
> >> and
> >> > > that
> >> > > > >> > people
> >> > > > >> > > > who
> >> > > > >> > > > > > >> don't
> >> > > > >> > > > > > >> > >> > > want that particular plugin can make a
> >> better
> >> > > one.
> >> > > > >> > > > > > >> > >> > >
> >> > > > >> > > > > > >> > >> > > (It is also an issue that a plugin,
> >> required
> >> > for
> >> > > > >> > > > > > cordova-android
> >> > > > >> > > > > > >> > >> > > 4.0.0, breaks apps which are also
> building
> >> for
> >> > > > >> > > cordova-ios
> >> > > > >> > > > > > 3.8.0.
> >> > > > >> > > > > > >> > >> > > I'll take a
> >> > > > >> > > > > > >> > >> > look
> >> > > > >> > > > > > >> > >> > > at that, and either remove the ios-native
> >> > > portions
> >> > > > >> of
> >> > > > >> > the
> >> > > > >> > > > > > >> whitelist
> >> > > > >> > > > > > >> > >> > plugin,
> >> > > > >> > > > > > >> > >> > > or neuter it so that it doesn't interfere
> >> with
> >> > > an
> >> > > > >> ios
> >> > > > >> > app
> >> > > > >> > > > if
> >> > > > >> > > > > > it's
> >> > > > >> > > > > > >> > >> > > not on the unplug-whitelist branch of
> that
> >> > > repo.)
> >> > > > >> > > > > > >> > >> > >
> >> > > > >> > > > > > >> > >> > > Ian
> >> > > > >> > > > > > >> > >> > >
> >> > > > >> > > > > > >> > >> > >
> >> > > > >> > > > > > >> > >> > > > @purplecabbage
> >> > > > >> > > > > > >> > >> > > > risingj.com
> >> > > > >> > > > > > >> > >> > > >
> >> > > > >> > > > > > >> > >> > > > On Mon, Mar 2, 2015 at 2:02 PM,
> Shazron <
> >> > > > >> > > > shazron@gmail.com
> >> > > > >> > > > > >
> >> > > > >> > > > > > >> > wrote:
> >> > > > >> > > > > > >> > >> > > >
> >> > > > >> > > > > > >> > >> > > > > legacy-whitelist-plugin should be
> >> fixed so
> >> > > > that
> >> > > > >> it
> >> > > > >> > > > > compiles
> >> > > > >> > > > > > >> on
> >> > > > >> > > > > > >> > >> > > > > cordova-ios@3.8.0. It shouldn't be a
> >> > > problem
> >> > > > to
> >> > > > >> > fix
> >> > > > >> > > > this
> >> > > > >> > > > > > at
> >> > > > >> > > > > > >> > >> > > > > compile
> >> > > > >> > > > > > >> > >> > or
> >> > > > >> > > > > > >> > >> > > > > run-time (whichever is applicable
> here
> >> > > related
> >> > > > >> to
> >> > > > >> > the
> >> > > > >> > > > > > compile
> >> > > > >> > > > > > >> > >> > > > > error)
> >> > > > >> > > > > > >> > >> > > > >
> >> > > > >> > > > > > >> > >> > > > > On Mon, Mar 2, 2015 at 1:47 PM,
> Darryl
> >> > Pogue
> >> > > > >> > > > > > >> > >> > > > > <dv...@gmail.com>
> >> > > > >> > > > > > >> > >> > > > wrote:
> >> > > > >> > > > > > >> > >> > > > > > On 2 March 2015 at 13:37, Joe
> Bowser
> >> <
> >> > > > >> > > > > bowserj@gmail.com>
> >> > > > >> > > > > > >> > wrote:
> >> > > > >> > > > > > >> > >> > > > > >> So, right now the whitelist
> changes
> >> are
> >> > > > >> what's
> >> > > > >> > > > holding
> >> > > > >> > > > > > up
> >> > > > >> > > > > > >> the
> >> > > > >> > > > > > >> > >> > 4.0.0
> >> > > > >> > > > > > >> > >> > > > > release
> >> > > > >> > > > > > >> > >> > > > > >> now? Is this really the only
> thing
> >> > > that's
> >> > > > >> > holding
> >> > > > >> > > > up
> >> > > > >> > > > > > this
> >> > > > >> > > > > > >> > >> > release?
> >> > > > >> > > > > > >> > >> > > > > >>
> >> > > > >> > > > > > >> > >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM
> >> Andrew
> >> > > > >> Grieve <
> >> > > > >> > > > > > >> > >> > > agrieve@chromium.org>
> >> > > > >> > > > > > >> > >> > > > > wrote:
> >> > > > >> > > > > > >> > >> > > > > >>
> >> > > > >> > > > > > >> > >> > > > > >>> I think we'll also need to finish
> >> with
> >> > > the
> >> > > > >> > > > whitelist
> >> > > > >> > > > > > >> changes
> >> > > > >> > > > > > >> > >> > > > > >>> &
> >> > > > >> > > > > > >> > >> > have
> >> > > > >> > > > > > >> > >> > > > > both
> >> > > > >> > > > > > >> > >> > > > > >>> the legacy and new-way whitelist
> >> > plugins
> >> > > > >> > released
> >> > > > >> > > > > > before
> >> > > > >> > > > > > >> we
> >> > > > >> > > > > > >> > >> > > > > >>> can
> >> > > > >> > > > > > >> > >> > do
> >> > > > >> > > > > > >> > >> > > a
> >> > > > >> > > > > > >> > >> > > > > 4.0.0
> >> > > > >> > > > > > >> > >> > > > > >>> release (otherwise you wouldn't
> be
> >> > able
> >> > > to
> >> > > > >> > write
> >> > > > >> > > an
> >> > > > >> > > > > app
> >> > > > >> > > > > > >> that
> >> > > > >> > > > > > >> > >> > > > > >>> hits
> >> > > > >> > > > > > >> > >> > > the
> >> > > > >> > > > > > >> > >> > > > > >>> network)
> >> > > > >> > > > > > >> > >> > > > > >>>
> >> > > > >> > > > > > >> > >> > > > > >
> >> > > > >> > > > > > >> > >> > > > > > Just FYI, the whitelist stuff is
> >> proving
> >> > > to
> >> > > > >> be a
> >> > > > >> > > bit
> >> > > > >> > > > > of a
> >> > > > >> > > > > > >> pain
> >> > > > >> > > > > > >> > >> > point.
> >> > > > >> > > > > > >> > >> > > > > > I'm using cordova-android@master,
> >> and
> >> > > need
> >> > > > to
> >> > > > >> > > > install
> >> > > > >> > > > > > the
> >> > > > >> > > > > > >> > >> > > > > > legacy-whitelist plugin in order to
> >> make
> >> > > > >> network
> >> > > > >> > > > > > requests.
> >> > > > >> > > > > > >> > >> > > > > > Once the plugin is installed,
> >> everything
> >> > > > >> seems to
> >> > > > >> > > > work.
> >> > > > >> > > > > > >> > >> > > > > >
> >> > > > >> > > > > > >> > >> > > > > > The problem is that the
> >> legacy-whitelist
> >> > > > >> plugin
> >> > > > >> > > > > generates
> >> > > > >> > > > > > >> > >> > > > > > compile errors with
> cordova-ios@3.8.0
> >> ,
> >> > so
> >> > > > >> now I
> >> > > > >> > > > can't
> >> > > > >> > > > > > just
> >> > > > >> > > > > > >> > run
> >> > > > >> > > > > > >> > >> > > > > > `cordova build`, I need to split
> the
> >> > > > >> platforms up
> >> > > > >> > > and
> >> > > > >> > > > > > >> > >> > > > > > install/uninstall the plugin in
> >> between.
> >> > > If
> >> > > > >> > someone
> >> > > > >> > > > > > makes a
> >> > > > >> > > > > > >> > >> > > > > > dev build for Android and forgets
> the
> >> > > > plugin,
> >> > > > >> it
> >> > > > >> > > will
> >> > > > >> > > > > > >> appear
> >> > > > >> > > > > > >> > >> > > > > > to build successfully but not
> >> actually
> >> > > > >> function
> >> > > > >> > > > > properly
> >> > > > >> > > > > > >> due
> >> > > > >> > > > > > >> > to
> >> > > > >> > > > > > >> > >> the whitelist.
> >> > > > >> > > > > > >> > >> > > > > >
> >> > > > >> > > > > > >> > >> > > > > > I know, this is all pre-release, so
> >> pain
> >> > > is
> >> > > > >> > > somewhat
> >> > > > >> > > > > > >> expected
> >> > > > >> > > > > > >> > >> > > > > > right now. I'm worried about the
> case
> >> > > where
> >> > > > >> > > > > > >> > >> > > > > > cordova-android@4.0.0 is released
> >> and
> >> > > > >> > > > > cordova-ios@3.8.0
> >> > > > >> > > > > > is
> >> > > > >> > > > > > >> > >> > > > > > still current, and how people
> >> > > > >> > > > > > >> > >> > can
> >> > > > >> > > > > > >> > >> > > > > > avoid whitelist breakage there.
> >> > > > >> > > > > > >> > >> > > > > >
> >> > > > >> > > > > > >> > >> > > > > >
> >> > > > >> > > > > > >> ------------------------------
> >> > > > ------------------------------
> >> > > > >> > > > > > >> > >> > ---------
> >> > > > >> > > > > > >> > >> > > > > > To unsubscribe, e-mail:
> >> > > > >> > > > > > dev-unsubscribe@cordova.apache.org
> >> > > > >> > > > > > >> > >> > > > > > For additional commands, e-mail:
> >> > > > >> > > > > > >> dev-help@cordova.apache.org
> >> > > > >> > > > > > >> > >> > > > > >
> >> > > > >> > > > > > >> > >> > > > >
> >> > > > >> > > > > > >> > >> > > > >
> >> > > > >> > > > > >
> >> > ------------------------------------------------------------
> >> > > > >> > > > > > >> > >> > ---------
> >> > > > >> > > > > > >> > >> > > > > To unsubscribe, e-mail:
> >> > > > >> > > > > dev-unsubscribe@cordova.apache.org
> >> > > > >> > > > > > >> > >> > > > > For additional commands, e-mail:
> >> > > > >> > > > > > dev-help@cordova.apache.org
> >> > > > >> > > > > > >> > >> > > > >
> >> > > > >> > > > > > >> > >> > > > >
> >> > > > >> > > > > > >> > >> > > >
> >> > > > >> > > > > > >> > >> > >
> >> > > > >> > > > > > >> > >> >
> >> > > > >> > > > > > >> > >>
> >> > > > >> > > > > > >> >
> >> > > > >> > > > > > >> >
> >> > > > >> > > > >
> >> > > > >>
> >> > ---------------------------------------------------------------------
> >> > > > >> > > > > > >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.
> >> > > > apache.org
> >> > > > >> > > > > > >> > For additional commands, e-mail:
> >> > > > >> dev-help@cordova.apache.org
> >> > > > >> > > > > > >> >
> >> > > > >> > > > > > >> >
> >> > > > >> > > > > > >>
> >> > > > >> > > > > > >
> >> > > > >> > > > > > >
> >> > > > >> > > > > >
> >> > > > >> > > > >
> >> > > > >> > > > >
> >> > > > >> > > > >
> >> > > > >> > > > > --
> >> > > > >> > > > > Carlos Santana
> >> > > > >> > > > > <cs...@gmail.com>
> >> > > > >> > > > >
> >> > > > >> > > >
> >> > > > >> > >
> >> > > > >> >
> >> > > > >>
> >> > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Michal - Good point about npm vs github for links. We tend to tweak docs
post npm publish, so I've changed the blog post links to github ones.
On Thu, Apr 9, 2015 at 3:55 PM, Andrew Grieve <ag...@chromium.org> wrote:
> The plugins being on npm will likely be a bump. Perhaps we should mention
> that it requires the latest CLI (not yet release one), and defer the blog
> post until CLI is released?
>
> On Thu, Apr 9, 2015 at 2:20 PM, Ian Clelland <ic...@chromium.org>
> wrote:
>
>> Moving from [VOTE] thread:
>>
>> On Thu, Apr 9, 2015 at 1:44 PM, Serge Huijben <s....@gmail.com>
>> wrote:
>>
>> > But why is the meta csp tag required?
>>
>>
>> It's not required, only recommended. It's more secure, as it can restrict
>> more network access than the whitelist itself is capable of. (streaming
>> <audio> and <video> tags, for instance).
>>
>> On Thu, Apr 9, 2015 at 1:44 PM, Treggiari, Leo <le...@intel.com>
>> wrote:
>>
>> > Another question, based upon my understanding, which must be wrong!
>> >
>> > The 4.0.0 Android Release will require the cordova-plugin-whitelist in
>> > order
>> > to get a whitelist implemented correctly.
>> >
>> > Given its name (dash-style) it is only available as an node component.
>> >
>> > The is no released CLI that knows how to fetch from npm?
>> > Or does 4.3, even though I don't see it in the release notes?
>> > Even so, there are many previous CLI releases which will not work?
>> >
>>
>> This is at least partly resolved by the fact that no released CLI points
>> to
>> cordova-android 4.0.0. Once 4.0.0 is released. we will be able to release
>> a
>> version of the CLI which downloads it by default.
>>
>> The whitelist plugins are published already, and discussion is underway
>> about voting/releasing cordova-lib (and accompanying tools), so I think
>> there are only two possible timelines:
>>
>> A) whitelist plugins released, then cordova-android 4 released, then tools
>> released (supports NPM plugins and Android 4).
>>
>> B) plugins released, then tools released (supports NPM plugins), then
>> cordova-android 4 released, then a small bump of tools is released (to pin
>> to cordova-android 4)
>>
>> In either case, users of the released CLI always have a version which
>> works.
>>
>>
>> > It would be good for the release notes to explain the situation.
>> >
>> > Leo
>> >
>>
>>
>> On Thu, Apr 9, 2015 at 1:24 PM, Michal Mocny <mm...@chromium.org> wrote:
>>
>> > Splashscreens was mentioned, icons was not. I don't think there is an
>> > icons change?
>> >
>> > On Thu, Apr 9, 2015 at 1:17 PM, Joe Bowser <bo...@gmail.com> wrote:
>> >
>> > > So, wasn't there a change regarding icons and spashscreens being
>> moved? I
>> > > have no idea if we want to add that, or if adding that should happen
>> > after
>> > > the release?
>> > >
>> > > On Wed, Apr 8, 2015 at 7:09 PM Andrew Grieve <ag...@chromium.org>
>> > wrote:
>> > >
>> > > > CB-8684 is now merged and I've updated the targetSdk (and made a
>> couple
>> > > > other changes).
>> > > >
>> > > > I'll start the release process in the morning as long as there no
>> > > > objections.
>> > > >
>> > > >
>> > > > On Tue, Apr 7, 2015 at 2:20 PM, Andrew Grieve <agrieve@chromium.org
>> >
>> > > > wrote:
>> > > >
>> > > > > I'll start on it once CB-8684 lands (Tony - assuming you'll have
>> this
>> > > > done
>> > > > > shortly and would prefer it lands?)
>> > > > >
>> > > > > On Tue, Apr 7, 2015 at 1:33 PM, Jesse <pu...@gmail.com>
>> > wrote:
>> > > > >
>> > > > >> Sweet!
>> > > > >>
>> > > > >> @purplecabbage
>> > > > >> risingj.com
>> > > > >>
>> > > > >> On Tue, Apr 7, 2015 at 8:35 AM, Andrew Grieve <
>> agrieve@chromium.org
>> > >
>> > > > >> wrote:
>> > > > >>
>> > > > >> > Let's do it!
>> > > > >> >
>> > > > >> > On Mon, Apr 6, 2015 at 7:33 PM, Joe Bowser <bo...@gmail.com>
>> > > wrote:
>> > > > >> >
>> > > > >> > > So, I think we should put off the embedder's guide until
>> after
>> > the
>> > > > >> > > release. A lot of it has changed, and since we're still
>> > > technically
>> > > > >> > > obligated to support the 3.x release tree for six months,
>> that
>> > > > should
>> > > > >> buy
>> > > > >> > > us some time to figure out how that is going to work.
>> Getting
>> > > > >> Cordova to
>> > > > >> > > work with a vanilla Android Studio project is a non-trivial
>> > task.
>> > > > >> > >
>> > > > >> > > Given that everything else appears to be done, should we
>> start
>> > > > voting
>> > > > >> on
>> > > > >> > an
>> > > > >> > > RC for this? What do people think?
>> > > > >> > >
>> > > > >> > >
>> > > > >> > >
>> > > > >> > > On Thu, Mar 19, 2015 at 10:31 AM Andrew Grieve <
>> > > > agrieve@chromium.org>
>> > > > >> > > wrote:
>> > > > >> > >
>> > > > >> > > > Here's issues:
>> > > > >> > > > https://issues.apache.org/jira/browse/CB-8715 (docs)
>> > > > >> > > > https://issues.apache.org/jira/browse/CB-8716 (whitelist)
>> > > > >> > > > https://issues.apache.org/jira/browse/CB-8717 (write
>> > > > >> RELEASENOTES.md)
>> > > > >> > > >
>> > > > >> > > > On Tue, Mar 17, 2015 at 10:15 AM, Carlos Santana <
>> > > > >> csantana23@gmail.com
>> > > > >> > >
>> > > > >> > > > wrote:
>> > > > >> > > >
>> > > > >> > > > > I would say let's start RC testing and voting, But not
>> pin
>> > the
>> > > > >> > version
>> > > > >> > > in
>> > > > >> > > > > Cordova CLI until the tasks that Andrew mentioned are
>> done.
>> > > > >> > > > > Andrew can you create the JIRA Items for the tasks that
>> need
>> > > to
>> > > > be
>> > > > >> > > done.
>> > > > >> > > > I
>> > > > >> > > > > thought there was a discussion about creating JIRA Items
>> to
>> > > help
>> > > > >> > track
>> > > > >> > > > and
>> > > > >> > > > > know what's left for release something.
>> > > > >> > > > >
>> > > > >> > > > > - upgrade guide,
>> > > > >> > > > > - publishing whitelist plugins,
>> > > > >> > > > > - and making it so that the default project template
>> > includes
>> > > > >> <plugin
>> > > > >> > > > > name="cordova-plugin-whitelist" />)
>> > > > >> > > > >
>> > > > >> > > > >
>> > > > >> > > > > On Mon, Mar 16, 2015 at 11:21 PM, Ian Clelland <
>> > > > >> > iclelland@chromium.org
>> > > > >> > > >
>> > > > >> > > > > wrote:
>> > > > >> > > > >
>> > > > >> > > > > > We'll probably need at least an RC for the whitelist
>> > plugin,
>> > > > if
>> > > > >> > not a
>> > > > >> > > > > vote,
>> > > > >> > > > > > to be able to vote on this.
>> > > > >> > > > > >
>> > > > >> > > > > > Or can we just include instructions like "Use
>> > > > >> > > > > > cordova-plugin-whitelist@f70b1bc for testing" while we
>> > > start
>> > > > >> the
>> > > > >> > > > > official
>> > > > >> > > > > > release process for the plugins?
>> > > > >> > > > > >
>> > > > >> > > > > > On Mon, Mar 16, 2015 at 11:17 PM, Ian Clelland <
>> > > > >> > > iclelland@chromium.org
>> > > > >> > > > >
>> > > > >> > > > > > wrote:
>> > > > >> > > > > >
>> > > > >> > > > > > > +1 -- Let's get this out the door :)
>> > > > >> > > > > > > I'll see what I can get done to move it in that
>> > direction.
>> > > > >> > > > > > >
>> > > > >> > > > > > > On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <
>> > > > >> > > agrieve@chromium.org
>> > > > >> > > > >
>> > > > >> > > > > > > wrote:
>> > > > >> > > > > > >
>> > > > >> > > > > > >> Everything's ready afaik (minus upgrade guide,
>> > publishing
>> > > > >> > > whitelist
>> > > > >> > > > > > >> plugins, and making it so that the default project
>> > > template
>> > > > >> > > includes
>> > > > >> > > > > > >> <plugin name="cordova-plugin-whitelist" />). Maybe
>> > let's
>> > > > do
>> > > > >> a RC
>> > > > >> > > > while
>> > > > >> > > > > > we
>> > > > >> > > > > > >> wait on these things being finished up?
>> > > > >> > > > > > >>
>> > > > >> > > > > > >> If anyone wants to take on any of these tasks, that
>> > would
>> > > > be
>> > > > >> > > > awesome.
>> > > > >> > > > > > >>
>> > > > >> > > > > > >> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <
>> > > > shazron@gmail.com>
>> > > > >> > > wrote:
>> > > > >> > > > > > >>
>> > > > >> > > > > > >> > +1 for vote thread, let's get this thing out so
>> > people
>> > > > >> (that
>> > > > >> > are
>> > > > >> > > > not
>> > > > >> > > > > > >> > us) can test...
>> > > > >> > > > > > >> >
>> > > > >> > > > > > >> >
>> > > > >> > > > > > >> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <
>> > > > >> > bowserj@gmail.com>
>> > > > >> > > > > > wrote:
>> > > > >> > > > > > >> > > OK, this is a three month old thread, and we're
>> > > waiting
>> > > > >> on a
>> > > > >> > > > > > >> discussion
>> > > > >> > > > > > >> > > before we release something? I really think we
>> > should
>> > > > go
>> > > > >> to
>> > > > >> > a
>> > > > >> > > > vote
>> > > > >> > > > > > >> thread
>> > > > >> > > > > > >> > > now that we have a legacy whitelist plugin and a
>> > new
>> > > > >> style
>> > > > >> > > > > whitelist
>> > > > >> > > > > > >> > > plugin. We shouldn't keep constantly delaying
>> this
>> > > > >> release
>> > > > >> > > > > because
>> > > > >> > > > > > of
>> > > > >> > > > > > >> > > what's happening on other platforms, especially
>> > since
>> > > > we
>> > > > >> > > already
>> > > > >> > > > > > >> > pluginized
>> > > > >> > > > > > >> > > the whitelist.
>> > > > >> > > > > > >> > >
>> > > > >> > > > > > >> > > Can we please release soon?
>> > > > >> > > > > > >> > >
>> > > > >> > > > > > >> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil
>> Khandelwal <
>> > > > >> > > > > > >> > nikhilkh@microsoft.com>
>> > > > >> > > > > > >> > > wrote:
>> > > > >> > > > > > >> > >
>> > > > >> > > > > > >> > >> I know we discussed a couple of approaches
>> > > > implementing
>> > > > >> the
>> > > > >> > > > > default
>> > > > >> > > > > > >> > >> whitelist policy for Android/iOS - either every
>> > app
>> > > > >> would
>> > > > >> > be
>> > > > >> > > > > > >> required to
>> > > > >> > > > > > >> > >> include the whitelist plugin or have it have
>> smart
>> > > > >> defaults
>> > > > >> > > in
>> > > > >> > > > > the
>> > > > >> > > > > > >> > platform
>> > > > >> > > > > > >> > >> implementation and the plugin being able to
>> > override
>> > > > >> them.
>> > > > >> > > > > > >> > >>
>> > > > >> > > > > > >> > >> I don’t think that thread closed with any
>> > > conclusions.
>> > > > >> > > > > > >> > >>
>> > > > >> > > > > > >> > >> Thanks,
>> > > > >> > > > > > >> > >> Nikhil
>> > > > >> > > > > > >> > >>
>> > > > >> > > > > > >> > >>
>> > > > >> > > > > > >> > >> -----Original Message-----
>> > > > >> > > > > > >> > >> From: Joe Bowser [mailto:bowserj@gmail.com]
>> > > > >> > > > > > >> > >> Sent: Thursday, March 12, 2015 11:23 AM
>> > > > >> > > > > > >> > >> To: dev
>> > > > >> > > > > > >> > >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0
>> > Release
>> > > > >> > > > > > >> > >>
>> > > > >> > > > > > >> > >> OK, so right now it's just docs? How soon can
>> we
>> > > get a
>> > > > >> VOTE
>> > > > >> > > > > thread
>> > > > >> > > > > > >> > started
>> > > > >> > > > > > >> > >> for 4.0.0?
>> > > > >> > > > > > >> > >>
>> > > > >> > > > > > >> > >> On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <
>> > > > >> > > > > > agrieve@chromium.org>
>> > > > >> > > > > > >> > >> wrote:
>> > > > >> > > > > > >> > >>
>> > > > >> > > > > > >> > >> > mobilespec is now working again... Took
>> longer
>> > > than
>> > > > I
>> > > > >> > would
>> > > > >> > > > > have
>> > > > >> > > > > > >> > >> > liked, but did you know that on Android
>> > FileReader
>> > > > >> > triggers
>> > > > >> > > > > > >> > >> > shouldInterceptRequest() with Blob URLs!?
>> > > > >> > > > > > >> > >> >
>> > > > >> > > > > > >> > >> > Separate thread is already happening re:
>> > > whitelists,
>> > > > >> so
>> > > > >> > > once
>> > > > >> > > > > > that's
>> > > > >> > > > > > >> > >> > figured out, it's just docs afaict.
>> > > > >> > > > > > >> > >> >
>> > > > >> > > > > > >> > >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian
>> Clelland <
>> > > > >> > > > > > >> iclelland@chromium.org
>> > > > >> > > > > > >> > >
>> > > > >> > > > > > >> > >> > wrote:
>> > > > >> > > > > > >> > >> >
>> > > > >> > > > > > >> > >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <
>> > > > >> > > > > purplecabbage@gmail.com
>> > > > >> > > > > > >
>> > > > >> > > > > > >> > wrote:
>> > > > >> > > > > > >> > >> > >
>> > > > >> > > > > > >> > >> > > > We should start a new whitelist plugin
>> > related
>> > > > >> > thread.
>> > > > >> > > > > > >> > >> > > >
>> > > > >> > > > > > >> > >> > > > Why is a plugin blocking a release?
>> Default
>> > > > (aka
>> > > > >> > > > > no-plugin)
>> > > > >> > > > > > >> > >> > > > behavior should be to allow all network
>> > > requests
>> > > > >> > > > shouldn't
>> > > > >> > > > > > it?
>> > > > >> > > > > > >> > >> > >
>> > > > >> > > > > > >> > >> > >
>> > > > >> > > > > > >> > >> > > Well, that just might be a blacklist then
>> :)
>> > > > >> > > > > > >> > >> > >
>> > > > >> > > > > > >> > >> > >
>> > > > >> > > > > > >> > >> > > > This thread is a
>> > > > >> > > > > > >> > >> > > > month long, and not the first discussion
>> of
>> > > > 4.0.0
>> > > > >> for
>> > > > >> > > > > > Android.
>> > > > >> > > > > > >> > >> > > >
>> > > > >> > > > > > >> > >> > >
>> > > > >> > > > > > >> > >> > > Seriously, though -- the whitelist
>> discussion
>> > is
>> > > > >> much
>> > > > >> > > > longer
>> > > > >> > > > > > than
>> > > > >> > > > > > >> > >> > > that,
>> > > > >> > > > > > >> > >> > and
>> > > > >> > > > > > >> > >> > > this isn't the first time that the default
>> > > > >> > > > no-network-access
>> > > > >> > > > > > >> policy
>> > > > >> > > > > > >> > >> > > has been brought up:
>> > > > >> > > > > > >> > >> > >
>> > > > >> > > > > > >> > >> > > (Here's the first question, from *July*:
>> > > > >> > > > > > >> > >> > >
>> http://markmail.org/message/t4vj4saisem2mcgw
>> > > > >> > > > > > >> > >> > > Here's where I mentioned what the
>> implemented
>> > > > policy
>> > > > >> > was:
>> > > > >> > > > > > >> > >> > >
>> http://markmail.org/message/s4necfnh4hnblpjm
>> > > > >> > > > > > >> > >> > > And in another discussion:
>> > > > >> > > > > > >> > >> > >
>> http://markmail.org/message/ap7syhqysizmsvrz)
>> > > > >> > > > > > >> > >> > >
>> > > > >> > > > > > >> > >> > > If we want to reconsider that decision,
>> then
>> > we
>> > > > >> should
>> > > > >> > > > > > certainly
>> > > > >> > > > > > >> do
>> > > > >> > > > > > >> > >> > > so before we cut a release. I think it
>> would
>> > be
>> > > a
>> > > > >> real
>> > > > >> > > > > problem
>> > > > >> > > > > > to
>> > > > >> > > > > > >> > >> > > change it afterwards, so let's get it
>> right.
>> > > > >> > > > > > >> > >> > >
>> > > > >> > > > > > >> > >> > > Also, it's not the plugin itself that's
>> > blocking
>> > > > the
>> > > > >> > > > release,
>> > > > >> > > > > > >> it's
>> > > > >> > > > > > >> > >> > > us making sure that we've implemented the
>> core
>> > > > hooks
>> > > > >> > > > > correctly
>> > > > >> > > > > > so
>> > > > >> > > > > > >> > >> > > that the plugin can actually do its job,
>> and
>> > > that
>> > > > >> > people
>> > > > >> > > > who
>> > > > >> > > > > > >> don't
>> > > > >> > > > > > >> > >> > > want that particular plugin can make a
>> better
>> > > one.
>> > > > >> > > > > > >> > >> > >
>> > > > >> > > > > > >> > >> > > (It is also an issue that a plugin,
>> required
>> > for
>> > > > >> > > > > > cordova-android
>> > > > >> > > > > > >> > >> > > 4.0.0, breaks apps which are also building
>> for
>> > > > >> > > cordova-ios
>> > > > >> > > > > > 3.8.0.
>> > > > >> > > > > > >> > >> > > I'll take a
>> > > > >> > > > > > >> > >> > look
>> > > > >> > > > > > >> > >> > > at that, and either remove the ios-native
>> > > portions
>> > > > >> of
>> > > > >> > the
>> > > > >> > > > > > >> whitelist
>> > > > >> > > > > > >> > >> > plugin,
>> > > > >> > > > > > >> > >> > > or neuter it so that it doesn't interfere
>> with
>> > > an
>> > > > >> ios
>> > > > >> > app
>> > > > >> > > > if
>> > > > >> > > > > > it's
>> > > > >> > > > > > >> > >> > > not on the unplug-whitelist branch of that
>> > > repo.)
>> > > > >> > > > > > >> > >> > >
>> > > > >> > > > > > >> > >> > > Ian
>> > > > >> > > > > > >> > >> > >
>> > > > >> > > > > > >> > >> > >
>> > > > >> > > > > > >> > >> > > > @purplecabbage
>> > > > >> > > > > > >> > >> > > > risingj.com
>> > > > >> > > > > > >> > >> > > >
>> > > > >> > > > > > >> > >> > > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <
>> > > > >> > > > shazron@gmail.com
>> > > > >> > > > > >
>> > > > >> > > > > > >> > wrote:
>> > > > >> > > > > > >> > >> > > >
>> > > > >> > > > > > >> > >> > > > > legacy-whitelist-plugin should be
>> fixed so
>> > > > that
>> > > > >> it
>> > > > >> > > > > compiles
>> > > > >> > > > > > >> on
>> > > > >> > > > > > >> > >> > > > > cordova-ios@3.8.0. It shouldn't be a
>> > > problem
>> > > > to
>> > > > >> > fix
>> > > > >> > > > this
>> > > > >> > > > > > at
>> > > > >> > > > > > >> > >> > > > > compile
>> > > > >> > > > > > >> > >> > or
>> > > > >> > > > > > >> > >> > > > > run-time (whichever is applicable here
>> > > related
>> > > > >> to
>> > > > >> > the
>> > > > >> > > > > > compile
>> > > > >> > > > > > >> > >> > > > > error)
>> > > > >> > > > > > >> > >> > > > >
>> > > > >> > > > > > >> > >> > > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl
>> > Pogue
>> > > > >> > > > > > >> > >> > > > > <dv...@gmail.com>
>> > > > >> > > > > > >> > >> > > > wrote:
>> > > > >> > > > > > >> > >> > > > > > On 2 March 2015 at 13:37, Joe Bowser
>> <
>> > > > >> > > > > bowserj@gmail.com>
>> > > > >> > > > > > >> > wrote:
>> > > > >> > > > > > >> > >> > > > > >> So, right now the whitelist changes
>> are
>> > > > >> what's
>> > > > >> > > > holding
>> > > > >> > > > > > up
>> > > > >> > > > > > >> the
>> > > > >> > > > > > >> > >> > 4.0.0
>> > > > >> > > > > > >> > >> > > > > release
>> > > > >> > > > > > >> > >> > > > > >> now? Is this really the only thing
>> > > that's
>> > > > >> > holding
>> > > > >> > > > up
>> > > > >> > > > > > this
>> > > > >> > > > > > >> > >> > release?
>> > > > >> > > > > > >> > >> > > > > >>
>> > > > >> > > > > > >> > >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM
>> Andrew
>> > > > >> Grieve <
>> > > > >> > > > > > >> > >> > > agrieve@chromium.org>
>> > > > >> > > > > > >> > >> > > > > wrote:
>> > > > >> > > > > > >> > >> > > > > >>
>> > > > >> > > > > > >> > >> > > > > >>> I think we'll also need to finish
>> with
>> > > the
>> > > > >> > > > whitelist
>> > > > >> > > > > > >> changes
>> > > > >> > > > > > >> > >> > > > > >>> &
>> > > > >> > > > > > >> > >> > have
>> > > > >> > > > > > >> > >> > > > > both
>> > > > >> > > > > > >> > >> > > > > >>> the legacy and new-way whitelist
>> > plugins
>> > > > >> > released
>> > > > >> > > > > > before
>> > > > >> > > > > > >> we
>> > > > >> > > > > > >> > >> > > > > >>> can
>> > > > >> > > > > > >> > >> > do
>> > > > >> > > > > > >> > >> > > a
>> > > > >> > > > > > >> > >> > > > > 4.0.0
>> > > > >> > > > > > >> > >> > > > > >>> release (otherwise you wouldn't be
>> > able
>> > > to
>> > > > >> > write
>> > > > >> > > an
>> > > > >> > > > > app
>> > > > >> > > > > > >> that
>> > > > >> > > > > > >> > >> > > > > >>> hits
>> > > > >> > > > > > >> > >> > > the
>> > > > >> > > > > > >> > >> > > > > >>> network)
>> > > > >> > > > > > >> > >> > > > > >>>
>> > > > >> > > > > > >> > >> > > > > >
>> > > > >> > > > > > >> > >> > > > > > Just FYI, the whitelist stuff is
>> proving
>> > > to
>> > > > >> be a
>> > > > >> > > bit
>> > > > >> > > > > of a
>> > > > >> > > > > > >> pain
>> > > > >> > > > > > >> > >> > point.
>> > > > >> > > > > > >> > >> > > > > > I'm using cordova-android@master,
>> and
>> > > need
>> > > > to
>> > > > >> > > > install
>> > > > >> > > > > > the
>> > > > >> > > > > > >> > >> > > > > > legacy-whitelist plugin in order to
>> make
>> > > > >> network
>> > > > >> > > > > > requests.
>> > > > >> > > > > > >> > >> > > > > > Once the plugin is installed,
>> everything
>> > > > >> seems to
>> > > > >> > > > work.
>> > > > >> > > > > > >> > >> > > > > >
>> > > > >> > > > > > >> > >> > > > > > The problem is that the
>> legacy-whitelist
>> > > > >> plugin
>> > > > >> > > > > generates
>> > > > >> > > > > > >> > >> > > > > > compile errors with cordova-ios@3.8.0
>> ,
>> > so
>> > > > >> now I
>> > > > >> > > > can't
>> > > > >> > > > > > just
>> > > > >> > > > > > >> > run
>> > > > >> > > > > > >> > >> > > > > > `cordova build`, I need to split the
>> > > > >> platforms up
>> > > > >> > > and
>> > > > >> > > > > > >> > >> > > > > > install/uninstall the plugin in
>> between.
>> > > If
>> > > > >> > someone
>> > > > >> > > > > > makes a
>> > > > >> > > > > > >> > >> > > > > > dev build for Android and forgets the
>> > > > plugin,
>> > > > >> it
>> > > > >> > > will
>> > > > >> > > > > > >> appear
>> > > > >> > > > > > >> > >> > > > > > to build successfully but not
>> actually
>> > > > >> function
>> > > > >> > > > > properly
>> > > > >> > > > > > >> due
>> > > > >> > > > > > >> > to
>> > > > >> > > > > > >> > >> the whitelist.
>> > > > >> > > > > > >> > >> > > > > >
>> > > > >> > > > > > >> > >> > > > > > I know, this is all pre-release, so
>> pain
>> > > is
>> > > > >> > > somewhat
>> > > > >> > > > > > >> expected
>> > > > >> > > > > > >> > >> > > > > > right now. I'm worried about the case
>> > > where
>> > > > >> > > > > > >> > >> > > > > > cordova-android@4.0.0 is released
>> and
>> > > > >> > > > > cordova-ios@3.8.0
>> > > > >> > > > > > is
>> > > > >> > > > > > >> > >> > > > > > still current, and how people
>> > > > >> > > > > > >> > >> > can
>> > > > >> > > > > > >> > >> > > > > > avoid whitelist breakage there.
>> > > > >> > > > > > >> > >> > > > > >
>> > > > >> > > > > > >> > >> > > > > >
>> > > > >> > > > > > >> ------------------------------
>> > > > ------------------------------
>> > > > >> > > > > > >> > >> > ---------
>> > > > >> > > > > > >> > >> > > > > > To unsubscribe, e-mail:
>> > > > >> > > > > > dev-unsubscribe@cordova.apache.org
>> > > > >> > > > > > >> > >> > > > > > For additional commands, e-mail:
>> > > > >> > > > > > >> dev-help@cordova.apache.org
>> > > > >> > > > > > >> > >> > > > > >
>> > > > >> > > > > > >> > >> > > > >
>> > > > >> > > > > > >> > >> > > > >
>> > > > >> > > > > >
>> > ------------------------------------------------------------
>> > > > >> > > > > > >> > >> > ---------
>> > > > >> > > > > > >> > >> > > > > To unsubscribe, e-mail:
>> > > > >> > > > > dev-unsubscribe@cordova.apache.org
>> > > > >> > > > > > >> > >> > > > > For additional commands, e-mail:
>> > > > >> > > > > > dev-help@cordova.apache.org
>> > > > >> > > > > > >> > >> > > > >
>> > > > >> > > > > > >> > >> > > > >
>> > > > >> > > > > > >> > >> > > >
>> > > > >> > > > > > >> > >> > >
>> > > > >> > > > > > >> > >> >
>> > > > >> > > > > > >> > >>
>> > > > >> > > > > > >> >
>> > > > >> > > > > > >> >
>> > > > >> > > > >
>> > > > >>
>> > ---------------------------------------------------------------------
>> > > > >> > > > > > >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.
>> > > > apache.org
>> > > > >> > > > > > >> > For additional commands, e-mail:
>> > > > >> dev-help@cordova.apache.org
>> > > > >> > > > > > >> >
>> > > > >> > > > > > >> >
>> > > > >> > > > > > >>
>> > > > >> > > > > > >
>> > > > >> > > > > > >
>> > > > >> > > > > >
>> > > > >> > > > >
>> > > > >> > > > >
>> > > > >> > > > >
>> > > > >> > > > > --
>> > > > >> > > > > Carlos Santana
>> > > > >> > > > > <cs...@gmail.com>
>> > > > >> > > > >
>> > > > >> > > >
>> > > > >> > >
>> > > > >> >
>> > > > >>
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Andrew Grieve <ag...@chromium.org>.
The plugins being on npm will likely be a bump. Perhaps we should mention
that it requires the latest CLI (not yet release one), and defer the blog
post until CLI is released?
On Thu, Apr 9, 2015 at 2:20 PM, Ian Clelland <ic...@chromium.org> wrote:
> Moving from [VOTE] thread:
>
> On Thu, Apr 9, 2015 at 1:44 PM, Serge Huijben <s....@gmail.com> wrote:
>
> > But why is the meta csp tag required?
>
>
> It's not required, only recommended. It's more secure, as it can restrict
> more network access than the whitelist itself is capable of. (streaming
> <audio> and <video> tags, for instance).
>
> On Thu, Apr 9, 2015 at 1:44 PM, Treggiari, Leo <le...@intel.com>
> wrote:
>
> > Another question, based upon my understanding, which must be wrong!
> >
> > The 4.0.0 Android Release will require the cordova-plugin-whitelist in
> > order
> > to get a whitelist implemented correctly.
> >
> > Given its name (dash-style) it is only available as an node component.
> >
> > The is no released CLI that knows how to fetch from npm?
> > Or does 4.3, even though I don't see it in the release notes?
> > Even so, there are many previous CLI releases which will not work?
> >
>
> This is at least partly resolved by the fact that no released CLI points to
> cordova-android 4.0.0. Once 4.0.0 is released. we will be able to release a
> version of the CLI which downloads it by default.
>
> The whitelist plugins are published already, and discussion is underway
> about voting/releasing cordova-lib (and accompanying tools), so I think
> there are only two possible timelines:
>
> A) whitelist plugins released, then cordova-android 4 released, then tools
> released (supports NPM plugins and Android 4).
>
> B) plugins released, then tools released (supports NPM plugins), then
> cordova-android 4 released, then a small bump of tools is released (to pin
> to cordova-android 4)
>
> In either case, users of the released CLI always have a version which
> works.
>
>
> > It would be good for the release notes to explain the situation.
> >
> > Leo
> >
>
>
> On Thu, Apr 9, 2015 at 1:24 PM, Michal Mocny <mm...@chromium.org> wrote:
>
> > Splashscreens was mentioned, icons was not. I don't think there is an
> > icons change?
> >
> > On Thu, Apr 9, 2015 at 1:17 PM, Joe Bowser <bo...@gmail.com> wrote:
> >
> > > So, wasn't there a change regarding icons and spashscreens being
> moved? I
> > > have no idea if we want to add that, or if adding that should happen
> > after
> > > the release?
> > >
> > > On Wed, Apr 8, 2015 at 7:09 PM Andrew Grieve <ag...@chromium.org>
> > wrote:
> > >
> > > > CB-8684 is now merged and I've updated the targetSdk (and made a
> couple
> > > > other changes).
> > > >
> > > > I'll start the release process in the morning as long as there no
> > > > objections.
> > > >
> > > >
> > > > On Tue, Apr 7, 2015 at 2:20 PM, Andrew Grieve <ag...@chromium.org>
> > > > wrote:
> > > >
> > > > > I'll start on it once CB-8684 lands (Tony - assuming you'll have
> this
> > > > done
> > > > > shortly and would prefer it lands?)
> > > > >
> > > > > On Tue, Apr 7, 2015 at 1:33 PM, Jesse <pu...@gmail.com>
> > wrote:
> > > > >
> > > > >> Sweet!
> > > > >>
> > > > >> @purplecabbage
> > > > >> risingj.com
> > > > >>
> > > > >> On Tue, Apr 7, 2015 at 8:35 AM, Andrew Grieve <
> agrieve@chromium.org
> > >
> > > > >> wrote:
> > > > >>
> > > > >> > Let's do it!
> > > > >> >
> > > > >> > On Mon, Apr 6, 2015 at 7:33 PM, Joe Bowser <bo...@gmail.com>
> > > wrote:
> > > > >> >
> > > > >> > > So, I think we should put off the embedder's guide until after
> > the
> > > > >> > > release. A lot of it has changed, and since we're still
> > > technically
> > > > >> > > obligated to support the 3.x release tree for six months, that
> > > > should
> > > > >> buy
> > > > >> > > us some time to figure out how that is going to work. Getting
> > > > >> Cordova to
> > > > >> > > work with a vanilla Android Studio project is a non-trivial
> > task.
> > > > >> > >
> > > > >> > > Given that everything else appears to be done, should we start
> > > > voting
> > > > >> on
> > > > >> > an
> > > > >> > > RC for this? What do people think?
> > > > >> > >
> > > > >> > >
> > > > >> > >
> > > > >> > > On Thu, Mar 19, 2015 at 10:31 AM Andrew Grieve <
> > > > agrieve@chromium.org>
> > > > >> > > wrote:
> > > > >> > >
> > > > >> > > > Here's issues:
> > > > >> > > > https://issues.apache.org/jira/browse/CB-8715 (docs)
> > > > >> > > > https://issues.apache.org/jira/browse/CB-8716 (whitelist)
> > > > >> > > > https://issues.apache.org/jira/browse/CB-8717 (write
> > > > >> RELEASENOTES.md)
> > > > >> > > >
> > > > >> > > > On Tue, Mar 17, 2015 at 10:15 AM, Carlos Santana <
> > > > >> csantana23@gmail.com
> > > > >> > >
> > > > >> > > > wrote:
> > > > >> > > >
> > > > >> > > > > I would say let's start RC testing and voting, But not pin
> > the
> > > > >> > version
> > > > >> > > in
> > > > >> > > > > Cordova CLI until the tasks that Andrew mentioned are
> done.
> > > > >> > > > > Andrew can you create the JIRA Items for the tasks that
> need
> > > to
> > > > be
> > > > >> > > done.
> > > > >> > > > I
> > > > >> > > > > thought there was a discussion about creating JIRA Items
> to
> > > help
> > > > >> > track
> > > > >> > > > and
> > > > >> > > > > know what's left for release something.
> > > > >> > > > >
> > > > >> > > > > - upgrade guide,
> > > > >> > > > > - publishing whitelist plugins,
> > > > >> > > > > - and making it so that the default project template
> > includes
> > > > >> <plugin
> > > > >> > > > > name="cordova-plugin-whitelist" />)
> > > > >> > > > >
> > > > >> > > > >
> > > > >> > > > > On Mon, Mar 16, 2015 at 11:21 PM, Ian Clelland <
> > > > >> > iclelland@chromium.org
> > > > >> > > >
> > > > >> > > > > wrote:
> > > > >> > > > >
> > > > >> > > > > > We'll probably need at least an RC for the whitelist
> > plugin,
> > > > if
> > > > >> > not a
> > > > >> > > > > vote,
> > > > >> > > > > > to be able to vote on this.
> > > > >> > > > > >
> > > > >> > > > > > Or can we just include instructions like "Use
> > > > >> > > > > > cordova-plugin-whitelist@f70b1bc for testing" while we
> > > start
> > > > >> the
> > > > >> > > > > official
> > > > >> > > > > > release process for the plugins?
> > > > >> > > > > >
> > > > >> > > > > > On Mon, Mar 16, 2015 at 11:17 PM, Ian Clelland <
> > > > >> > > iclelland@chromium.org
> > > > >> > > > >
> > > > >> > > > > > wrote:
> > > > >> > > > > >
> > > > >> > > > > > > +1 -- Let's get this out the door :)
> > > > >> > > > > > > I'll see what I can get done to move it in that
> > direction.
> > > > >> > > > > > >
> > > > >> > > > > > > On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <
> > > > >> > > agrieve@chromium.org
> > > > >> > > > >
> > > > >> > > > > > > wrote:
> > > > >> > > > > > >
> > > > >> > > > > > >> Everything's ready afaik (minus upgrade guide,
> > publishing
> > > > >> > > whitelist
> > > > >> > > > > > >> plugins, and making it so that the default project
> > > template
> > > > >> > > includes
> > > > >> > > > > > >> <plugin name="cordova-plugin-whitelist" />). Maybe
> > let's
> > > > do
> > > > >> a RC
> > > > >> > > > while
> > > > >> > > > > > we
> > > > >> > > > > > >> wait on these things being finished up?
> > > > >> > > > > > >>
> > > > >> > > > > > >> If anyone wants to take on any of these tasks, that
> > would
> > > > be
> > > > >> > > > awesome.
> > > > >> > > > > > >>
> > > > >> > > > > > >> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <
> > > > shazron@gmail.com>
> > > > >> > > wrote:
> > > > >> > > > > > >>
> > > > >> > > > > > >> > +1 for vote thread, let's get this thing out so
> > people
> > > > >> (that
> > > > >> > are
> > > > >> > > > not
> > > > >> > > > > > >> > us) can test...
> > > > >> > > > > > >> >
> > > > >> > > > > > >> >
> > > > >> > > > > > >> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <
> > > > >> > bowserj@gmail.com>
> > > > >> > > > > > wrote:
> > > > >> > > > > > >> > > OK, this is a three month old thread, and we're
> > > waiting
> > > > >> on a
> > > > >> > > > > > >> discussion
> > > > >> > > > > > >> > > before we release something? I really think we
> > should
> > > > go
> > > > >> to
> > > > >> > a
> > > > >> > > > vote
> > > > >> > > > > > >> thread
> > > > >> > > > > > >> > > now that we have a legacy whitelist plugin and a
> > new
> > > > >> style
> > > > >> > > > > whitelist
> > > > >> > > > > > >> > > plugin. We shouldn't keep constantly delaying
> this
> > > > >> release
> > > > >> > > > > because
> > > > >> > > > > > of
> > > > >> > > > > > >> > > what's happening on other platforms, especially
> > since
> > > > we
> > > > >> > > already
> > > > >> > > > > > >> > pluginized
> > > > >> > > > > > >> > > the whitelist.
> > > > >> > > > > > >> > >
> > > > >> > > > > > >> > > Can we please release soon?
> > > > >> > > > > > >> > >
> > > > >> > > > > > >> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil
> Khandelwal <
> > > > >> > > > > > >> > nikhilkh@microsoft.com>
> > > > >> > > > > > >> > > wrote:
> > > > >> > > > > > >> > >
> > > > >> > > > > > >> > >> I know we discussed a couple of approaches
> > > > implementing
> > > > >> the
> > > > >> > > > > default
> > > > >> > > > > > >> > >> whitelist policy for Android/iOS - either every
> > app
> > > > >> would
> > > > >> > be
> > > > >> > > > > > >> required to
> > > > >> > > > > > >> > >> include the whitelist plugin or have it have
> smart
> > > > >> defaults
> > > > >> > > in
> > > > >> > > > > the
> > > > >> > > > > > >> > platform
> > > > >> > > > > > >> > >> implementation and the plugin being able to
> > override
> > > > >> them.
> > > > >> > > > > > >> > >>
> > > > >> > > > > > >> > >> I don’t think that thread closed with any
> > > conclusions.
> > > > >> > > > > > >> > >>
> > > > >> > > > > > >> > >> Thanks,
> > > > >> > > > > > >> > >> Nikhil
> > > > >> > > > > > >> > >>
> > > > >> > > > > > >> > >>
> > > > >> > > > > > >> > >> -----Original Message-----
> > > > >> > > > > > >> > >> From: Joe Bowser [mailto:bowserj@gmail.com]
> > > > >> > > > > > >> > >> Sent: Thursday, March 12, 2015 11:23 AM
> > > > >> > > > > > >> > >> To: dev
> > > > >> > > > > > >> > >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0
> > Release
> > > > >> > > > > > >> > >>
> > > > >> > > > > > >> > >> OK, so right now it's just docs? How soon can we
> > > get a
> > > > >> VOTE
> > > > >> > > > > thread
> > > > >> > > > > > >> > started
> > > > >> > > > > > >> > >> for 4.0.0?
> > > > >> > > > > > >> > >>
> > > > >> > > > > > >> > >> On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <
> > > > >> > > > > > agrieve@chromium.org>
> > > > >> > > > > > >> > >> wrote:
> > > > >> > > > > > >> > >>
> > > > >> > > > > > >> > >> > mobilespec is now working again... Took longer
> > > than
> > > > I
> > > > >> > would
> > > > >> > > > > have
> > > > >> > > > > > >> > >> > liked, but did you know that on Android
> > FileReader
> > > > >> > triggers
> > > > >> > > > > > >> > >> > shouldInterceptRequest() with Blob URLs!?
> > > > >> > > > > > >> > >> >
> > > > >> > > > > > >> > >> > Separate thread is already happening re:
> > > whitelists,
> > > > >> so
> > > > >> > > once
> > > > >> > > > > > that's
> > > > >> > > > > > >> > >> > figured out, it's just docs afaict.
> > > > >> > > > > > >> > >> >
> > > > >> > > > > > >> > >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian Clelland
> <
> > > > >> > > > > > >> iclelland@chromium.org
> > > > >> > > > > > >> > >
> > > > >> > > > > > >> > >> > wrote:
> > > > >> > > > > > >> > >> >
> > > > >> > > > > > >> > >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <
> > > > >> > > > > purplecabbage@gmail.com
> > > > >> > > > > > >
> > > > >> > > > > > >> > wrote:
> > > > >> > > > > > >> > >> > >
> > > > >> > > > > > >> > >> > > > We should start a new whitelist plugin
> > related
> > > > >> > thread.
> > > > >> > > > > > >> > >> > > >
> > > > >> > > > > > >> > >> > > > Why is a plugin blocking a release?
> Default
> > > > (aka
> > > > >> > > > > no-plugin)
> > > > >> > > > > > >> > >> > > > behavior should be to allow all network
> > > requests
> > > > >> > > > shouldn't
> > > > >> > > > > > it?
> > > > >> > > > > > >> > >> > >
> > > > >> > > > > > >> > >> > >
> > > > >> > > > > > >> > >> > > Well, that just might be a blacklist then :)
> > > > >> > > > > > >> > >> > >
> > > > >> > > > > > >> > >> > >
> > > > >> > > > > > >> > >> > > > This thread is a
> > > > >> > > > > > >> > >> > > > month long, and not the first discussion
> of
> > > > 4.0.0
> > > > >> for
> > > > >> > > > > > Android.
> > > > >> > > > > > >> > >> > > >
> > > > >> > > > > > >> > >> > >
> > > > >> > > > > > >> > >> > > Seriously, though -- the whitelist
> discussion
> > is
> > > > >> much
> > > > >> > > > longer
> > > > >> > > > > > than
> > > > >> > > > > > >> > >> > > that,
> > > > >> > > > > > >> > >> > and
> > > > >> > > > > > >> > >> > > this isn't the first time that the default
> > > > >> > > > no-network-access
> > > > >> > > > > > >> policy
> > > > >> > > > > > >> > >> > > has been brought up:
> > > > >> > > > > > >> > >> > >
> > > > >> > > > > > >> > >> > > (Here's the first question, from *July*:
> > > > >> > > > > > >> > >> > >
> http://markmail.org/message/t4vj4saisem2mcgw
> > > > >> > > > > > >> > >> > > Here's where I mentioned what the
> implemented
> > > > policy
> > > > >> > was:
> > > > >> > > > > > >> > >> > >
> http://markmail.org/message/s4necfnh4hnblpjm
> > > > >> > > > > > >> > >> > > And in another discussion:
> > > > >> > > > > > >> > >> > >
> http://markmail.org/message/ap7syhqysizmsvrz)
> > > > >> > > > > > >> > >> > >
> > > > >> > > > > > >> > >> > > If we want to reconsider that decision, then
> > we
> > > > >> should
> > > > >> > > > > > certainly
> > > > >> > > > > > >> do
> > > > >> > > > > > >> > >> > > so before we cut a release. I think it would
> > be
> > > a
> > > > >> real
> > > > >> > > > > problem
> > > > >> > > > > > to
> > > > >> > > > > > >> > >> > > change it afterwards, so let's get it right.
> > > > >> > > > > > >> > >> > >
> > > > >> > > > > > >> > >> > > Also, it's not the plugin itself that's
> > blocking
> > > > the
> > > > >> > > > release,
> > > > >> > > > > > >> it's
> > > > >> > > > > > >> > >> > > us making sure that we've implemented the
> core
> > > > hooks
> > > > >> > > > > correctly
> > > > >> > > > > > so
> > > > >> > > > > > >> > >> > > that the plugin can actually do its job, and
> > > that
> > > > >> > people
> > > > >> > > > who
> > > > >> > > > > > >> don't
> > > > >> > > > > > >> > >> > > want that particular plugin can make a
> better
> > > one.
> > > > >> > > > > > >> > >> > >
> > > > >> > > > > > >> > >> > > (It is also an issue that a plugin, required
> > for
> > > > >> > > > > > cordova-android
> > > > >> > > > > > >> > >> > > 4.0.0, breaks apps which are also building
> for
> > > > >> > > cordova-ios
> > > > >> > > > > > 3.8.0.
> > > > >> > > > > > >> > >> > > I'll take a
> > > > >> > > > > > >> > >> > look
> > > > >> > > > > > >> > >> > > at that, and either remove the ios-native
> > > portions
> > > > >> of
> > > > >> > the
> > > > >> > > > > > >> whitelist
> > > > >> > > > > > >> > >> > plugin,
> > > > >> > > > > > >> > >> > > or neuter it so that it doesn't interfere
> with
> > > an
> > > > >> ios
> > > > >> > app
> > > > >> > > > if
> > > > >> > > > > > it's
> > > > >> > > > > > >> > >> > > not on the unplug-whitelist branch of that
> > > repo.)
> > > > >> > > > > > >> > >> > >
> > > > >> > > > > > >> > >> > > Ian
> > > > >> > > > > > >> > >> > >
> > > > >> > > > > > >> > >> > >
> > > > >> > > > > > >> > >> > > > @purplecabbage
> > > > >> > > > > > >> > >> > > > risingj.com
> > > > >> > > > > > >> > >> > > >
> > > > >> > > > > > >> > >> > > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <
> > > > >> > > > shazron@gmail.com
> > > > >> > > > > >
> > > > >> > > > > > >> > wrote:
> > > > >> > > > > > >> > >> > > >
> > > > >> > > > > > >> > >> > > > > legacy-whitelist-plugin should be fixed
> so
> > > > that
> > > > >> it
> > > > >> > > > > compiles
> > > > >> > > > > > >> on
> > > > >> > > > > > >> > >> > > > > cordova-ios@3.8.0. It shouldn't be a
> > > problem
> > > > to
> > > > >> > fix
> > > > >> > > > this
> > > > >> > > > > > at
> > > > >> > > > > > >> > >> > > > > compile
> > > > >> > > > > > >> > >> > or
> > > > >> > > > > > >> > >> > > > > run-time (whichever is applicable here
> > > related
> > > > >> to
> > > > >> > the
> > > > >> > > > > > compile
> > > > >> > > > > > >> > >> > > > > error)
> > > > >> > > > > > >> > >> > > > >
> > > > >> > > > > > >> > >> > > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl
> > Pogue
> > > > >> > > > > > >> > >> > > > > <dv...@gmail.com>
> > > > >> > > > > > >> > >> > > > wrote:
> > > > >> > > > > > >> > >> > > > > > On 2 March 2015 at 13:37, Joe Bowser <
> > > > >> > > > > bowserj@gmail.com>
> > > > >> > > > > > >> > wrote:
> > > > >> > > > > > >> > >> > > > > >> So, right now the whitelist changes
> are
> > > > >> what's
> > > > >> > > > holding
> > > > >> > > > > > up
> > > > >> > > > > > >> the
> > > > >> > > > > > >> > >> > 4.0.0
> > > > >> > > > > > >> > >> > > > > release
> > > > >> > > > > > >> > >> > > > > >> now? Is this really the only thing
> > > that's
> > > > >> > holding
> > > > >> > > > up
> > > > >> > > > > > this
> > > > >> > > > > > >> > >> > release?
> > > > >> > > > > > >> > >> > > > > >>
> > > > >> > > > > > >> > >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM
> Andrew
> > > > >> Grieve <
> > > > >> > > > > > >> > >> > > agrieve@chromium.org>
> > > > >> > > > > > >> > >> > > > > wrote:
> > > > >> > > > > > >> > >> > > > > >>
> > > > >> > > > > > >> > >> > > > > >>> I think we'll also need to finish
> with
> > > the
> > > > >> > > > whitelist
> > > > >> > > > > > >> changes
> > > > >> > > > > > >> > >> > > > > >>> &
> > > > >> > > > > > >> > >> > have
> > > > >> > > > > > >> > >> > > > > both
> > > > >> > > > > > >> > >> > > > > >>> the legacy and new-way whitelist
> > plugins
> > > > >> > released
> > > > >> > > > > > before
> > > > >> > > > > > >> we
> > > > >> > > > > > >> > >> > > > > >>> can
> > > > >> > > > > > >> > >> > do
> > > > >> > > > > > >> > >> > > a
> > > > >> > > > > > >> > >> > > > > 4.0.0
> > > > >> > > > > > >> > >> > > > > >>> release (otherwise you wouldn't be
> > able
> > > to
> > > > >> > write
> > > > >> > > an
> > > > >> > > > > app
> > > > >> > > > > > >> that
> > > > >> > > > > > >> > >> > > > > >>> hits
> > > > >> > > > > > >> > >> > > the
> > > > >> > > > > > >> > >> > > > > >>> network)
> > > > >> > > > > > >> > >> > > > > >>>
> > > > >> > > > > > >> > >> > > > > >
> > > > >> > > > > > >> > >> > > > > > Just FYI, the whitelist stuff is
> proving
> > > to
> > > > >> be a
> > > > >> > > bit
> > > > >> > > > > of a
> > > > >> > > > > > >> pain
> > > > >> > > > > > >> > >> > point.
> > > > >> > > > > > >> > >> > > > > > I'm using cordova-android@master, and
> > > need
> > > > to
> > > > >> > > > install
> > > > >> > > > > > the
> > > > >> > > > > > >> > >> > > > > > legacy-whitelist plugin in order to
> make
> > > > >> network
> > > > >> > > > > > requests.
> > > > >> > > > > > >> > >> > > > > > Once the plugin is installed,
> everything
> > > > >> seems to
> > > > >> > > > work.
> > > > >> > > > > > >> > >> > > > > >
> > > > >> > > > > > >> > >> > > > > > The problem is that the
> legacy-whitelist
> > > > >> plugin
> > > > >> > > > > generates
> > > > >> > > > > > >> > >> > > > > > compile errors with cordova-ios@3.8.0
> ,
> > so
> > > > >> now I
> > > > >> > > > can't
> > > > >> > > > > > just
> > > > >> > > > > > >> > run
> > > > >> > > > > > >> > >> > > > > > `cordova build`, I need to split the
> > > > >> platforms up
> > > > >> > > and
> > > > >> > > > > > >> > >> > > > > > install/uninstall the plugin in
> between.
> > > If
> > > > >> > someone
> > > > >> > > > > > makes a
> > > > >> > > > > > >> > >> > > > > > dev build for Android and forgets the
> > > > plugin,
> > > > >> it
> > > > >> > > will
> > > > >> > > > > > >> appear
> > > > >> > > > > > >> > >> > > > > > to build successfully but not actually
> > > > >> function
> > > > >> > > > > properly
> > > > >> > > > > > >> due
> > > > >> > > > > > >> > to
> > > > >> > > > > > >> > >> the whitelist.
> > > > >> > > > > > >> > >> > > > > >
> > > > >> > > > > > >> > >> > > > > > I know, this is all pre-release, so
> pain
> > > is
> > > > >> > > somewhat
> > > > >> > > > > > >> expected
> > > > >> > > > > > >> > >> > > > > > right now. I'm worried about the case
> > > where
> > > > >> > > > > > >> > >> > > > > > cordova-android@4.0.0 is released and
> > > > >> > > > > cordova-ios@3.8.0
> > > > >> > > > > > is
> > > > >> > > > > > >> > >> > > > > > still current, and how people
> > > > >> > > > > > >> > >> > can
> > > > >> > > > > > >> > >> > > > > > avoid whitelist breakage there.
> > > > >> > > > > > >> > >> > > > > >
> > > > >> > > > > > >> > >> > > > > >
> > > > >> > > > > > >> ------------------------------
> > > > ------------------------------
> > > > >> > > > > > >> > >> > ---------
> > > > >> > > > > > >> > >> > > > > > To unsubscribe, e-mail:
> > > > >> > > > > > dev-unsubscribe@cordova.apache.org
> > > > >> > > > > > >> > >> > > > > > For additional commands, e-mail:
> > > > >> > > > > > >> dev-help@cordova.apache.org
> > > > >> > > > > > >> > >> > > > > >
> > > > >> > > > > > >> > >> > > > >
> > > > >> > > > > > >> > >> > > > >
> > > > >> > > > > >
> > ------------------------------------------------------------
> > > > >> > > > > > >> > >> > ---------
> > > > >> > > > > > >> > >> > > > > To unsubscribe, e-mail:
> > > > >> > > > > dev-unsubscribe@cordova.apache.org
> > > > >> > > > > > >> > >> > > > > For additional commands, e-mail:
> > > > >> > > > > > dev-help@cordova.apache.org
> > > > >> > > > > > >> > >> > > > >
> > > > >> > > > > > >> > >> > > > >
> > > > >> > > > > > >> > >> > > >
> > > > >> > > > > > >> > >> > >
> > > > >> > > > > > >> > >> >
> > > > >> > > > > > >> > >>
> > > > >> > > > > > >> >
> > > > >> > > > > > >> >
> > > > >> > > > >
> > > > >>
> > ---------------------------------------------------------------------
> > > > >> > > > > > >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.
> > > > apache.org
> > > > >> > > > > > >> > For additional commands, e-mail:
> > > > >> dev-help@cordova.apache.org
> > > > >> > > > > > >> >
> > > > >> > > > > > >> >
> > > > >> > > > > > >>
> > > > >> > > > > > >
> > > > >> > > > > > >
> > > > >> > > > > >
> > > > >> > > > >
> > > > >> > > > >
> > > > >> > > > >
> > > > >> > > > > --
> > > > >> > > > > Carlos Santana
> > > > >> > > > > <cs...@gmail.com>
> > > > >> > > > >
> > > > >> > > >
> > > > >> > >
> > > > >> >
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Ian Clelland <ic...@chromium.org>.
Moving from [VOTE] thread:
On Thu, Apr 9, 2015 at 1:44 PM, Serge Huijben <s....@gmail.com> wrote:
> But why is the meta csp tag required?
It's not required, only recommended. It's more secure, as it can restrict
more network access than the whitelist itself is capable of. (streaming
<audio> and <video> tags, for instance).
On Thu, Apr 9, 2015 at 1:44 PM, Treggiari, Leo <le...@intel.com>
wrote:
> Another question, based upon my understanding, which must be wrong!
>
> The 4.0.0 Android Release will require the cordova-plugin-whitelist in
> order
> to get a whitelist implemented correctly.
>
> Given its name (dash-style) it is only available as an node component.
>
> The is no released CLI that knows how to fetch from npm?
> Or does 4.3, even though I don't see it in the release notes?
> Even so, there are many previous CLI releases which will not work?
>
This is at least partly resolved by the fact that no released CLI points to
cordova-android 4.0.0. Once 4.0.0 is released. we will be able to release a
version of the CLI which downloads it by default.
The whitelist plugins are published already, and discussion is underway
about voting/releasing cordova-lib (and accompanying tools), so I think
there are only two possible timelines:
A) whitelist plugins released, then cordova-android 4 released, then tools
released (supports NPM plugins and Android 4).
B) plugins released, then tools released (supports NPM plugins), then
cordova-android 4 released, then a small bump of tools is released (to pin
to cordova-android 4)
In either case, users of the released CLI always have a version which works.
> It would be good for the release notes to explain the situation.
>
> Leo
>
On Thu, Apr 9, 2015 at 1:24 PM, Michal Mocny <mm...@chromium.org> wrote:
> Splashscreens was mentioned, icons was not. I don't think there is an
> icons change?
>
> On Thu, Apr 9, 2015 at 1:17 PM, Joe Bowser <bo...@gmail.com> wrote:
>
> > So, wasn't there a change regarding icons and spashscreens being moved? I
> > have no idea if we want to add that, or if adding that should happen
> after
> > the release?
> >
> > On Wed, Apr 8, 2015 at 7:09 PM Andrew Grieve <ag...@chromium.org>
> wrote:
> >
> > > CB-8684 is now merged and I've updated the targetSdk (and made a couple
> > > other changes).
> > >
> > > I'll start the release process in the morning as long as there no
> > > objections.
> > >
> > >
> > > On Tue, Apr 7, 2015 at 2:20 PM, Andrew Grieve <ag...@chromium.org>
> > > wrote:
> > >
> > > > I'll start on it once CB-8684 lands (Tony - assuming you'll have this
> > > done
> > > > shortly and would prefer it lands?)
> > > >
> > > > On Tue, Apr 7, 2015 at 1:33 PM, Jesse <pu...@gmail.com>
> wrote:
> > > >
> > > >> Sweet!
> > > >>
> > > >> @purplecabbage
> > > >> risingj.com
> > > >>
> > > >> On Tue, Apr 7, 2015 at 8:35 AM, Andrew Grieve <agrieve@chromium.org
> >
> > > >> wrote:
> > > >>
> > > >> > Let's do it!
> > > >> >
> > > >> > On Mon, Apr 6, 2015 at 7:33 PM, Joe Bowser <bo...@gmail.com>
> > wrote:
> > > >> >
> > > >> > > So, I think we should put off the embedder's guide until after
> the
> > > >> > > release. A lot of it has changed, and since we're still
> > technically
> > > >> > > obligated to support the 3.x release tree for six months, that
> > > should
> > > >> buy
> > > >> > > us some time to figure out how that is going to work. Getting
> > > >> Cordova to
> > > >> > > work with a vanilla Android Studio project is a non-trivial
> task.
> > > >> > >
> > > >> > > Given that everything else appears to be done, should we start
> > > voting
> > > >> on
> > > >> > an
> > > >> > > RC for this? What do people think?
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > On Thu, Mar 19, 2015 at 10:31 AM Andrew Grieve <
> > > agrieve@chromium.org>
> > > >> > > wrote:
> > > >> > >
> > > >> > > > Here's issues:
> > > >> > > > https://issues.apache.org/jira/browse/CB-8715 (docs)
> > > >> > > > https://issues.apache.org/jira/browse/CB-8716 (whitelist)
> > > >> > > > https://issues.apache.org/jira/browse/CB-8717 (write
> > > >> RELEASENOTES.md)
> > > >> > > >
> > > >> > > > On Tue, Mar 17, 2015 at 10:15 AM, Carlos Santana <
> > > >> csantana23@gmail.com
> > > >> > >
> > > >> > > > wrote:
> > > >> > > >
> > > >> > > > > I would say let's start RC testing and voting, But not pin
> the
> > > >> > version
> > > >> > > in
> > > >> > > > > Cordova CLI until the tasks that Andrew mentioned are done.
> > > >> > > > > Andrew can you create the JIRA Items for the tasks that need
> > to
> > > be
> > > >> > > done.
> > > >> > > > I
> > > >> > > > > thought there was a discussion about creating JIRA Items to
> > help
> > > >> > track
> > > >> > > > and
> > > >> > > > > know what's left for release something.
> > > >> > > > >
> > > >> > > > > - upgrade guide,
> > > >> > > > > - publishing whitelist plugins,
> > > >> > > > > - and making it so that the default project template
> includes
> > > >> <plugin
> > > >> > > > > name="cordova-plugin-whitelist" />)
> > > >> > > > >
> > > >> > > > >
> > > >> > > > > On Mon, Mar 16, 2015 at 11:21 PM, Ian Clelland <
> > > >> > iclelland@chromium.org
> > > >> > > >
> > > >> > > > > wrote:
> > > >> > > > >
> > > >> > > > > > We'll probably need at least an RC for the whitelist
> plugin,
> > > if
> > > >> > not a
> > > >> > > > > vote,
> > > >> > > > > > to be able to vote on this.
> > > >> > > > > >
> > > >> > > > > > Or can we just include instructions like "Use
> > > >> > > > > > cordova-plugin-whitelist@f70b1bc for testing" while we
> > start
> > > >> the
> > > >> > > > > official
> > > >> > > > > > release process for the plugins?
> > > >> > > > > >
> > > >> > > > > > On Mon, Mar 16, 2015 at 11:17 PM, Ian Clelland <
> > > >> > > iclelland@chromium.org
> > > >> > > > >
> > > >> > > > > > wrote:
> > > >> > > > > >
> > > >> > > > > > > +1 -- Let's get this out the door :)
> > > >> > > > > > > I'll see what I can get done to move it in that
> direction.
> > > >> > > > > > >
> > > >> > > > > > > On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <
> > > >> > > agrieve@chromium.org
> > > >> > > > >
> > > >> > > > > > > wrote:
> > > >> > > > > > >
> > > >> > > > > > >> Everything's ready afaik (minus upgrade guide,
> publishing
> > > >> > > whitelist
> > > >> > > > > > >> plugins, and making it so that the default project
> > template
> > > >> > > includes
> > > >> > > > > > >> <plugin name="cordova-plugin-whitelist" />). Maybe
> let's
> > > do
> > > >> a RC
> > > >> > > > while
> > > >> > > > > > we
> > > >> > > > > > >> wait on these things being finished up?
> > > >> > > > > > >>
> > > >> > > > > > >> If anyone wants to take on any of these tasks, that
> would
> > > be
> > > >> > > > awesome.
> > > >> > > > > > >>
> > > >> > > > > > >> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <
> > > shazron@gmail.com>
> > > >> > > wrote:
> > > >> > > > > > >>
> > > >> > > > > > >> > +1 for vote thread, let's get this thing out so
> people
> > > >> (that
> > > >> > are
> > > >> > > > not
> > > >> > > > > > >> > us) can test...
> > > >> > > > > > >> >
> > > >> > > > > > >> >
> > > >> > > > > > >> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <
> > > >> > bowserj@gmail.com>
> > > >> > > > > > wrote:
> > > >> > > > > > >> > > OK, this is a three month old thread, and we're
> > waiting
> > > >> on a
> > > >> > > > > > >> discussion
> > > >> > > > > > >> > > before we release something? I really think we
> should
> > > go
> > > >> to
> > > >> > a
> > > >> > > > vote
> > > >> > > > > > >> thread
> > > >> > > > > > >> > > now that we have a legacy whitelist plugin and a
> new
> > > >> style
> > > >> > > > > whitelist
> > > >> > > > > > >> > > plugin. We shouldn't keep constantly delaying this
> > > >> release
> > > >> > > > > because
> > > >> > > > > > of
> > > >> > > > > > >> > > what's happening on other platforms, especially
> since
> > > we
> > > >> > > already
> > > >> > > > > > >> > pluginized
> > > >> > > > > > >> > > the whitelist.
> > > >> > > > > > >> > >
> > > >> > > > > > >> > > Can we please release soon?
> > > >> > > > > > >> > >
> > > >> > > > > > >> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil Khandelwal <
> > > >> > > > > > >> > nikhilkh@microsoft.com>
> > > >> > > > > > >> > > wrote:
> > > >> > > > > > >> > >
> > > >> > > > > > >> > >> I know we discussed a couple of approaches
> > > implementing
> > > >> the
> > > >> > > > > default
> > > >> > > > > > >> > >> whitelist policy for Android/iOS - either every
> app
> > > >> would
> > > >> > be
> > > >> > > > > > >> required to
> > > >> > > > > > >> > >> include the whitelist plugin or have it have smart
> > > >> defaults
> > > >> > > in
> > > >> > > > > the
> > > >> > > > > > >> > platform
> > > >> > > > > > >> > >> implementation and the plugin being able to
> override
> > > >> them.
> > > >> > > > > > >> > >>
> > > >> > > > > > >> > >> I don’t think that thread closed with any
> > conclusions.
> > > >> > > > > > >> > >>
> > > >> > > > > > >> > >> Thanks,
> > > >> > > > > > >> > >> Nikhil
> > > >> > > > > > >> > >>
> > > >> > > > > > >> > >>
> > > >> > > > > > >> > >> -----Original Message-----
> > > >> > > > > > >> > >> From: Joe Bowser [mailto:bowserj@gmail.com]
> > > >> > > > > > >> > >> Sent: Thursday, March 12, 2015 11:23 AM
> > > >> > > > > > >> > >> To: dev
> > > >> > > > > > >> > >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0
> Release
> > > >> > > > > > >> > >>
> > > >> > > > > > >> > >> OK, so right now it's just docs? How soon can we
> > get a
> > > >> VOTE
> > > >> > > > > thread
> > > >> > > > > > >> > started
> > > >> > > > > > >> > >> for 4.0.0?
> > > >> > > > > > >> > >>
> > > >> > > > > > >> > >> On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <
> > > >> > > > > > agrieve@chromium.org>
> > > >> > > > > > >> > >> wrote:
> > > >> > > > > > >> > >>
> > > >> > > > > > >> > >> > mobilespec is now working again... Took longer
> > than
> > > I
> > > >> > would
> > > >> > > > > have
> > > >> > > > > > >> > >> > liked, but did you know that on Android
> FileReader
> > > >> > triggers
> > > >> > > > > > >> > >> > shouldInterceptRequest() with Blob URLs!?
> > > >> > > > > > >> > >> >
> > > >> > > > > > >> > >> > Separate thread is already happening re:
> > whitelists,
> > > >> so
> > > >> > > once
> > > >> > > > > > that's
> > > >> > > > > > >> > >> > figured out, it's just docs afaict.
> > > >> > > > > > >> > >> >
> > > >> > > > > > >> > >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian Clelland <
> > > >> > > > > > >> iclelland@chromium.org
> > > >> > > > > > >> > >
> > > >> > > > > > >> > >> > wrote:
> > > >> > > > > > >> > >> >
> > > >> > > > > > >> > >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <
> > > >> > > > > purplecabbage@gmail.com
> > > >> > > > > > >
> > > >> > > > > > >> > wrote:
> > > >> > > > > > >> > >> > >
> > > >> > > > > > >> > >> > > > We should start a new whitelist plugin
> related
> > > >> > thread.
> > > >> > > > > > >> > >> > > >
> > > >> > > > > > >> > >> > > > Why is a plugin blocking a release? Default
> > > (aka
> > > >> > > > > no-plugin)
> > > >> > > > > > >> > >> > > > behavior should be to allow all network
> > requests
> > > >> > > > shouldn't
> > > >> > > > > > it?
> > > >> > > > > > >> > >> > >
> > > >> > > > > > >> > >> > >
> > > >> > > > > > >> > >> > > Well, that just might be a blacklist then :)
> > > >> > > > > > >> > >> > >
> > > >> > > > > > >> > >> > >
> > > >> > > > > > >> > >> > > > This thread is a
> > > >> > > > > > >> > >> > > > month long, and not the first discussion of
> > > 4.0.0
> > > >> for
> > > >> > > > > > Android.
> > > >> > > > > > >> > >> > > >
> > > >> > > > > > >> > >> > >
> > > >> > > > > > >> > >> > > Seriously, though -- the whitelist discussion
> is
> > > >> much
> > > >> > > > longer
> > > >> > > > > > than
> > > >> > > > > > >> > >> > > that,
> > > >> > > > > > >> > >> > and
> > > >> > > > > > >> > >> > > this isn't the first time that the default
> > > >> > > > no-network-access
> > > >> > > > > > >> policy
> > > >> > > > > > >> > >> > > has been brought up:
> > > >> > > > > > >> > >> > >
> > > >> > > > > > >> > >> > > (Here's the first question, from *July*:
> > > >> > > > > > >> > >> > > http://markmail.org/message/t4vj4saisem2mcgw
> > > >> > > > > > >> > >> > > Here's where I mentioned what the implemented
> > > policy
> > > >> > was:
> > > >> > > > > > >> > >> > > http://markmail.org/message/s4necfnh4hnblpjm
> > > >> > > > > > >> > >> > > And in another discussion:
> > > >> > > > > > >> > >> > > http://markmail.org/message/ap7syhqysizmsvrz)
> > > >> > > > > > >> > >> > >
> > > >> > > > > > >> > >> > > If we want to reconsider that decision, then
> we
> > > >> should
> > > >> > > > > > certainly
> > > >> > > > > > >> do
> > > >> > > > > > >> > >> > > so before we cut a release. I think it would
> be
> > a
> > > >> real
> > > >> > > > > problem
> > > >> > > > > > to
> > > >> > > > > > >> > >> > > change it afterwards, so let's get it right.
> > > >> > > > > > >> > >> > >
> > > >> > > > > > >> > >> > > Also, it's not the plugin itself that's
> blocking
> > > the
> > > >> > > > release,
> > > >> > > > > > >> it's
> > > >> > > > > > >> > >> > > us making sure that we've implemented the core
> > > hooks
> > > >> > > > > correctly
> > > >> > > > > > so
> > > >> > > > > > >> > >> > > that the plugin can actually do its job, and
> > that
> > > >> > people
> > > >> > > > who
> > > >> > > > > > >> don't
> > > >> > > > > > >> > >> > > want that particular plugin can make a better
> > one.
> > > >> > > > > > >> > >> > >
> > > >> > > > > > >> > >> > > (It is also an issue that a plugin, required
> for
> > > >> > > > > > cordova-android
> > > >> > > > > > >> > >> > > 4.0.0, breaks apps which are also building for
> > > >> > > cordova-ios
> > > >> > > > > > 3.8.0.
> > > >> > > > > > >> > >> > > I'll take a
> > > >> > > > > > >> > >> > look
> > > >> > > > > > >> > >> > > at that, and either remove the ios-native
> > portions
> > > >> of
> > > >> > the
> > > >> > > > > > >> whitelist
> > > >> > > > > > >> > >> > plugin,
> > > >> > > > > > >> > >> > > or neuter it so that it doesn't interfere with
> > an
> > > >> ios
> > > >> > app
> > > >> > > > if
> > > >> > > > > > it's
> > > >> > > > > > >> > >> > > not on the unplug-whitelist branch of that
> > repo.)
> > > >> > > > > > >> > >> > >
> > > >> > > > > > >> > >> > > Ian
> > > >> > > > > > >> > >> > >
> > > >> > > > > > >> > >> > >
> > > >> > > > > > >> > >> > > > @purplecabbage
> > > >> > > > > > >> > >> > > > risingj.com
> > > >> > > > > > >> > >> > > >
> > > >> > > > > > >> > >> > > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <
> > > >> > > > shazron@gmail.com
> > > >> > > > > >
> > > >> > > > > > >> > wrote:
> > > >> > > > > > >> > >> > > >
> > > >> > > > > > >> > >> > > > > legacy-whitelist-plugin should be fixed so
> > > that
> > > >> it
> > > >> > > > > compiles
> > > >> > > > > > >> on
> > > >> > > > > > >> > >> > > > > cordova-ios@3.8.0. It shouldn't be a
> > problem
> > > to
> > > >> > fix
> > > >> > > > this
> > > >> > > > > > at
> > > >> > > > > > >> > >> > > > > compile
> > > >> > > > > > >> > >> > or
> > > >> > > > > > >> > >> > > > > run-time (whichever is applicable here
> > related
> > > >> to
> > > >> > the
> > > >> > > > > > compile
> > > >> > > > > > >> > >> > > > > error)
> > > >> > > > > > >> > >> > > > >
> > > >> > > > > > >> > >> > > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl
> Pogue
> > > >> > > > > > >> > >> > > > > <dv...@gmail.com>
> > > >> > > > > > >> > >> > > > wrote:
> > > >> > > > > > >> > >> > > > > > On 2 March 2015 at 13:37, Joe Bowser <
> > > >> > > > > bowserj@gmail.com>
> > > >> > > > > > >> > wrote:
> > > >> > > > > > >> > >> > > > > >> So, right now the whitelist changes are
> > > >> what's
> > > >> > > > holding
> > > >> > > > > > up
> > > >> > > > > > >> the
> > > >> > > > > > >> > >> > 4.0.0
> > > >> > > > > > >> > >> > > > > release
> > > >> > > > > > >> > >> > > > > >> now? Is this really the only thing
> > that's
> > > >> > holding
> > > >> > > > up
> > > >> > > > > > this
> > > >> > > > > > >> > >> > release?
> > > >> > > > > > >> > >> > > > > >>
> > > >> > > > > > >> > >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM Andrew
> > > >> Grieve <
> > > >> > > > > > >> > >> > > agrieve@chromium.org>
> > > >> > > > > > >> > >> > > > > wrote:
> > > >> > > > > > >> > >> > > > > >>
> > > >> > > > > > >> > >> > > > > >>> I think we'll also need to finish with
> > the
> > > >> > > > whitelist
> > > >> > > > > > >> changes
> > > >> > > > > > >> > >> > > > > >>> &
> > > >> > > > > > >> > >> > have
> > > >> > > > > > >> > >> > > > > both
> > > >> > > > > > >> > >> > > > > >>> the legacy and new-way whitelist
> plugins
> > > >> > released
> > > >> > > > > > before
> > > >> > > > > > >> we
> > > >> > > > > > >> > >> > > > > >>> can
> > > >> > > > > > >> > >> > do
> > > >> > > > > > >> > >> > > a
> > > >> > > > > > >> > >> > > > > 4.0.0
> > > >> > > > > > >> > >> > > > > >>> release (otherwise you wouldn't be
> able
> > to
> > > >> > write
> > > >> > > an
> > > >> > > > > app
> > > >> > > > > > >> that
> > > >> > > > > > >> > >> > > > > >>> hits
> > > >> > > > > > >> > >> > > the
> > > >> > > > > > >> > >> > > > > >>> network)
> > > >> > > > > > >> > >> > > > > >>>
> > > >> > > > > > >> > >> > > > > >
> > > >> > > > > > >> > >> > > > > > Just FYI, the whitelist stuff is proving
> > to
> > > >> be a
> > > >> > > bit
> > > >> > > > > of a
> > > >> > > > > > >> pain
> > > >> > > > > > >> > >> > point.
> > > >> > > > > > >> > >> > > > > > I'm using cordova-android@master, and
> > need
> > > to
> > > >> > > > install
> > > >> > > > > > the
> > > >> > > > > > >> > >> > > > > > legacy-whitelist plugin in order to make
> > > >> network
> > > >> > > > > > requests.
> > > >> > > > > > >> > >> > > > > > Once the plugin is installed, everything
> > > >> seems to
> > > >> > > > work.
> > > >> > > > > > >> > >> > > > > >
> > > >> > > > > > >> > >> > > > > > The problem is that the legacy-whitelist
> > > >> plugin
> > > >> > > > > generates
> > > >> > > > > > >> > >> > > > > > compile errors with cordova-ios@3.8.0,
> so
> > > >> now I
> > > >> > > > can't
> > > >> > > > > > just
> > > >> > > > > > >> > run
> > > >> > > > > > >> > >> > > > > > `cordova build`, I need to split the
> > > >> platforms up
> > > >> > > and
> > > >> > > > > > >> > >> > > > > > install/uninstall the plugin in between.
> > If
> > > >> > someone
> > > >> > > > > > makes a
> > > >> > > > > > >> > >> > > > > > dev build for Android and forgets the
> > > plugin,
> > > >> it
> > > >> > > will
> > > >> > > > > > >> appear
> > > >> > > > > > >> > >> > > > > > to build successfully but not actually
> > > >> function
> > > >> > > > > properly
> > > >> > > > > > >> due
> > > >> > > > > > >> > to
> > > >> > > > > > >> > >> the whitelist.
> > > >> > > > > > >> > >> > > > > >
> > > >> > > > > > >> > >> > > > > > I know, this is all pre-release, so pain
> > is
> > > >> > > somewhat
> > > >> > > > > > >> expected
> > > >> > > > > > >> > >> > > > > > right now. I'm worried about the case
> > where
> > > >> > > > > > >> > >> > > > > > cordova-android@4.0.0 is released and
> > > >> > > > > cordova-ios@3.8.0
> > > >> > > > > > is
> > > >> > > > > > >> > >> > > > > > still current, and how people
> > > >> > > > > > >> > >> > can
> > > >> > > > > > >> > >> > > > > > avoid whitelist breakage there.
> > > >> > > > > > >> > >> > > > > >
> > > >> > > > > > >> > >> > > > > >
> > > >> > > > > > >> ------------------------------
> > > ------------------------------
> > > >> > > > > > >> > >> > ---------
> > > >> > > > > > >> > >> > > > > > To unsubscribe, e-mail:
> > > >> > > > > > dev-unsubscribe@cordova.apache.org
> > > >> > > > > > >> > >> > > > > > For additional commands, e-mail:
> > > >> > > > > > >> dev-help@cordova.apache.org
> > > >> > > > > > >> > >> > > > > >
> > > >> > > > > > >> > >> > > > >
> > > >> > > > > > >> > >> > > > >
> > > >> > > > > >
> ------------------------------------------------------------
> > > >> > > > > > >> > >> > ---------
> > > >> > > > > > >> > >> > > > > To unsubscribe, e-mail:
> > > >> > > > > dev-unsubscribe@cordova.apache.org
> > > >> > > > > > >> > >> > > > > For additional commands, e-mail:
> > > >> > > > > > dev-help@cordova.apache.org
> > > >> > > > > > >> > >> > > > >
> > > >> > > > > > >> > >> > > > >
> > > >> > > > > > >> > >> > > >
> > > >> > > > > > >> > >> > >
> > > >> > > > > > >> > >> >
> > > >> > > > > > >> > >>
> > > >> > > > > > >> >
> > > >> > > > > > >> >
> > > >> > > > >
> > > >>
> ---------------------------------------------------------------------
> > > >> > > > > > >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.
> > > apache.org
> > > >> > > > > > >> > For additional commands, e-mail:
> > > >> dev-help@cordova.apache.org
> > > >> > > > > > >> >
> > > >> > > > > > >> >
> > > >> > > > > > >>
> > > >> > > > > > >
> > > >> > > > > > >
> > > >> > > > > >
> > > >> > > > >
> > > >> > > > >
> > > >> > > > >
> > > >> > > > > --
> > > >> > > > > Carlos Santana
> > > >> > > > > <cs...@gmail.com>
> > > >> > > > >
> > > >> > > >
> > > >> > >
> > > >> >
> > > >>
> > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Michal Mocny <mm...@chromium.org>.
Splashscreens was mentioned, icons was not. I don't think there is an
icons change?
On Thu, Apr 9, 2015 at 1:17 PM, Joe Bowser <bo...@gmail.com> wrote:
> So, wasn't there a change regarding icons and spashscreens being moved? I
> have no idea if we want to add that, or if adding that should happen after
> the release?
>
> On Wed, Apr 8, 2015 at 7:09 PM Andrew Grieve <ag...@chromium.org> wrote:
>
> > CB-8684 is now merged and I've updated the targetSdk (and made a couple
> > other changes).
> >
> > I'll start the release process in the morning as long as there no
> > objections.
> >
> >
> > On Tue, Apr 7, 2015 at 2:20 PM, Andrew Grieve <ag...@chromium.org>
> > wrote:
> >
> > > I'll start on it once CB-8684 lands (Tony - assuming you'll have this
> > done
> > > shortly and would prefer it lands?)
> > >
> > > On Tue, Apr 7, 2015 at 1:33 PM, Jesse <pu...@gmail.com> wrote:
> > >
> > >> Sweet!
> > >>
> > >> @purplecabbage
> > >> risingj.com
> > >>
> > >> On Tue, Apr 7, 2015 at 8:35 AM, Andrew Grieve <ag...@chromium.org>
> > >> wrote:
> > >>
> > >> > Let's do it!
> > >> >
> > >> > On Mon, Apr 6, 2015 at 7:33 PM, Joe Bowser <bo...@gmail.com>
> wrote:
> > >> >
> > >> > > So, I think we should put off the embedder's guide until after the
> > >> > > release. A lot of it has changed, and since we're still
> technically
> > >> > > obligated to support the 3.x release tree for six months, that
> > should
> > >> buy
> > >> > > us some time to figure out how that is going to work. Getting
> > >> Cordova to
> > >> > > work with a vanilla Android Studio project is a non-trivial task.
> > >> > >
> > >> > > Given that everything else appears to be done, should we start
> > voting
> > >> on
> > >> > an
> > >> > > RC for this? What do people think?
> > >> > >
> > >> > >
> > >> > >
> > >> > > On Thu, Mar 19, 2015 at 10:31 AM Andrew Grieve <
> > agrieve@chromium.org>
> > >> > > wrote:
> > >> > >
> > >> > > > Here's issues:
> > >> > > > https://issues.apache.org/jira/browse/CB-8715 (docs)
> > >> > > > https://issues.apache.org/jira/browse/CB-8716 (whitelist)
> > >> > > > https://issues.apache.org/jira/browse/CB-8717 (write
> > >> RELEASENOTES.md)
> > >> > > >
> > >> > > > On Tue, Mar 17, 2015 at 10:15 AM, Carlos Santana <
> > >> csantana23@gmail.com
> > >> > >
> > >> > > > wrote:
> > >> > > >
> > >> > > > > I would say let's start RC testing and voting, But not pin the
> > >> > version
> > >> > > in
> > >> > > > > Cordova CLI until the tasks that Andrew mentioned are done.
> > >> > > > > Andrew can you create the JIRA Items for the tasks that need
> to
> > be
> > >> > > done.
> > >> > > > I
> > >> > > > > thought there was a discussion about creating JIRA Items to
> help
> > >> > track
> > >> > > > and
> > >> > > > > know what's left for release something.
> > >> > > > >
> > >> > > > > - upgrade guide,
> > >> > > > > - publishing whitelist plugins,
> > >> > > > > - and making it so that the default project template includes
> > >> <plugin
> > >> > > > > name="cordova-plugin-whitelist" />)
> > >> > > > >
> > >> > > > >
> > >> > > > > On Mon, Mar 16, 2015 at 11:21 PM, Ian Clelland <
> > >> > iclelland@chromium.org
> > >> > > >
> > >> > > > > wrote:
> > >> > > > >
> > >> > > > > > We'll probably need at least an RC for the whitelist plugin,
> > if
> > >> > not a
> > >> > > > > vote,
> > >> > > > > > to be able to vote on this.
> > >> > > > > >
> > >> > > > > > Or can we just include instructions like "Use
> > >> > > > > > cordova-plugin-whitelist@f70b1bc for testing" while we
> start
> > >> the
> > >> > > > > official
> > >> > > > > > release process for the plugins?
> > >> > > > > >
> > >> > > > > > On Mon, Mar 16, 2015 at 11:17 PM, Ian Clelland <
> > >> > > iclelland@chromium.org
> > >> > > > >
> > >> > > > > > wrote:
> > >> > > > > >
> > >> > > > > > > +1 -- Let's get this out the door :)
> > >> > > > > > > I'll see what I can get done to move it in that direction.
> > >> > > > > > >
> > >> > > > > > > On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <
> > >> > > agrieve@chromium.org
> > >> > > > >
> > >> > > > > > > wrote:
> > >> > > > > > >
> > >> > > > > > >> Everything's ready afaik (minus upgrade guide, publishing
> > >> > > whitelist
> > >> > > > > > >> plugins, and making it so that the default project
> template
> > >> > > includes
> > >> > > > > > >> <plugin name="cordova-plugin-whitelist" />). Maybe let's
> > do
> > >> a RC
> > >> > > > while
> > >> > > > > > we
> > >> > > > > > >> wait on these things being finished up?
> > >> > > > > > >>
> > >> > > > > > >> If anyone wants to take on any of these tasks, that would
> > be
> > >> > > > awesome.
> > >> > > > > > >>
> > >> > > > > > >> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <
> > shazron@gmail.com>
> > >> > > wrote:
> > >> > > > > > >>
> > >> > > > > > >> > +1 for vote thread, let's get this thing out so people
> > >> (that
> > >> > are
> > >> > > > not
> > >> > > > > > >> > us) can test...
> > >> > > > > > >> >
> > >> > > > > > >> >
> > >> > > > > > >> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <
> > >> > bowserj@gmail.com>
> > >> > > > > > wrote:
> > >> > > > > > >> > > OK, this is a three month old thread, and we're
> waiting
> > >> on a
> > >> > > > > > >> discussion
> > >> > > > > > >> > > before we release something? I really think we should
> > go
> > >> to
> > >> > a
> > >> > > > vote
> > >> > > > > > >> thread
> > >> > > > > > >> > > now that we have a legacy whitelist plugin and a new
> > >> style
> > >> > > > > whitelist
> > >> > > > > > >> > > plugin. We shouldn't keep constantly delaying this
> > >> release
> > >> > > > > because
> > >> > > > > > of
> > >> > > > > > >> > > what's happening on other platforms, especially since
> > we
> > >> > > already
> > >> > > > > > >> > pluginized
> > >> > > > > > >> > > the whitelist.
> > >> > > > > > >> > >
> > >> > > > > > >> > > Can we please release soon?
> > >> > > > > > >> > >
> > >> > > > > > >> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil Khandelwal <
> > >> > > > > > >> > nikhilkh@microsoft.com>
> > >> > > > > > >> > > wrote:
> > >> > > > > > >> > >
> > >> > > > > > >> > >> I know we discussed a couple of approaches
> > implementing
> > >> the
> > >> > > > > default
> > >> > > > > > >> > >> whitelist policy for Android/iOS - either every app
> > >> would
> > >> > be
> > >> > > > > > >> required to
> > >> > > > > > >> > >> include the whitelist plugin or have it have smart
> > >> defaults
> > >> > > in
> > >> > > > > the
> > >> > > > > > >> > platform
> > >> > > > > > >> > >> implementation and the plugin being able to override
> > >> them.
> > >> > > > > > >> > >>
> > >> > > > > > >> > >> I don’t think that thread closed with any
> conclusions.
> > >> > > > > > >> > >>
> > >> > > > > > >> > >> Thanks,
> > >> > > > > > >> > >> Nikhil
> > >> > > > > > >> > >>
> > >> > > > > > >> > >>
> > >> > > > > > >> > >> -----Original Message-----
> > >> > > > > > >> > >> From: Joe Bowser [mailto:bowserj@gmail.com]
> > >> > > > > > >> > >> Sent: Thursday, March 12, 2015 11:23 AM
> > >> > > > > > >> > >> To: dev
> > >> > > > > > >> > >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > >> > > > > > >> > >>
> > >> > > > > > >> > >> OK, so right now it's just docs? How soon can we
> get a
> > >> VOTE
> > >> > > > > thread
> > >> > > > > > >> > started
> > >> > > > > > >> > >> for 4.0.0?
> > >> > > > > > >> > >>
> > >> > > > > > >> > >> On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <
> > >> > > > > > agrieve@chromium.org>
> > >> > > > > > >> > >> wrote:
> > >> > > > > > >> > >>
> > >> > > > > > >> > >> > mobilespec is now working again... Took longer
> than
> > I
> > >> > would
> > >> > > > > have
> > >> > > > > > >> > >> > liked, but did you know that on Android FileReader
> > >> > triggers
> > >> > > > > > >> > >> > shouldInterceptRequest() with Blob URLs!?
> > >> > > > > > >> > >> >
> > >> > > > > > >> > >> > Separate thread is already happening re:
> whitelists,
> > >> so
> > >> > > once
> > >> > > > > > that's
> > >> > > > > > >> > >> > figured out, it's just docs afaict.
> > >> > > > > > >> > >> >
> > >> > > > > > >> > >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian Clelland <
> > >> > > > > > >> iclelland@chromium.org
> > >> > > > > > >> > >
> > >> > > > > > >> > >> > wrote:
> > >> > > > > > >> > >> >
> > >> > > > > > >> > >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <
> > >> > > > > purplecabbage@gmail.com
> > >> > > > > > >
> > >> > > > > > >> > wrote:
> > >> > > > > > >> > >> > >
> > >> > > > > > >> > >> > > > We should start a new whitelist plugin related
> > >> > thread.
> > >> > > > > > >> > >> > > >
> > >> > > > > > >> > >> > > > Why is a plugin blocking a release? Default
> > (aka
> > >> > > > > no-plugin)
> > >> > > > > > >> > >> > > > behavior should be to allow all network
> requests
> > >> > > > shouldn't
> > >> > > > > > it?
> > >> > > > > > >> > >> > >
> > >> > > > > > >> > >> > >
> > >> > > > > > >> > >> > > Well, that just might be a blacklist then :)
> > >> > > > > > >> > >> > >
> > >> > > > > > >> > >> > >
> > >> > > > > > >> > >> > > > This thread is a
> > >> > > > > > >> > >> > > > month long, and not the first discussion of
> > 4.0.0
> > >> for
> > >> > > > > > Android.
> > >> > > > > > >> > >> > > >
> > >> > > > > > >> > >> > >
> > >> > > > > > >> > >> > > Seriously, though -- the whitelist discussion is
> > >> much
> > >> > > > longer
> > >> > > > > > than
> > >> > > > > > >> > >> > > that,
> > >> > > > > > >> > >> > and
> > >> > > > > > >> > >> > > this isn't the first time that the default
> > >> > > > no-network-access
> > >> > > > > > >> policy
> > >> > > > > > >> > >> > > has been brought up:
> > >> > > > > > >> > >> > >
> > >> > > > > > >> > >> > > (Here's the first question, from *July*:
> > >> > > > > > >> > >> > > http://markmail.org/message/t4vj4saisem2mcgw
> > >> > > > > > >> > >> > > Here's where I mentioned what the implemented
> > policy
> > >> > was:
> > >> > > > > > >> > >> > > http://markmail.org/message/s4necfnh4hnblpjm
> > >> > > > > > >> > >> > > And in another discussion:
> > >> > > > > > >> > >> > > http://markmail.org/message/ap7syhqysizmsvrz)
> > >> > > > > > >> > >> > >
> > >> > > > > > >> > >> > > If we want to reconsider that decision, then we
> > >> should
> > >> > > > > > certainly
> > >> > > > > > >> do
> > >> > > > > > >> > >> > > so before we cut a release. I think it would be
> a
> > >> real
> > >> > > > > problem
> > >> > > > > > to
> > >> > > > > > >> > >> > > change it afterwards, so let's get it right.
> > >> > > > > > >> > >> > >
> > >> > > > > > >> > >> > > Also, it's not the plugin itself that's blocking
> > the
> > >> > > > release,
> > >> > > > > > >> it's
> > >> > > > > > >> > >> > > us making sure that we've implemented the core
> > hooks
> > >> > > > > correctly
> > >> > > > > > so
> > >> > > > > > >> > >> > > that the plugin can actually do its job, and
> that
> > >> > people
> > >> > > > who
> > >> > > > > > >> don't
> > >> > > > > > >> > >> > > want that particular plugin can make a better
> one.
> > >> > > > > > >> > >> > >
> > >> > > > > > >> > >> > > (It is also an issue that a plugin, required for
> > >> > > > > > cordova-android
> > >> > > > > > >> > >> > > 4.0.0, breaks apps which are also building for
> > >> > > cordova-ios
> > >> > > > > > 3.8.0.
> > >> > > > > > >> > >> > > I'll take a
> > >> > > > > > >> > >> > look
> > >> > > > > > >> > >> > > at that, and either remove the ios-native
> portions
> > >> of
> > >> > the
> > >> > > > > > >> whitelist
> > >> > > > > > >> > >> > plugin,
> > >> > > > > > >> > >> > > or neuter it so that it doesn't interfere with
> an
> > >> ios
> > >> > app
> > >> > > > if
> > >> > > > > > it's
> > >> > > > > > >> > >> > > not on the unplug-whitelist branch of that
> repo.)
> > >> > > > > > >> > >> > >
> > >> > > > > > >> > >> > > Ian
> > >> > > > > > >> > >> > >
> > >> > > > > > >> > >> > >
> > >> > > > > > >> > >> > > > @purplecabbage
> > >> > > > > > >> > >> > > > risingj.com
> > >> > > > > > >> > >> > > >
> > >> > > > > > >> > >> > > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <
> > >> > > > shazron@gmail.com
> > >> > > > > >
> > >> > > > > > >> > wrote:
> > >> > > > > > >> > >> > > >
> > >> > > > > > >> > >> > > > > legacy-whitelist-plugin should be fixed so
> > that
> > >> it
> > >> > > > > compiles
> > >> > > > > > >> on
> > >> > > > > > >> > >> > > > > cordova-ios@3.8.0. It shouldn't be a
> problem
> > to
> > >> > fix
> > >> > > > this
> > >> > > > > > at
> > >> > > > > > >> > >> > > > > compile
> > >> > > > > > >> > >> > or
> > >> > > > > > >> > >> > > > > run-time (whichever is applicable here
> related
> > >> to
> > >> > the
> > >> > > > > > compile
> > >> > > > > > >> > >> > > > > error)
> > >> > > > > > >> > >> > > > >
> > >> > > > > > >> > >> > > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue
> > >> > > > > > >> > >> > > > > <dv...@gmail.com>
> > >> > > > > > >> > >> > > > wrote:
> > >> > > > > > >> > >> > > > > > On 2 March 2015 at 13:37, Joe Bowser <
> > >> > > > > bowserj@gmail.com>
> > >> > > > > > >> > wrote:
> > >> > > > > > >> > >> > > > > >> So, right now the whitelist changes are
> > >> what's
> > >> > > > holding
> > >> > > > > > up
> > >> > > > > > >> the
> > >> > > > > > >> > >> > 4.0.0
> > >> > > > > > >> > >> > > > > release
> > >> > > > > > >> > >> > > > > >> now? Is this really the only thing
> that's
> > >> > holding
> > >> > > > up
> > >> > > > > > this
> > >> > > > > > >> > >> > release?
> > >> > > > > > >> > >> > > > > >>
> > >> > > > > > >> > >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM Andrew
> > >> Grieve <
> > >> > > > > > >> > >> > > agrieve@chromium.org>
> > >> > > > > > >> > >> > > > > wrote:
> > >> > > > > > >> > >> > > > > >>
> > >> > > > > > >> > >> > > > > >>> I think we'll also need to finish with
> the
> > >> > > > whitelist
> > >> > > > > > >> changes
> > >> > > > > > >> > >> > > > > >>> &
> > >> > > > > > >> > >> > have
> > >> > > > > > >> > >> > > > > both
> > >> > > > > > >> > >> > > > > >>> the legacy and new-way whitelist plugins
> > >> > released
> > >> > > > > > before
> > >> > > > > > >> we
> > >> > > > > > >> > >> > > > > >>> can
> > >> > > > > > >> > >> > do
> > >> > > > > > >> > >> > > a
> > >> > > > > > >> > >> > > > > 4.0.0
> > >> > > > > > >> > >> > > > > >>> release (otherwise you wouldn't be able
> to
> > >> > write
> > >> > > an
> > >> > > > > app
> > >> > > > > > >> that
> > >> > > > > > >> > >> > > > > >>> hits
> > >> > > > > > >> > >> > > the
> > >> > > > > > >> > >> > > > > >>> network)
> > >> > > > > > >> > >> > > > > >>>
> > >> > > > > > >> > >> > > > > >
> > >> > > > > > >> > >> > > > > > Just FYI, the whitelist stuff is proving
> to
> > >> be a
> > >> > > bit
> > >> > > > > of a
> > >> > > > > > >> pain
> > >> > > > > > >> > >> > point.
> > >> > > > > > >> > >> > > > > > I'm using cordova-android@master, and
> need
> > to
> > >> > > > install
> > >> > > > > > the
> > >> > > > > > >> > >> > > > > > legacy-whitelist plugin in order to make
> > >> network
> > >> > > > > > requests.
> > >> > > > > > >> > >> > > > > > Once the plugin is installed, everything
> > >> seems to
> > >> > > > work.
> > >> > > > > > >> > >> > > > > >
> > >> > > > > > >> > >> > > > > > The problem is that the legacy-whitelist
> > >> plugin
> > >> > > > > generates
> > >> > > > > > >> > >> > > > > > compile errors with cordova-ios@3.8.0, so
> > >> now I
> > >> > > > can't
> > >> > > > > > just
> > >> > > > > > >> > run
> > >> > > > > > >> > >> > > > > > `cordova build`, I need to split the
> > >> platforms up
> > >> > > and
> > >> > > > > > >> > >> > > > > > install/uninstall the plugin in between.
> If
> > >> > someone
> > >> > > > > > makes a
> > >> > > > > > >> > >> > > > > > dev build for Android and forgets the
> > plugin,
> > >> it
> > >> > > will
> > >> > > > > > >> appear
> > >> > > > > > >> > >> > > > > > to build successfully but not actually
> > >> function
> > >> > > > > properly
> > >> > > > > > >> due
> > >> > > > > > >> > to
> > >> > > > > > >> > >> the whitelist.
> > >> > > > > > >> > >> > > > > >
> > >> > > > > > >> > >> > > > > > I know, this is all pre-release, so pain
> is
> > >> > > somewhat
> > >> > > > > > >> expected
> > >> > > > > > >> > >> > > > > > right now. I'm worried about the case
> where
> > >> > > > > > >> > >> > > > > > cordova-android@4.0.0 is released and
> > >> > > > > cordova-ios@3.8.0
> > >> > > > > > is
> > >> > > > > > >> > >> > > > > > still current, and how people
> > >> > > > > > >> > >> > can
> > >> > > > > > >> > >> > > > > > avoid whitelist breakage there.
> > >> > > > > > >> > >> > > > > >
> > >> > > > > > >> > >> > > > > >
> > >> > > > > > >> ------------------------------
> > ------------------------------
> > >> > > > > > >> > >> > ---------
> > >> > > > > > >> > >> > > > > > To unsubscribe, e-mail:
> > >> > > > > > dev-unsubscribe@cordova.apache.org
> > >> > > > > > >> > >> > > > > > For additional commands, e-mail:
> > >> > > > > > >> dev-help@cordova.apache.org
> > >> > > > > > >> > >> > > > > >
> > >> > > > > > >> > >> > > > >
> > >> > > > > > >> > >> > > > >
> > >> > > > > > ------------------------------------------------------------
> > >> > > > > > >> > >> > ---------
> > >> > > > > > >> > >> > > > > To unsubscribe, e-mail:
> > >> > > > > dev-unsubscribe@cordova.apache.org
> > >> > > > > > >> > >> > > > > For additional commands, e-mail:
> > >> > > > > > dev-help@cordova.apache.org
> > >> > > > > > >> > >> > > > >
> > >> > > > > > >> > >> > > > >
> > >> > > > > > >> > >> > > >
> > >> > > > > > >> > >> > >
> > >> > > > > > >> > >> >
> > >> > > > > > >> > >>
> > >> > > > > > >> >
> > >> > > > > > >> >
> > >> > > > >
> > >> ---------------------------------------------------------------------
> > >> > > > > > >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.
> > apache.org
> > >> > > > > > >> > For additional commands, e-mail:
> > >> dev-help@cordova.apache.org
> > >> > > > > > >> >
> > >> > > > > > >> >
> > >> > > > > > >>
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > >
> > >> > > > >
> > >> > > > >
> > >> > > > >
> > >> > > > > --
> > >> > > > > Carlos Santana
> > >> > > > > <cs...@gmail.com>
> > >> > > > >
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >
> > >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Joe Bowser <bo...@gmail.com>.
So, wasn't there a change regarding icons and spashscreens being moved? I
have no idea if we want to add that, or if adding that should happen after
the release?
On Wed, Apr 8, 2015 at 7:09 PM Andrew Grieve <ag...@chromium.org> wrote:
> CB-8684 is now merged and I've updated the targetSdk (and made a couple
> other changes).
>
> I'll start the release process in the morning as long as there no
> objections.
>
>
> On Tue, Apr 7, 2015 at 2:20 PM, Andrew Grieve <ag...@chromium.org>
> wrote:
>
> > I'll start on it once CB-8684 lands (Tony - assuming you'll have this
> done
> > shortly and would prefer it lands?)
> >
> > On Tue, Apr 7, 2015 at 1:33 PM, Jesse <pu...@gmail.com> wrote:
> >
> >> Sweet!
> >>
> >> @purplecabbage
> >> risingj.com
> >>
> >> On Tue, Apr 7, 2015 at 8:35 AM, Andrew Grieve <ag...@chromium.org>
> >> wrote:
> >>
> >> > Let's do it!
> >> >
> >> > On Mon, Apr 6, 2015 at 7:33 PM, Joe Bowser <bo...@gmail.com> wrote:
> >> >
> >> > > So, I think we should put off the embedder's guide until after the
> >> > > release. A lot of it has changed, and since we're still technically
> >> > > obligated to support the 3.x release tree for six months, that
> should
> >> buy
> >> > > us some time to figure out how that is going to work. Getting
> >> Cordova to
> >> > > work with a vanilla Android Studio project is a non-trivial task.
> >> > >
> >> > > Given that everything else appears to be done, should we start
> voting
> >> on
> >> > an
> >> > > RC for this? What do people think?
> >> > >
> >> > >
> >> > >
> >> > > On Thu, Mar 19, 2015 at 10:31 AM Andrew Grieve <
> agrieve@chromium.org>
> >> > > wrote:
> >> > >
> >> > > > Here's issues:
> >> > > > https://issues.apache.org/jira/browse/CB-8715 (docs)
> >> > > > https://issues.apache.org/jira/browse/CB-8716 (whitelist)
> >> > > > https://issues.apache.org/jira/browse/CB-8717 (write
> >> RELEASENOTES.md)
> >> > > >
> >> > > > On Tue, Mar 17, 2015 at 10:15 AM, Carlos Santana <
> >> csantana23@gmail.com
> >> > >
> >> > > > wrote:
> >> > > >
> >> > > > > I would say let's start RC testing and voting, But not pin the
> >> > version
> >> > > in
> >> > > > > Cordova CLI until the tasks that Andrew mentioned are done.
> >> > > > > Andrew can you create the JIRA Items for the tasks that need to
> be
> >> > > done.
> >> > > > I
> >> > > > > thought there was a discussion about creating JIRA Items to help
> >> > track
> >> > > > and
> >> > > > > know what's left for release something.
> >> > > > >
> >> > > > > - upgrade guide,
> >> > > > > - publishing whitelist plugins,
> >> > > > > - and making it so that the default project template includes
> >> <plugin
> >> > > > > name="cordova-plugin-whitelist" />)
> >> > > > >
> >> > > > >
> >> > > > > On Mon, Mar 16, 2015 at 11:21 PM, Ian Clelland <
> >> > iclelland@chromium.org
> >> > > >
> >> > > > > wrote:
> >> > > > >
> >> > > > > > We'll probably need at least an RC for the whitelist plugin,
> if
> >> > not a
> >> > > > > vote,
> >> > > > > > to be able to vote on this.
> >> > > > > >
> >> > > > > > Or can we just include instructions like "Use
> >> > > > > > cordova-plugin-whitelist@f70b1bc for testing" while we start
> >> the
> >> > > > > official
> >> > > > > > release process for the plugins?
> >> > > > > >
> >> > > > > > On Mon, Mar 16, 2015 at 11:17 PM, Ian Clelland <
> >> > > iclelland@chromium.org
> >> > > > >
> >> > > > > > wrote:
> >> > > > > >
> >> > > > > > > +1 -- Let's get this out the door :)
> >> > > > > > > I'll see what I can get done to move it in that direction.
> >> > > > > > >
> >> > > > > > > On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <
> >> > > agrieve@chromium.org
> >> > > > >
> >> > > > > > > wrote:
> >> > > > > > >
> >> > > > > > >> Everything's ready afaik (minus upgrade guide, publishing
> >> > > whitelist
> >> > > > > > >> plugins, and making it so that the default project template
> >> > > includes
> >> > > > > > >> <plugin name="cordova-plugin-whitelist" />). Maybe let's
> do
> >> a RC
> >> > > > while
> >> > > > > > we
> >> > > > > > >> wait on these things being finished up?
> >> > > > > > >>
> >> > > > > > >> If anyone wants to take on any of these tasks, that would
> be
> >> > > > awesome.
> >> > > > > > >>
> >> > > > > > >> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <
> shazron@gmail.com>
> >> > > wrote:
> >> > > > > > >>
> >> > > > > > >> > +1 for vote thread, let's get this thing out so people
> >> (that
> >> > are
> >> > > > not
> >> > > > > > >> > us) can test...
> >> > > > > > >> >
> >> > > > > > >> >
> >> > > > > > >> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <
> >> > bowserj@gmail.com>
> >> > > > > > wrote:
> >> > > > > > >> > > OK, this is a three month old thread, and we're waiting
> >> on a
> >> > > > > > >> discussion
> >> > > > > > >> > > before we release something? I really think we should
> go
> >> to
> >> > a
> >> > > > vote
> >> > > > > > >> thread
> >> > > > > > >> > > now that we have a legacy whitelist plugin and a new
> >> style
> >> > > > > whitelist
> >> > > > > > >> > > plugin. We shouldn't keep constantly delaying this
> >> release
> >> > > > > because
> >> > > > > > of
> >> > > > > > >> > > what's happening on other platforms, especially since
> we
> >> > > already
> >> > > > > > >> > pluginized
> >> > > > > > >> > > the whitelist.
> >> > > > > > >> > >
> >> > > > > > >> > > Can we please release soon?
> >> > > > > > >> > >
> >> > > > > > >> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil Khandelwal <
> >> > > > > > >> > nikhilkh@microsoft.com>
> >> > > > > > >> > > wrote:
> >> > > > > > >> > >
> >> > > > > > >> > >> I know we discussed a couple of approaches
> implementing
> >> the
> >> > > > > default
> >> > > > > > >> > >> whitelist policy for Android/iOS - either every app
> >> would
> >> > be
> >> > > > > > >> required to
> >> > > > > > >> > >> include the whitelist plugin or have it have smart
> >> defaults
> >> > > in
> >> > > > > the
> >> > > > > > >> > platform
> >> > > > > > >> > >> implementation and the plugin being able to override
> >> them.
> >> > > > > > >> > >>
> >> > > > > > >> > >> I don’t think that thread closed with any conclusions.
> >> > > > > > >> > >>
> >> > > > > > >> > >> Thanks,
> >> > > > > > >> > >> Nikhil
> >> > > > > > >> > >>
> >> > > > > > >> > >>
> >> > > > > > >> > >> -----Original Message-----
> >> > > > > > >> > >> From: Joe Bowser [mailto:bowserj@gmail.com]
> >> > > > > > >> > >> Sent: Thursday, March 12, 2015 11:23 AM
> >> > > > > > >> > >> To: dev
> >> > > > > > >> > >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> >> > > > > > >> > >>
> >> > > > > > >> > >> OK, so right now it's just docs? How soon can we get a
> >> VOTE
> >> > > > > thread
> >> > > > > > >> > started
> >> > > > > > >> > >> for 4.0.0?
> >> > > > > > >> > >>
> >> > > > > > >> > >> On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <
> >> > > > > > agrieve@chromium.org>
> >> > > > > > >> > >> wrote:
> >> > > > > > >> > >>
> >> > > > > > >> > >> > mobilespec is now working again... Took longer than
> I
> >> > would
> >> > > > > have
> >> > > > > > >> > >> > liked, but did you know that on Android FileReader
> >> > triggers
> >> > > > > > >> > >> > shouldInterceptRequest() with Blob URLs!?
> >> > > > > > >> > >> >
> >> > > > > > >> > >> > Separate thread is already happening re: whitelists,
> >> so
> >> > > once
> >> > > > > > that's
> >> > > > > > >> > >> > figured out, it's just docs afaict.
> >> > > > > > >> > >> >
> >> > > > > > >> > >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian Clelland <
> >> > > > > > >> iclelland@chromium.org
> >> > > > > > >> > >
> >> > > > > > >> > >> > wrote:
> >> > > > > > >> > >> >
> >> > > > > > >> > >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <
> >> > > > > purplecabbage@gmail.com
> >> > > > > > >
> >> > > > > > >> > wrote:
> >> > > > > > >> > >> > >
> >> > > > > > >> > >> > > > We should start a new whitelist plugin related
> >> > thread.
> >> > > > > > >> > >> > > >
> >> > > > > > >> > >> > > > Why is a plugin blocking a release? Default
> (aka
> >> > > > > no-plugin)
> >> > > > > > >> > >> > > > behavior should be to allow all network requests
> >> > > > shouldn't
> >> > > > > > it?
> >> > > > > > >> > >> > >
> >> > > > > > >> > >> > >
> >> > > > > > >> > >> > > Well, that just might be a blacklist then :)
> >> > > > > > >> > >> > >
> >> > > > > > >> > >> > >
> >> > > > > > >> > >> > > > This thread is a
> >> > > > > > >> > >> > > > month long, and not the first discussion of
> 4.0.0
> >> for
> >> > > > > > Android.
> >> > > > > > >> > >> > > >
> >> > > > > > >> > >> > >
> >> > > > > > >> > >> > > Seriously, though -- the whitelist discussion is
> >> much
> >> > > > longer
> >> > > > > > than
> >> > > > > > >> > >> > > that,
> >> > > > > > >> > >> > and
> >> > > > > > >> > >> > > this isn't the first time that the default
> >> > > > no-network-access
> >> > > > > > >> policy
> >> > > > > > >> > >> > > has been brought up:
> >> > > > > > >> > >> > >
> >> > > > > > >> > >> > > (Here's the first question, from *July*:
> >> > > > > > >> > >> > > http://markmail.org/message/t4vj4saisem2mcgw
> >> > > > > > >> > >> > > Here's where I mentioned what the implemented
> policy
> >> > was:
> >> > > > > > >> > >> > > http://markmail.org/message/s4necfnh4hnblpjm
> >> > > > > > >> > >> > > And in another discussion:
> >> > > > > > >> > >> > > http://markmail.org/message/ap7syhqysizmsvrz)
> >> > > > > > >> > >> > >
> >> > > > > > >> > >> > > If we want to reconsider that decision, then we
> >> should
> >> > > > > > certainly
> >> > > > > > >> do
> >> > > > > > >> > >> > > so before we cut a release. I think it would be a
> >> real
> >> > > > > problem
> >> > > > > > to
> >> > > > > > >> > >> > > change it afterwards, so let's get it right.
> >> > > > > > >> > >> > >
> >> > > > > > >> > >> > > Also, it's not the plugin itself that's blocking
> the
> >> > > > release,
> >> > > > > > >> it's
> >> > > > > > >> > >> > > us making sure that we've implemented the core
> hooks
> >> > > > > correctly
> >> > > > > > so
> >> > > > > > >> > >> > > that the plugin can actually do its job, and that
> >> > people
> >> > > > who
> >> > > > > > >> don't
> >> > > > > > >> > >> > > want that particular plugin can make a better one.
> >> > > > > > >> > >> > >
> >> > > > > > >> > >> > > (It is also an issue that a plugin, required for
> >> > > > > > cordova-android
> >> > > > > > >> > >> > > 4.0.0, breaks apps which are also building for
> >> > > cordova-ios
> >> > > > > > 3.8.0.
> >> > > > > > >> > >> > > I'll take a
> >> > > > > > >> > >> > look
> >> > > > > > >> > >> > > at that, and either remove the ios-native portions
> >> of
> >> > the
> >> > > > > > >> whitelist
> >> > > > > > >> > >> > plugin,
> >> > > > > > >> > >> > > or neuter it so that it doesn't interfere with an
> >> ios
> >> > app
> >> > > > if
> >> > > > > > it's
> >> > > > > > >> > >> > > not on the unplug-whitelist branch of that repo.)
> >> > > > > > >> > >> > >
> >> > > > > > >> > >> > > Ian
> >> > > > > > >> > >> > >
> >> > > > > > >> > >> > >
> >> > > > > > >> > >> > > > @purplecabbage
> >> > > > > > >> > >> > > > risingj.com
> >> > > > > > >> > >> > > >
> >> > > > > > >> > >> > > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <
> >> > > > shazron@gmail.com
> >> > > > > >
> >> > > > > > >> > wrote:
> >> > > > > > >> > >> > > >
> >> > > > > > >> > >> > > > > legacy-whitelist-plugin should be fixed so
> that
> >> it
> >> > > > > compiles
> >> > > > > > >> on
> >> > > > > > >> > >> > > > > cordova-ios@3.8.0. It shouldn't be a problem
> to
> >> > fix
> >> > > > this
> >> > > > > > at
> >> > > > > > >> > >> > > > > compile
> >> > > > > > >> > >> > or
> >> > > > > > >> > >> > > > > run-time (whichever is applicable here related
> >> to
> >> > the
> >> > > > > > compile
> >> > > > > > >> > >> > > > > error)
> >> > > > > > >> > >> > > > >
> >> > > > > > >> > >> > > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue
> >> > > > > > >> > >> > > > > <dv...@gmail.com>
> >> > > > > > >> > >> > > > wrote:
> >> > > > > > >> > >> > > > > > On 2 March 2015 at 13:37, Joe Bowser <
> >> > > > > bowserj@gmail.com>
> >> > > > > > >> > wrote:
> >> > > > > > >> > >> > > > > >> So, right now the whitelist changes are
> >> what's
> >> > > > holding
> >> > > > > > up
> >> > > > > > >> the
> >> > > > > > >> > >> > 4.0.0
> >> > > > > > >> > >> > > > > release
> >> > > > > > >> > >> > > > > >> now? Is this really the only thing that's
> >> > holding
> >> > > > up
> >> > > > > > this
> >> > > > > > >> > >> > release?
> >> > > > > > >> > >> > > > > >>
> >> > > > > > >> > >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM Andrew
> >> Grieve <
> >> > > > > > >> > >> > > agrieve@chromium.org>
> >> > > > > > >> > >> > > > > wrote:
> >> > > > > > >> > >> > > > > >>
> >> > > > > > >> > >> > > > > >>> I think we'll also need to finish with the
> >> > > > whitelist
> >> > > > > > >> changes
> >> > > > > > >> > >> > > > > >>> &
> >> > > > > > >> > >> > have
> >> > > > > > >> > >> > > > > both
> >> > > > > > >> > >> > > > > >>> the legacy and new-way whitelist plugins
> >> > released
> >> > > > > > before
> >> > > > > > >> we
> >> > > > > > >> > >> > > > > >>> can
> >> > > > > > >> > >> > do
> >> > > > > > >> > >> > > a
> >> > > > > > >> > >> > > > > 4.0.0
> >> > > > > > >> > >> > > > > >>> release (otherwise you wouldn't be able to
> >> > write
> >> > > an
> >> > > > > app
> >> > > > > > >> that
> >> > > > > > >> > >> > > > > >>> hits
> >> > > > > > >> > >> > > the
> >> > > > > > >> > >> > > > > >>> network)
> >> > > > > > >> > >> > > > > >>>
> >> > > > > > >> > >> > > > > >
> >> > > > > > >> > >> > > > > > Just FYI, the whitelist stuff is proving to
> >> be a
> >> > > bit
> >> > > > > of a
> >> > > > > > >> pain
> >> > > > > > >> > >> > point.
> >> > > > > > >> > >> > > > > > I'm using cordova-android@master, and need
> to
> >> > > > install
> >> > > > > > the
> >> > > > > > >> > >> > > > > > legacy-whitelist plugin in order to make
> >> network
> >> > > > > > requests.
> >> > > > > > >> > >> > > > > > Once the plugin is installed, everything
> >> seems to
> >> > > > work.
> >> > > > > > >> > >> > > > > >
> >> > > > > > >> > >> > > > > > The problem is that the legacy-whitelist
> >> plugin
> >> > > > > generates
> >> > > > > > >> > >> > > > > > compile errors with cordova-ios@3.8.0, so
> >> now I
> >> > > > can't
> >> > > > > > just
> >> > > > > > >> > run
> >> > > > > > >> > >> > > > > > `cordova build`, I need to split the
> >> platforms up
> >> > > and
> >> > > > > > >> > >> > > > > > install/uninstall the plugin in between. If
> >> > someone
> >> > > > > > makes a
> >> > > > > > >> > >> > > > > > dev build for Android and forgets the
> plugin,
> >> it
> >> > > will
> >> > > > > > >> appear
> >> > > > > > >> > >> > > > > > to build successfully but not actually
> >> function
> >> > > > > properly
> >> > > > > > >> due
> >> > > > > > >> > to
> >> > > > > > >> > >> the whitelist.
> >> > > > > > >> > >> > > > > >
> >> > > > > > >> > >> > > > > > I know, this is all pre-release, so pain is
> >> > > somewhat
> >> > > > > > >> expected
> >> > > > > > >> > >> > > > > > right now. I'm worried about the case where
> >> > > > > > >> > >> > > > > > cordova-android@4.0.0 is released and
> >> > > > > cordova-ios@3.8.0
> >> > > > > > is
> >> > > > > > >> > >> > > > > > still current, and how people
> >> > > > > > >> > >> > can
> >> > > > > > >> > >> > > > > > avoid whitelist breakage there.
> >> > > > > > >> > >> > > > > >
> >> > > > > > >> > >> > > > > >
> >> > > > > > >> ------------------------------
> ------------------------------
> >> > > > > > >> > >> > ---------
> >> > > > > > >> > >> > > > > > To unsubscribe, e-mail:
> >> > > > > > dev-unsubscribe@cordova.apache.org
> >> > > > > > >> > >> > > > > > For additional commands, e-mail:
> >> > > > > > >> dev-help@cordova.apache.org
> >> > > > > > >> > >> > > > > >
> >> > > > > > >> > >> > > > >
> >> > > > > > >> > >> > > > >
> >> > > > > > ------------------------------------------------------------
> >> > > > > > >> > >> > ---------
> >> > > > > > >> > >> > > > > To unsubscribe, e-mail:
> >> > > > > dev-unsubscribe@cordova.apache.org
> >> > > > > > >> > >> > > > > For additional commands, e-mail:
> >> > > > > > dev-help@cordova.apache.org
> >> > > > > > >> > >> > > > >
> >> > > > > > >> > >> > > > >
> >> > > > > > >> > >> > > >
> >> > > > > > >> > >> > >
> >> > > > > > >> > >> >
> >> > > > > > >> > >>
> >> > > > > > >> >
> >> > > > > > >> >
> >> > > > >
> >> ---------------------------------------------------------------------
> >> > > > > > >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.
> apache.org
> >> > > > > > >> > For additional commands, e-mail:
> >> dev-help@cordova.apache.org
> >> > > > > > >> >
> >> > > > > > >> >
> >> > > > > > >>
> >> > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > > > --
> >> > > > > Carlos Santana
> >> > > > > <cs...@gmail.com>
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Andrew Grieve <ag...@chromium.org>.
CB-8684 is now merged and I've updated the targetSdk (and made a couple
other changes).
I'll start the release process in the morning as long as there no
objections.
On Tue, Apr 7, 2015 at 2:20 PM, Andrew Grieve <ag...@chromium.org> wrote:
> I'll start on it once CB-8684 lands (Tony - assuming you'll have this done
> shortly and would prefer it lands?)
>
> On Tue, Apr 7, 2015 at 1:33 PM, Jesse <pu...@gmail.com> wrote:
>
>> Sweet!
>>
>> @purplecabbage
>> risingj.com
>>
>> On Tue, Apr 7, 2015 at 8:35 AM, Andrew Grieve <ag...@chromium.org>
>> wrote:
>>
>> > Let's do it!
>> >
>> > On Mon, Apr 6, 2015 at 7:33 PM, Joe Bowser <bo...@gmail.com> wrote:
>> >
>> > > So, I think we should put off the embedder's guide until after the
>> > > release. A lot of it has changed, and since we're still technically
>> > > obligated to support the 3.x release tree for six months, that should
>> buy
>> > > us some time to figure out how that is going to work. Getting
>> Cordova to
>> > > work with a vanilla Android Studio project is a non-trivial task.
>> > >
>> > > Given that everything else appears to be done, should we start voting
>> on
>> > an
>> > > RC for this? What do people think?
>> > >
>> > >
>> > >
>> > > On Thu, Mar 19, 2015 at 10:31 AM Andrew Grieve <ag...@chromium.org>
>> > > wrote:
>> > >
>> > > > Here's issues:
>> > > > https://issues.apache.org/jira/browse/CB-8715 (docs)
>> > > > https://issues.apache.org/jira/browse/CB-8716 (whitelist)
>> > > > https://issues.apache.org/jira/browse/CB-8717 (write
>> RELEASENOTES.md)
>> > > >
>> > > > On Tue, Mar 17, 2015 at 10:15 AM, Carlos Santana <
>> csantana23@gmail.com
>> > >
>> > > > wrote:
>> > > >
>> > > > > I would say let's start RC testing and voting, But not pin the
>> > version
>> > > in
>> > > > > Cordova CLI until the tasks that Andrew mentioned are done.
>> > > > > Andrew can you create the JIRA Items for the tasks that need to be
>> > > done.
>> > > > I
>> > > > > thought there was a discussion about creating JIRA Items to help
>> > track
>> > > > and
>> > > > > know what's left for release something.
>> > > > >
>> > > > > - upgrade guide,
>> > > > > - publishing whitelist plugins,
>> > > > > - and making it so that the default project template includes
>> <plugin
>> > > > > name="cordova-plugin-whitelist" />)
>> > > > >
>> > > > >
>> > > > > On Mon, Mar 16, 2015 at 11:21 PM, Ian Clelland <
>> > iclelland@chromium.org
>> > > >
>> > > > > wrote:
>> > > > >
>> > > > > > We'll probably need at least an RC for the whitelist plugin, if
>> > not a
>> > > > > vote,
>> > > > > > to be able to vote on this.
>> > > > > >
>> > > > > > Or can we just include instructions like "Use
>> > > > > > cordova-plugin-whitelist@f70b1bc for testing" while we start
>> the
>> > > > > official
>> > > > > > release process for the plugins?
>> > > > > >
>> > > > > > On Mon, Mar 16, 2015 at 11:17 PM, Ian Clelland <
>> > > iclelland@chromium.org
>> > > > >
>> > > > > > wrote:
>> > > > > >
>> > > > > > > +1 -- Let's get this out the door :)
>> > > > > > > I'll see what I can get done to move it in that direction.
>> > > > > > >
>> > > > > > > On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <
>> > > agrieve@chromium.org
>> > > > >
>> > > > > > > wrote:
>> > > > > > >
>> > > > > > >> Everything's ready afaik (minus upgrade guide, publishing
>> > > whitelist
>> > > > > > >> plugins, and making it so that the default project template
>> > > includes
>> > > > > > >> <plugin name="cordova-plugin-whitelist" />). Maybe let's do
>> a RC
>> > > > while
>> > > > > > we
>> > > > > > >> wait on these things being finished up?
>> > > > > > >>
>> > > > > > >> If anyone wants to take on any of these tasks, that would be
>> > > > awesome.
>> > > > > > >>
>> > > > > > >> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <sh...@gmail.com>
>> > > wrote:
>> > > > > > >>
>> > > > > > >> > +1 for vote thread, let's get this thing out so people
>> (that
>> > are
>> > > > not
>> > > > > > >> > us) can test...
>> > > > > > >> >
>> > > > > > >> >
>> > > > > > >> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <
>> > bowserj@gmail.com>
>> > > > > > wrote:
>> > > > > > >> > > OK, this is a three month old thread, and we're waiting
>> on a
>> > > > > > >> discussion
>> > > > > > >> > > before we release something? I really think we should go
>> to
>> > a
>> > > > vote
>> > > > > > >> thread
>> > > > > > >> > > now that we have a legacy whitelist plugin and a new
>> style
>> > > > > whitelist
>> > > > > > >> > > plugin. We shouldn't keep constantly delaying this
>> release
>> > > > > because
>> > > > > > of
>> > > > > > >> > > what's happening on other platforms, especially since we
>> > > already
>> > > > > > >> > pluginized
>> > > > > > >> > > the whitelist.
>> > > > > > >> > >
>> > > > > > >> > > Can we please release soon?
>> > > > > > >> > >
>> > > > > > >> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil Khandelwal <
>> > > > > > >> > nikhilkh@microsoft.com>
>> > > > > > >> > > wrote:
>> > > > > > >> > >
>> > > > > > >> > >> I know we discussed a couple of approaches implementing
>> the
>> > > > > default
>> > > > > > >> > >> whitelist policy for Android/iOS - either every app
>> would
>> > be
>> > > > > > >> required to
>> > > > > > >> > >> include the whitelist plugin or have it have smart
>> defaults
>> > > in
>> > > > > the
>> > > > > > >> > platform
>> > > > > > >> > >> implementation and the plugin being able to override
>> them.
>> > > > > > >> > >>
>> > > > > > >> > >> I don’t think that thread closed with any conclusions.
>> > > > > > >> > >>
>> > > > > > >> > >> Thanks,
>> > > > > > >> > >> Nikhil
>> > > > > > >> > >>
>> > > > > > >> > >>
>> > > > > > >> > >> -----Original Message-----
>> > > > > > >> > >> From: Joe Bowser [mailto:bowserj@gmail.com]
>> > > > > > >> > >> Sent: Thursday, March 12, 2015 11:23 AM
>> > > > > > >> > >> To: dev
>> > > > > > >> > >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
>> > > > > > >> > >>
>> > > > > > >> > >> OK, so right now it's just docs? How soon can we get a
>> VOTE
>> > > > > thread
>> > > > > > >> > started
>> > > > > > >> > >> for 4.0.0?
>> > > > > > >> > >>
>> > > > > > >> > >> On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <
>> > > > > > agrieve@chromium.org>
>> > > > > > >> > >> wrote:
>> > > > > > >> > >>
>> > > > > > >> > >> > mobilespec is now working again... Took longer than I
>> > would
>> > > > > have
>> > > > > > >> > >> > liked, but did you know that on Android FileReader
>> > triggers
>> > > > > > >> > >> > shouldInterceptRequest() with Blob URLs!?
>> > > > > > >> > >> >
>> > > > > > >> > >> > Separate thread is already happening re: whitelists,
>> so
>> > > once
>> > > > > > that's
>> > > > > > >> > >> > figured out, it's just docs afaict.
>> > > > > > >> > >> >
>> > > > > > >> > >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian Clelland <
>> > > > > > >> iclelland@chromium.org
>> > > > > > >> > >
>> > > > > > >> > >> > wrote:
>> > > > > > >> > >> >
>> > > > > > >> > >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <
>> > > > > purplecabbage@gmail.com
>> > > > > > >
>> > > > > > >> > wrote:
>> > > > > > >> > >> > >
>> > > > > > >> > >> > > > We should start a new whitelist plugin related
>> > thread.
>> > > > > > >> > >> > > >
>> > > > > > >> > >> > > > Why is a plugin blocking a release? Default (aka
>> > > > > no-plugin)
>> > > > > > >> > >> > > > behavior should be to allow all network requests
>> > > > shouldn't
>> > > > > > it?
>> > > > > > >> > >> > >
>> > > > > > >> > >> > >
>> > > > > > >> > >> > > Well, that just might be a blacklist then :)
>> > > > > > >> > >> > >
>> > > > > > >> > >> > >
>> > > > > > >> > >> > > > This thread is a
>> > > > > > >> > >> > > > month long, and not the first discussion of 4.0.0
>> for
>> > > > > > Android.
>> > > > > > >> > >> > > >
>> > > > > > >> > >> > >
>> > > > > > >> > >> > > Seriously, though -- the whitelist discussion is
>> much
>> > > > longer
>> > > > > > than
>> > > > > > >> > >> > > that,
>> > > > > > >> > >> > and
>> > > > > > >> > >> > > this isn't the first time that the default
>> > > > no-network-access
>> > > > > > >> policy
>> > > > > > >> > >> > > has been brought up:
>> > > > > > >> > >> > >
>> > > > > > >> > >> > > (Here's the first question, from *July*:
>> > > > > > >> > >> > > http://markmail.org/message/t4vj4saisem2mcgw
>> > > > > > >> > >> > > Here's where I mentioned what the implemented policy
>> > was:
>> > > > > > >> > >> > > http://markmail.org/message/s4necfnh4hnblpjm
>> > > > > > >> > >> > > And in another discussion:
>> > > > > > >> > >> > > http://markmail.org/message/ap7syhqysizmsvrz)
>> > > > > > >> > >> > >
>> > > > > > >> > >> > > If we want to reconsider that decision, then we
>> should
>> > > > > > certainly
>> > > > > > >> do
>> > > > > > >> > >> > > so before we cut a release. I think it would be a
>> real
>> > > > > problem
>> > > > > > to
>> > > > > > >> > >> > > change it afterwards, so let's get it right.
>> > > > > > >> > >> > >
>> > > > > > >> > >> > > Also, it's not the plugin itself that's blocking the
>> > > > release,
>> > > > > > >> it's
>> > > > > > >> > >> > > us making sure that we've implemented the core hooks
>> > > > > correctly
>> > > > > > so
>> > > > > > >> > >> > > that the plugin can actually do its job, and that
>> > people
>> > > > who
>> > > > > > >> don't
>> > > > > > >> > >> > > want that particular plugin can make a better one.
>> > > > > > >> > >> > >
>> > > > > > >> > >> > > (It is also an issue that a plugin, required for
>> > > > > > cordova-android
>> > > > > > >> > >> > > 4.0.0, breaks apps which are also building for
>> > > cordova-ios
>> > > > > > 3.8.0.
>> > > > > > >> > >> > > I'll take a
>> > > > > > >> > >> > look
>> > > > > > >> > >> > > at that, and either remove the ios-native portions
>> of
>> > the
>> > > > > > >> whitelist
>> > > > > > >> > >> > plugin,
>> > > > > > >> > >> > > or neuter it so that it doesn't interfere with an
>> ios
>> > app
>> > > > if
>> > > > > > it's
>> > > > > > >> > >> > > not on the unplug-whitelist branch of that repo.)
>> > > > > > >> > >> > >
>> > > > > > >> > >> > > Ian
>> > > > > > >> > >> > >
>> > > > > > >> > >> > >
>> > > > > > >> > >> > > > @purplecabbage
>> > > > > > >> > >> > > > risingj.com
>> > > > > > >> > >> > > >
>> > > > > > >> > >> > > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <
>> > > > shazron@gmail.com
>> > > > > >
>> > > > > > >> > wrote:
>> > > > > > >> > >> > > >
>> > > > > > >> > >> > > > > legacy-whitelist-plugin should be fixed so that
>> it
>> > > > > compiles
>> > > > > > >> on
>> > > > > > >> > >> > > > > cordova-ios@3.8.0. It shouldn't be a problem to
>> > fix
>> > > > this
>> > > > > > at
>> > > > > > >> > >> > > > > compile
>> > > > > > >> > >> > or
>> > > > > > >> > >> > > > > run-time (whichever is applicable here related
>> to
>> > the
>> > > > > > compile
>> > > > > > >> > >> > > > > error)
>> > > > > > >> > >> > > > >
>> > > > > > >> > >> > > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue
>> > > > > > >> > >> > > > > <dv...@gmail.com>
>> > > > > > >> > >> > > > wrote:
>> > > > > > >> > >> > > > > > On 2 March 2015 at 13:37, Joe Bowser <
>> > > > > bowserj@gmail.com>
>> > > > > > >> > wrote:
>> > > > > > >> > >> > > > > >> So, right now the whitelist changes are
>> what's
>> > > > holding
>> > > > > > up
>> > > > > > >> the
>> > > > > > >> > >> > 4.0.0
>> > > > > > >> > >> > > > > release
>> > > > > > >> > >> > > > > >> now? Is this really the only thing that's
>> > holding
>> > > > up
>> > > > > > this
>> > > > > > >> > >> > release?
>> > > > > > >> > >> > > > > >>
>> > > > > > >> > >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM Andrew
>> Grieve <
>> > > > > > >> > >> > > agrieve@chromium.org>
>> > > > > > >> > >> > > > > wrote:
>> > > > > > >> > >> > > > > >>
>> > > > > > >> > >> > > > > >>> I think we'll also need to finish with the
>> > > > whitelist
>> > > > > > >> changes
>> > > > > > >> > >> > > > > >>> &
>> > > > > > >> > >> > have
>> > > > > > >> > >> > > > > both
>> > > > > > >> > >> > > > > >>> the legacy and new-way whitelist plugins
>> > released
>> > > > > > before
>> > > > > > >> we
>> > > > > > >> > >> > > > > >>> can
>> > > > > > >> > >> > do
>> > > > > > >> > >> > > a
>> > > > > > >> > >> > > > > 4.0.0
>> > > > > > >> > >> > > > > >>> release (otherwise you wouldn't be able to
>> > write
>> > > an
>> > > > > app
>> > > > > > >> that
>> > > > > > >> > >> > > > > >>> hits
>> > > > > > >> > >> > > the
>> > > > > > >> > >> > > > > >>> network)
>> > > > > > >> > >> > > > > >>>
>> > > > > > >> > >> > > > > >
>> > > > > > >> > >> > > > > > Just FYI, the whitelist stuff is proving to
>> be a
>> > > bit
>> > > > > of a
>> > > > > > >> pain
>> > > > > > >> > >> > point.
>> > > > > > >> > >> > > > > > I'm using cordova-android@master, and need to
>> > > > install
>> > > > > > the
>> > > > > > >> > >> > > > > > legacy-whitelist plugin in order to make
>> network
>> > > > > > requests.
>> > > > > > >> > >> > > > > > Once the plugin is installed, everything
>> seems to
>> > > > work.
>> > > > > > >> > >> > > > > >
>> > > > > > >> > >> > > > > > The problem is that the legacy-whitelist
>> plugin
>> > > > > generates
>> > > > > > >> > >> > > > > > compile errors with cordova-ios@3.8.0, so
>> now I
>> > > > can't
>> > > > > > just
>> > > > > > >> > run
>> > > > > > >> > >> > > > > > `cordova build`, I need to split the
>> platforms up
>> > > and
>> > > > > > >> > >> > > > > > install/uninstall the plugin in between. If
>> > someone
>> > > > > > makes a
>> > > > > > >> > >> > > > > > dev build for Android and forgets the plugin,
>> it
>> > > will
>> > > > > > >> appear
>> > > > > > >> > >> > > > > > to build successfully but not actually
>> function
>> > > > > properly
>> > > > > > >> due
>> > > > > > >> > to
>> > > > > > >> > >> the whitelist.
>> > > > > > >> > >> > > > > >
>> > > > > > >> > >> > > > > > I know, this is all pre-release, so pain is
>> > > somewhat
>> > > > > > >> expected
>> > > > > > >> > >> > > > > > right now. I'm worried about the case where
>> > > > > > >> > >> > > > > > cordova-android@4.0.0 is released and
>> > > > > cordova-ios@3.8.0
>> > > > > > is
>> > > > > > >> > >> > > > > > still current, and how people
>> > > > > > >> > >> > can
>> > > > > > >> > >> > > > > > avoid whitelist breakage there.
>> > > > > > >> > >> > > > > >
>> > > > > > >> > >> > > > > >
>> > > > > > >> ------------------------------------------------------------
>> > > > > > >> > >> > ---------
>> > > > > > >> > >> > > > > > To unsubscribe, e-mail:
>> > > > > > dev-unsubscribe@cordova.apache.org
>> > > > > > >> > >> > > > > > For additional commands, e-mail:
>> > > > > > >> dev-help@cordova.apache.org
>> > > > > > >> > >> > > > > >
>> > > > > > >> > >> > > > >
>> > > > > > >> > >> > > > >
>> > > > > > ------------------------------------------------------------
>> > > > > > >> > >> > ---------
>> > > > > > >> > >> > > > > To unsubscribe, e-mail:
>> > > > > dev-unsubscribe@cordova.apache.org
>> > > > > > >> > >> > > > > For additional commands, e-mail:
>> > > > > > dev-help@cordova.apache.org
>> > > > > > >> > >> > > > >
>> > > > > > >> > >> > > > >
>> > > > > > >> > >> > > >
>> > > > > > >> > >> > >
>> > > > > > >> > >> >
>> > > > > > >> > >>
>> > > > > > >> >
>> > > > > > >> >
>> > > > >
>> ---------------------------------------------------------------------
>> > > > > > >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> > > > > > >> > For additional commands, e-mail:
>> dev-help@cordova.apache.org
>> > > > > > >> >
>> > > > > > >> >
>> > > > > > >>
>> > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > > --
>> > > > > Carlos Santana
>> > > > > <cs...@gmail.com>
>> > > > >
>> > > >
>> > >
>> >
>>
>
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Andrew Grieve <ag...@chromium.org>.
I'll start on it once CB-8684 lands (Tony - assuming you'll have this done
shortly and would prefer it lands?)
On Tue, Apr 7, 2015 at 1:33 PM, Jesse <pu...@gmail.com> wrote:
> Sweet!
>
> @purplecabbage
> risingj.com
>
> On Tue, Apr 7, 2015 at 8:35 AM, Andrew Grieve <ag...@chromium.org>
> wrote:
>
> > Let's do it!
> >
> > On Mon, Apr 6, 2015 at 7:33 PM, Joe Bowser <bo...@gmail.com> wrote:
> >
> > > So, I think we should put off the embedder's guide until after the
> > > release. A lot of it has changed, and since we're still technically
> > > obligated to support the 3.x release tree for six months, that should
> buy
> > > us some time to figure out how that is going to work. Getting Cordova
> to
> > > work with a vanilla Android Studio project is a non-trivial task.
> > >
> > > Given that everything else appears to be done, should we start voting
> on
> > an
> > > RC for this? What do people think?
> > >
> > >
> > >
> > > On Thu, Mar 19, 2015 at 10:31 AM Andrew Grieve <ag...@chromium.org>
> > > wrote:
> > >
> > > > Here's issues:
> > > > https://issues.apache.org/jira/browse/CB-8715 (docs)
> > > > https://issues.apache.org/jira/browse/CB-8716 (whitelist)
> > > > https://issues.apache.org/jira/browse/CB-8717 (write
> RELEASENOTES.md)
> > > >
> > > > On Tue, Mar 17, 2015 at 10:15 AM, Carlos Santana <
> csantana23@gmail.com
> > >
> > > > wrote:
> > > >
> > > > > I would say let's start RC testing and voting, But not pin the
> > version
> > > in
> > > > > Cordova CLI until the tasks that Andrew mentioned are done.
> > > > > Andrew can you create the JIRA Items for the tasks that need to be
> > > done.
> > > > I
> > > > > thought there was a discussion about creating JIRA Items to help
> > track
> > > > and
> > > > > know what's left for release something.
> > > > >
> > > > > - upgrade guide,
> > > > > - publishing whitelist plugins,
> > > > > - and making it so that the default project template includes
> <plugin
> > > > > name="cordova-plugin-whitelist" />)
> > > > >
> > > > >
> > > > > On Mon, Mar 16, 2015 at 11:21 PM, Ian Clelland <
> > iclelland@chromium.org
> > > >
> > > > > wrote:
> > > > >
> > > > > > We'll probably need at least an RC for the whitelist plugin, if
> > not a
> > > > > vote,
> > > > > > to be able to vote on this.
> > > > > >
> > > > > > Or can we just include instructions like "Use
> > > > > > cordova-plugin-whitelist@f70b1bc for testing" while we start the
> > > > > official
> > > > > > release process for the plugins?
> > > > > >
> > > > > > On Mon, Mar 16, 2015 at 11:17 PM, Ian Clelland <
> > > iclelland@chromium.org
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > +1 -- Let's get this out the door :)
> > > > > > > I'll see what I can get done to move it in that direction.
> > > > > > >
> > > > > > > On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <
> > > agrieve@chromium.org
> > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > >> Everything's ready afaik (minus upgrade guide, publishing
> > > whitelist
> > > > > > >> plugins, and making it so that the default project template
> > > includes
> > > > > > >> <plugin name="cordova-plugin-whitelist" />). Maybe let's do a
> RC
> > > > while
> > > > > > we
> > > > > > >> wait on these things being finished up?
> > > > > > >>
> > > > > > >> If anyone wants to take on any of these tasks, that would be
> > > > awesome.
> > > > > > >>
> > > > > > >> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <sh...@gmail.com>
> > > wrote:
> > > > > > >>
> > > > > > >> > +1 for vote thread, let's get this thing out so people (that
> > are
> > > > not
> > > > > > >> > us) can test...
> > > > > > >> >
> > > > > > >> >
> > > > > > >> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <
> > bowserj@gmail.com>
> > > > > > wrote:
> > > > > > >> > > OK, this is a three month old thread, and we're waiting
> on a
> > > > > > >> discussion
> > > > > > >> > > before we release something? I really think we should go
> to
> > a
> > > > vote
> > > > > > >> thread
> > > > > > >> > > now that we have a legacy whitelist plugin and a new style
> > > > > whitelist
> > > > > > >> > > plugin. We shouldn't keep constantly delaying this
> release
> > > > > because
> > > > > > of
> > > > > > >> > > what's happening on other platforms, especially since we
> > > already
> > > > > > >> > pluginized
> > > > > > >> > > the whitelist.
> > > > > > >> > >
> > > > > > >> > > Can we please release soon?
> > > > > > >> > >
> > > > > > >> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil Khandelwal <
> > > > > > >> > nikhilkh@microsoft.com>
> > > > > > >> > > wrote:
> > > > > > >> > >
> > > > > > >> > >> I know we discussed a couple of approaches implementing
> the
> > > > > default
> > > > > > >> > >> whitelist policy for Android/iOS - either every app would
> > be
> > > > > > >> required to
> > > > > > >> > >> include the whitelist plugin or have it have smart
> defaults
> > > in
> > > > > the
> > > > > > >> > platform
> > > > > > >> > >> implementation and the plugin being able to override
> them.
> > > > > > >> > >>
> > > > > > >> > >> I don’t think that thread closed with any conclusions.
> > > > > > >> > >>
> > > > > > >> > >> Thanks,
> > > > > > >> > >> Nikhil
> > > > > > >> > >>
> > > > > > >> > >>
> > > > > > >> > >> -----Original Message-----
> > > > > > >> > >> From: Joe Bowser [mailto:bowserj@gmail.com]
> > > > > > >> > >> Sent: Thursday, March 12, 2015 11:23 AM
> > > > > > >> > >> To: dev
> > > > > > >> > >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > > > > > >> > >>
> > > > > > >> > >> OK, so right now it's just docs? How soon can we get a
> VOTE
> > > > > thread
> > > > > > >> > started
> > > > > > >> > >> for 4.0.0?
> > > > > > >> > >>
> > > > > > >> > >> On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <
> > > > > > agrieve@chromium.org>
> > > > > > >> > >> wrote:
> > > > > > >> > >>
> > > > > > >> > >> > mobilespec is now working again... Took longer than I
> > would
> > > > > have
> > > > > > >> > >> > liked, but did you know that on Android FileReader
> > triggers
> > > > > > >> > >> > shouldInterceptRequest() with Blob URLs!?
> > > > > > >> > >> >
> > > > > > >> > >> > Separate thread is already happening re: whitelists, so
> > > once
> > > > > > that's
> > > > > > >> > >> > figured out, it's just docs afaict.
> > > > > > >> > >> >
> > > > > > >> > >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian Clelland <
> > > > > > >> iclelland@chromium.org
> > > > > > >> > >
> > > > > > >> > >> > wrote:
> > > > > > >> > >> >
> > > > > > >> > >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <
> > > > > purplecabbage@gmail.com
> > > > > > >
> > > > > > >> > wrote:
> > > > > > >> > >> > >
> > > > > > >> > >> > > > We should start a new whitelist plugin related
> > thread.
> > > > > > >> > >> > > >
> > > > > > >> > >> > > > Why is a plugin blocking a release? Default (aka
> > > > > no-plugin)
> > > > > > >> > >> > > > behavior should be to allow all network requests
> > > > shouldn't
> > > > > > it?
> > > > > > >> > >> > >
> > > > > > >> > >> > >
> > > > > > >> > >> > > Well, that just might be a blacklist then :)
> > > > > > >> > >> > >
> > > > > > >> > >> > >
> > > > > > >> > >> > > > This thread is a
> > > > > > >> > >> > > > month long, and not the first discussion of 4.0.0
> for
> > > > > > Android.
> > > > > > >> > >> > > >
> > > > > > >> > >> > >
> > > > > > >> > >> > > Seriously, though -- the whitelist discussion is much
> > > > longer
> > > > > > than
> > > > > > >> > >> > > that,
> > > > > > >> > >> > and
> > > > > > >> > >> > > this isn't the first time that the default
> > > > no-network-access
> > > > > > >> policy
> > > > > > >> > >> > > has been brought up:
> > > > > > >> > >> > >
> > > > > > >> > >> > > (Here's the first question, from *July*:
> > > > > > >> > >> > > http://markmail.org/message/t4vj4saisem2mcgw
> > > > > > >> > >> > > Here's where I mentioned what the implemented policy
> > was:
> > > > > > >> > >> > > http://markmail.org/message/s4necfnh4hnblpjm
> > > > > > >> > >> > > And in another discussion:
> > > > > > >> > >> > > http://markmail.org/message/ap7syhqysizmsvrz)
> > > > > > >> > >> > >
> > > > > > >> > >> > > If we want to reconsider that decision, then we
> should
> > > > > > certainly
> > > > > > >> do
> > > > > > >> > >> > > so before we cut a release. I think it would be a
> real
> > > > > problem
> > > > > > to
> > > > > > >> > >> > > change it afterwards, so let's get it right.
> > > > > > >> > >> > >
> > > > > > >> > >> > > Also, it's not the plugin itself that's blocking the
> > > > release,
> > > > > > >> it's
> > > > > > >> > >> > > us making sure that we've implemented the core hooks
> > > > > correctly
> > > > > > so
> > > > > > >> > >> > > that the plugin can actually do its job, and that
> > people
> > > > who
> > > > > > >> don't
> > > > > > >> > >> > > want that particular plugin can make a better one.
> > > > > > >> > >> > >
> > > > > > >> > >> > > (It is also an issue that a plugin, required for
> > > > > > cordova-android
> > > > > > >> > >> > > 4.0.0, breaks apps which are also building for
> > > cordova-ios
> > > > > > 3.8.0.
> > > > > > >> > >> > > I'll take a
> > > > > > >> > >> > look
> > > > > > >> > >> > > at that, and either remove the ios-native portions of
> > the
> > > > > > >> whitelist
> > > > > > >> > >> > plugin,
> > > > > > >> > >> > > or neuter it so that it doesn't interfere with an ios
> > app
> > > > if
> > > > > > it's
> > > > > > >> > >> > > not on the unplug-whitelist branch of that repo.)
> > > > > > >> > >> > >
> > > > > > >> > >> > > Ian
> > > > > > >> > >> > >
> > > > > > >> > >> > >
> > > > > > >> > >> > > > @purplecabbage
> > > > > > >> > >> > > > risingj.com
> > > > > > >> > >> > > >
> > > > > > >> > >> > > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <
> > > > shazron@gmail.com
> > > > > >
> > > > > > >> > wrote:
> > > > > > >> > >> > > >
> > > > > > >> > >> > > > > legacy-whitelist-plugin should be fixed so that
> it
> > > > > compiles
> > > > > > >> on
> > > > > > >> > >> > > > > cordova-ios@3.8.0. It shouldn't be a problem to
> > fix
> > > > this
> > > > > > at
> > > > > > >> > >> > > > > compile
> > > > > > >> > >> > or
> > > > > > >> > >> > > > > run-time (whichever is applicable here related to
> > the
> > > > > > compile
> > > > > > >> > >> > > > > error)
> > > > > > >> > >> > > > >
> > > > > > >> > >> > > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue
> > > > > > >> > >> > > > > <dv...@gmail.com>
> > > > > > >> > >> > > > wrote:
> > > > > > >> > >> > > > > > On 2 March 2015 at 13:37, Joe Bowser <
> > > > > bowserj@gmail.com>
> > > > > > >> > wrote:
> > > > > > >> > >> > > > > >> So, right now the whitelist changes are what's
> > > > holding
> > > > > > up
> > > > > > >> the
> > > > > > >> > >> > 4.0.0
> > > > > > >> > >> > > > > release
> > > > > > >> > >> > > > > >> now? Is this really the only thing that's
> > holding
> > > > up
> > > > > > this
> > > > > > >> > >> > release?
> > > > > > >> > >> > > > > >>
> > > > > > >> > >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM Andrew
> Grieve <
> > > > > > >> > >> > > agrieve@chromium.org>
> > > > > > >> > >> > > > > wrote:
> > > > > > >> > >> > > > > >>
> > > > > > >> > >> > > > > >>> I think we'll also need to finish with the
> > > > whitelist
> > > > > > >> changes
> > > > > > >> > >> > > > > >>> &
> > > > > > >> > >> > have
> > > > > > >> > >> > > > > both
> > > > > > >> > >> > > > > >>> the legacy and new-way whitelist plugins
> > released
> > > > > > before
> > > > > > >> we
> > > > > > >> > >> > > > > >>> can
> > > > > > >> > >> > do
> > > > > > >> > >> > > a
> > > > > > >> > >> > > > > 4.0.0
> > > > > > >> > >> > > > > >>> release (otherwise you wouldn't be able to
> > write
> > > an
> > > > > app
> > > > > > >> that
> > > > > > >> > >> > > > > >>> hits
> > > > > > >> > >> > > the
> > > > > > >> > >> > > > > >>> network)
> > > > > > >> > >> > > > > >>>
> > > > > > >> > >> > > > > >
> > > > > > >> > >> > > > > > Just FYI, the whitelist stuff is proving to be
> a
> > > bit
> > > > > of a
> > > > > > >> pain
> > > > > > >> > >> > point.
> > > > > > >> > >> > > > > > I'm using cordova-android@master, and need to
> > > > install
> > > > > > the
> > > > > > >> > >> > > > > > legacy-whitelist plugin in order to make
> network
> > > > > > requests.
> > > > > > >> > >> > > > > > Once the plugin is installed, everything seems
> to
> > > > work.
> > > > > > >> > >> > > > > >
> > > > > > >> > >> > > > > > The problem is that the legacy-whitelist plugin
> > > > > generates
> > > > > > >> > >> > > > > > compile errors with cordova-ios@3.8.0, so now
> I
> > > > can't
> > > > > > just
> > > > > > >> > run
> > > > > > >> > >> > > > > > `cordova build`, I need to split the platforms
> up
> > > and
> > > > > > >> > >> > > > > > install/uninstall the plugin in between. If
> > someone
> > > > > > makes a
> > > > > > >> > >> > > > > > dev build for Android and forgets the plugin,
> it
> > > will
> > > > > > >> appear
> > > > > > >> > >> > > > > > to build successfully but not actually function
> > > > > properly
> > > > > > >> due
> > > > > > >> > to
> > > > > > >> > >> the whitelist.
> > > > > > >> > >> > > > > >
> > > > > > >> > >> > > > > > I know, this is all pre-release, so pain is
> > > somewhat
> > > > > > >> expected
> > > > > > >> > >> > > > > > right now. I'm worried about the case where
> > > > > > >> > >> > > > > > cordova-android@4.0.0 is released and
> > > > > cordova-ios@3.8.0
> > > > > > is
> > > > > > >> > >> > > > > > still current, and how people
> > > > > > >> > >> > can
> > > > > > >> > >> > > > > > avoid whitelist breakage there.
> > > > > > >> > >> > > > > >
> > > > > > >> > >> > > > > >
> > > > > > >> ------------------------------------------------------------
> > > > > > >> > >> > ---------
> > > > > > >> > >> > > > > > To unsubscribe, e-mail:
> > > > > > dev-unsubscribe@cordova.apache.org
> > > > > > >> > >> > > > > > For additional commands, e-mail:
> > > > > > >> dev-help@cordova.apache.org
> > > > > > >> > >> > > > > >
> > > > > > >> > >> > > > >
> > > > > > >> > >> > > > >
> > > > > > ------------------------------------------------------------
> > > > > > >> > >> > ---------
> > > > > > >> > >> > > > > To unsubscribe, e-mail:
> > > > > dev-unsubscribe@cordova.apache.org
> > > > > > >> > >> > > > > For additional commands, e-mail:
> > > > > > dev-help@cordova.apache.org
> > > > > > >> > >> > > > >
> > > > > > >> > >> > > > >
> > > > > > >> > >> > > >
> > > > > > >> > >> > >
> > > > > > >> > >> >
> > > > > > >> > >>
> > > > > > >> >
> > > > > > >> >
> > > > >
> ---------------------------------------------------------------------
> > > > > > >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > > > >> > For additional commands, e-mail:
> dev-help@cordova.apache.org
> > > > > > >> >
> > > > > > >> >
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Carlos Santana
> > > > > <cs...@gmail.com>
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Jesse <pu...@gmail.com>.
Sweet!
@purplecabbage
risingj.com
On Tue, Apr 7, 2015 at 8:35 AM, Andrew Grieve <ag...@chromium.org> wrote:
> Let's do it!
>
> On Mon, Apr 6, 2015 at 7:33 PM, Joe Bowser <bo...@gmail.com> wrote:
>
> > So, I think we should put off the embedder's guide until after the
> > release. A lot of it has changed, and since we're still technically
> > obligated to support the 3.x release tree for six months, that should buy
> > us some time to figure out how that is going to work. Getting Cordova to
> > work with a vanilla Android Studio project is a non-trivial task.
> >
> > Given that everything else appears to be done, should we start voting on
> an
> > RC for this? What do people think?
> >
> >
> >
> > On Thu, Mar 19, 2015 at 10:31 AM Andrew Grieve <ag...@chromium.org>
> > wrote:
> >
> > > Here's issues:
> > > https://issues.apache.org/jira/browse/CB-8715 (docs)
> > > https://issues.apache.org/jira/browse/CB-8716 (whitelist)
> > > https://issues.apache.org/jira/browse/CB-8717 (write RELEASENOTES.md)
> > >
> > > On Tue, Mar 17, 2015 at 10:15 AM, Carlos Santana <csantana23@gmail.com
> >
> > > wrote:
> > >
> > > > I would say let's start RC testing and voting, But not pin the
> version
> > in
> > > > Cordova CLI until the tasks that Andrew mentioned are done.
> > > > Andrew can you create the JIRA Items for the tasks that need to be
> > done.
> > > I
> > > > thought there was a discussion about creating JIRA Items to help
> track
> > > and
> > > > know what's left for release something.
> > > >
> > > > - upgrade guide,
> > > > - publishing whitelist plugins,
> > > > - and making it so that the default project template includes <plugin
> > > > name="cordova-plugin-whitelist" />)
> > > >
> > > >
> > > > On Mon, Mar 16, 2015 at 11:21 PM, Ian Clelland <
> iclelland@chromium.org
> > >
> > > > wrote:
> > > >
> > > > > We'll probably need at least an RC for the whitelist plugin, if
> not a
> > > > vote,
> > > > > to be able to vote on this.
> > > > >
> > > > > Or can we just include instructions like "Use
> > > > > cordova-plugin-whitelist@f70b1bc for testing" while we start the
> > > > official
> > > > > release process for the plugins?
> > > > >
> > > > > On Mon, Mar 16, 2015 at 11:17 PM, Ian Clelland <
> > iclelland@chromium.org
> > > >
> > > > > wrote:
> > > > >
> > > > > > +1 -- Let's get this out the door :)
> > > > > > I'll see what I can get done to move it in that direction.
> > > > > >
> > > > > > On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <
> > agrieve@chromium.org
> > > >
> > > > > > wrote:
> > > > > >
> > > > > >> Everything's ready afaik (minus upgrade guide, publishing
> > whitelist
> > > > > >> plugins, and making it so that the default project template
> > includes
> > > > > >> <plugin name="cordova-plugin-whitelist" />). Maybe let's do a RC
> > > while
> > > > > we
> > > > > >> wait on these things being finished up?
> > > > > >>
> > > > > >> If anyone wants to take on any of these tasks, that would be
> > > awesome.
> > > > > >>
> > > > > >> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <sh...@gmail.com>
> > wrote:
> > > > > >>
> > > > > >> > +1 for vote thread, let's get this thing out so people (that
> are
> > > not
> > > > > >> > us) can test...
> > > > > >> >
> > > > > >> >
> > > > > >> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <
> bowserj@gmail.com>
> > > > > wrote:
> > > > > >> > > OK, this is a three month old thread, and we're waiting on a
> > > > > >> discussion
> > > > > >> > > before we release something? I really think we should go to
> a
> > > vote
> > > > > >> thread
> > > > > >> > > now that we have a legacy whitelist plugin and a new style
> > > > whitelist
> > > > > >> > > plugin. We shouldn't keep constantly delaying this release
> > > > because
> > > > > of
> > > > > >> > > what's happening on other platforms, especially since we
> > already
> > > > > >> > pluginized
> > > > > >> > > the whitelist.
> > > > > >> > >
> > > > > >> > > Can we please release soon?
> > > > > >> > >
> > > > > >> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil Khandelwal <
> > > > > >> > nikhilkh@microsoft.com>
> > > > > >> > > wrote:
> > > > > >> > >
> > > > > >> > >> I know we discussed a couple of approaches implementing the
> > > > default
> > > > > >> > >> whitelist policy for Android/iOS - either every app would
> be
> > > > > >> required to
> > > > > >> > >> include the whitelist plugin or have it have smart defaults
> > in
> > > > the
> > > > > >> > platform
> > > > > >> > >> implementation and the plugin being able to override them.
> > > > > >> > >>
> > > > > >> > >> I don’t think that thread closed with any conclusions.
> > > > > >> > >>
> > > > > >> > >> Thanks,
> > > > > >> > >> Nikhil
> > > > > >> > >>
> > > > > >> > >>
> > > > > >> > >> -----Original Message-----
> > > > > >> > >> From: Joe Bowser [mailto:bowserj@gmail.com]
> > > > > >> > >> Sent: Thursday, March 12, 2015 11:23 AM
> > > > > >> > >> To: dev
> > > > > >> > >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > > > > >> > >>
> > > > > >> > >> OK, so right now it's just docs? How soon can we get a VOTE
> > > > thread
> > > > > >> > started
> > > > > >> > >> for 4.0.0?
> > > > > >> > >>
> > > > > >> > >> On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <
> > > > > agrieve@chromium.org>
> > > > > >> > >> wrote:
> > > > > >> > >>
> > > > > >> > >> > mobilespec is now working again... Took longer than I
> would
> > > > have
> > > > > >> > >> > liked, but did you know that on Android FileReader
> triggers
> > > > > >> > >> > shouldInterceptRequest() with Blob URLs!?
> > > > > >> > >> >
> > > > > >> > >> > Separate thread is already happening re: whitelists, so
> > once
> > > > > that's
> > > > > >> > >> > figured out, it's just docs afaict.
> > > > > >> > >> >
> > > > > >> > >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian Clelland <
> > > > > >> iclelland@chromium.org
> > > > > >> > >
> > > > > >> > >> > wrote:
> > > > > >> > >> >
> > > > > >> > >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <
> > > > purplecabbage@gmail.com
> > > > > >
> > > > > >> > wrote:
> > > > > >> > >> > >
> > > > > >> > >> > > > We should start a new whitelist plugin related
> thread.
> > > > > >> > >> > > >
> > > > > >> > >> > > > Why is a plugin blocking a release? Default (aka
> > > > no-plugin)
> > > > > >> > >> > > > behavior should be to allow all network requests
> > > shouldn't
> > > > > it?
> > > > > >> > >> > >
> > > > > >> > >> > >
> > > > > >> > >> > > Well, that just might be a blacklist then :)
> > > > > >> > >> > >
> > > > > >> > >> > >
> > > > > >> > >> > > > This thread is a
> > > > > >> > >> > > > month long, and not the first discussion of 4.0.0 for
> > > > > Android.
> > > > > >> > >> > > >
> > > > > >> > >> > >
> > > > > >> > >> > > Seriously, though -- the whitelist discussion is much
> > > longer
> > > > > than
> > > > > >> > >> > > that,
> > > > > >> > >> > and
> > > > > >> > >> > > this isn't the first time that the default
> > > no-network-access
> > > > > >> policy
> > > > > >> > >> > > has been brought up:
> > > > > >> > >> > >
> > > > > >> > >> > > (Here's the first question, from *July*:
> > > > > >> > >> > > http://markmail.org/message/t4vj4saisem2mcgw
> > > > > >> > >> > > Here's where I mentioned what the implemented policy
> was:
> > > > > >> > >> > > http://markmail.org/message/s4necfnh4hnblpjm
> > > > > >> > >> > > And in another discussion:
> > > > > >> > >> > > http://markmail.org/message/ap7syhqysizmsvrz)
> > > > > >> > >> > >
> > > > > >> > >> > > If we want to reconsider that decision, then we should
> > > > > certainly
> > > > > >> do
> > > > > >> > >> > > so before we cut a release. I think it would be a real
> > > > problem
> > > > > to
> > > > > >> > >> > > change it afterwards, so let's get it right.
> > > > > >> > >> > >
> > > > > >> > >> > > Also, it's not the plugin itself that's blocking the
> > > release,
> > > > > >> it's
> > > > > >> > >> > > us making sure that we've implemented the core hooks
> > > > correctly
> > > > > so
> > > > > >> > >> > > that the plugin can actually do its job, and that
> people
> > > who
> > > > > >> don't
> > > > > >> > >> > > want that particular plugin can make a better one.
> > > > > >> > >> > >
> > > > > >> > >> > > (It is also an issue that a plugin, required for
> > > > > cordova-android
> > > > > >> > >> > > 4.0.0, breaks apps which are also building for
> > cordova-ios
> > > > > 3.8.0.
> > > > > >> > >> > > I'll take a
> > > > > >> > >> > look
> > > > > >> > >> > > at that, and either remove the ios-native portions of
> the
> > > > > >> whitelist
> > > > > >> > >> > plugin,
> > > > > >> > >> > > or neuter it so that it doesn't interfere with an ios
> app
> > > if
> > > > > it's
> > > > > >> > >> > > not on the unplug-whitelist branch of that repo.)
> > > > > >> > >> > >
> > > > > >> > >> > > Ian
> > > > > >> > >> > >
> > > > > >> > >> > >
> > > > > >> > >> > > > @purplecabbage
> > > > > >> > >> > > > risingj.com
> > > > > >> > >> > > >
> > > > > >> > >> > > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <
> > > shazron@gmail.com
> > > > >
> > > > > >> > wrote:
> > > > > >> > >> > > >
> > > > > >> > >> > > > > legacy-whitelist-plugin should be fixed so that it
> > > > compiles
> > > > > >> on
> > > > > >> > >> > > > > cordova-ios@3.8.0. It shouldn't be a problem to
> fix
> > > this
> > > > > at
> > > > > >> > >> > > > > compile
> > > > > >> > >> > or
> > > > > >> > >> > > > > run-time (whichever is applicable here related to
> the
> > > > > compile
> > > > > >> > >> > > > > error)
> > > > > >> > >> > > > >
> > > > > >> > >> > > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue
> > > > > >> > >> > > > > <dv...@gmail.com>
> > > > > >> > >> > > > wrote:
> > > > > >> > >> > > > > > On 2 March 2015 at 13:37, Joe Bowser <
> > > > bowserj@gmail.com>
> > > > > >> > wrote:
> > > > > >> > >> > > > > >> So, right now the whitelist changes are what's
> > > holding
> > > > > up
> > > > > >> the
> > > > > >> > >> > 4.0.0
> > > > > >> > >> > > > > release
> > > > > >> > >> > > > > >> now? Is this really the only thing that's
> holding
> > > up
> > > > > this
> > > > > >> > >> > release?
> > > > > >> > >> > > > > >>
> > > > > >> > >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve <
> > > > > >> > >> > > agrieve@chromium.org>
> > > > > >> > >> > > > > wrote:
> > > > > >> > >> > > > > >>
> > > > > >> > >> > > > > >>> I think we'll also need to finish with the
> > > whitelist
> > > > > >> changes
> > > > > >> > >> > > > > >>> &
> > > > > >> > >> > have
> > > > > >> > >> > > > > both
> > > > > >> > >> > > > > >>> the legacy and new-way whitelist plugins
> released
> > > > > before
> > > > > >> we
> > > > > >> > >> > > > > >>> can
> > > > > >> > >> > do
> > > > > >> > >> > > a
> > > > > >> > >> > > > > 4.0.0
> > > > > >> > >> > > > > >>> release (otherwise you wouldn't be able to
> write
> > an
> > > > app
> > > > > >> that
> > > > > >> > >> > > > > >>> hits
> > > > > >> > >> > > the
> > > > > >> > >> > > > > >>> network)
> > > > > >> > >> > > > > >>>
> > > > > >> > >> > > > > >
> > > > > >> > >> > > > > > Just FYI, the whitelist stuff is proving to be a
> > bit
> > > > of a
> > > > > >> pain
> > > > > >> > >> > point.
> > > > > >> > >> > > > > > I'm using cordova-android@master, and need to
> > > install
> > > > > the
> > > > > >> > >> > > > > > legacy-whitelist plugin in order to make network
> > > > > requests.
> > > > > >> > >> > > > > > Once the plugin is installed, everything seems to
> > > work.
> > > > > >> > >> > > > > >
> > > > > >> > >> > > > > > The problem is that the legacy-whitelist plugin
> > > > generates
> > > > > >> > >> > > > > > compile errors with cordova-ios@3.8.0, so now I
> > > can't
> > > > > just
> > > > > >> > run
> > > > > >> > >> > > > > > `cordova build`, I need to split the platforms up
> > and
> > > > > >> > >> > > > > > install/uninstall the plugin in between. If
> someone
> > > > > makes a
> > > > > >> > >> > > > > > dev build for Android and forgets the plugin, it
> > will
> > > > > >> appear
> > > > > >> > >> > > > > > to build successfully but not actually function
> > > > properly
> > > > > >> due
> > > > > >> > to
> > > > > >> > >> the whitelist.
> > > > > >> > >> > > > > >
> > > > > >> > >> > > > > > I know, this is all pre-release, so pain is
> > somewhat
> > > > > >> expected
> > > > > >> > >> > > > > > right now. I'm worried about the case where
> > > > > >> > >> > > > > > cordova-android@4.0.0 is released and
> > > > cordova-ios@3.8.0
> > > > > is
> > > > > >> > >> > > > > > still current, and how people
> > > > > >> > >> > can
> > > > > >> > >> > > > > > avoid whitelist breakage there.
> > > > > >> > >> > > > > >
> > > > > >> > >> > > > > >
> > > > > >> ------------------------------------------------------------
> > > > > >> > >> > ---------
> > > > > >> > >> > > > > > To unsubscribe, e-mail:
> > > > > dev-unsubscribe@cordova.apache.org
> > > > > >> > >> > > > > > For additional commands, e-mail:
> > > > > >> dev-help@cordova.apache.org
> > > > > >> > >> > > > > >
> > > > > >> > >> > > > >
> > > > > >> > >> > > > >
> > > > > ------------------------------------------------------------
> > > > > >> > >> > ---------
> > > > > >> > >> > > > > To unsubscribe, e-mail:
> > > > dev-unsubscribe@cordova.apache.org
> > > > > >> > >> > > > > For additional commands, e-mail:
> > > > > dev-help@cordova.apache.org
> > > > > >> > >> > > > >
> > > > > >> > >> > > > >
> > > > > >> > >> > > >
> > > > > >> > >> > >
> > > > > >> > >> >
> > > > > >> > >>
> > > > > >> >
> > > > > >> >
> > > > ---------------------------------------------------------------------
> > > > > >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > > >> > For additional commands, e-mail: dev-help@cordova.apache.org
> > > > > >> >
> > > > > >> >
> > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Carlos Santana
> > > > <cs...@gmail.com>
> > > >
> > >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Let's do it!
On Mon, Apr 6, 2015 at 7:33 PM, Joe Bowser <bo...@gmail.com> wrote:
> So, I think we should put off the embedder's guide until after the
> release. A lot of it has changed, and since we're still technically
> obligated to support the 3.x release tree for six months, that should buy
> us some time to figure out how that is going to work. Getting Cordova to
> work with a vanilla Android Studio project is a non-trivial task.
>
> Given that everything else appears to be done, should we start voting on an
> RC for this? What do people think?
>
>
>
> On Thu, Mar 19, 2015 at 10:31 AM Andrew Grieve <ag...@chromium.org>
> wrote:
>
> > Here's issues:
> > https://issues.apache.org/jira/browse/CB-8715 (docs)
> > https://issues.apache.org/jira/browse/CB-8716 (whitelist)
> > https://issues.apache.org/jira/browse/CB-8717 (write RELEASENOTES.md)
> >
> > On Tue, Mar 17, 2015 at 10:15 AM, Carlos Santana <cs...@gmail.com>
> > wrote:
> >
> > > I would say let's start RC testing and voting, But not pin the version
> in
> > > Cordova CLI until the tasks that Andrew mentioned are done.
> > > Andrew can you create the JIRA Items for the tasks that need to be
> done.
> > I
> > > thought there was a discussion about creating JIRA Items to help track
> > and
> > > know what's left for release something.
> > >
> > > - upgrade guide,
> > > - publishing whitelist plugins,
> > > - and making it so that the default project template includes <plugin
> > > name="cordova-plugin-whitelist" />)
> > >
> > >
> > > On Mon, Mar 16, 2015 at 11:21 PM, Ian Clelland <iclelland@chromium.org
> >
> > > wrote:
> > >
> > > > We'll probably need at least an RC for the whitelist plugin, if not a
> > > vote,
> > > > to be able to vote on this.
> > > >
> > > > Or can we just include instructions like "Use
> > > > cordova-plugin-whitelist@f70b1bc for testing" while we start the
> > > official
> > > > release process for the plugins?
> > > >
> > > > On Mon, Mar 16, 2015 at 11:17 PM, Ian Clelland <
> iclelland@chromium.org
> > >
> > > > wrote:
> > > >
> > > > > +1 -- Let's get this out the door :)
> > > > > I'll see what I can get done to move it in that direction.
> > > > >
> > > > > On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <
> agrieve@chromium.org
> > >
> > > > > wrote:
> > > > >
> > > > >> Everything's ready afaik (minus upgrade guide, publishing
> whitelist
> > > > >> plugins, and making it so that the default project template
> includes
> > > > >> <plugin name="cordova-plugin-whitelist" />). Maybe let's do a RC
> > while
> > > > we
> > > > >> wait on these things being finished up?
> > > > >>
> > > > >> If anyone wants to take on any of these tasks, that would be
> > awesome.
> > > > >>
> > > > >> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <sh...@gmail.com>
> wrote:
> > > > >>
> > > > >> > +1 for vote thread, let's get this thing out so people (that are
> > not
> > > > >> > us) can test...
> > > > >> >
> > > > >> >
> > > > >> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <bo...@gmail.com>
> > > > wrote:
> > > > >> > > OK, this is a three month old thread, and we're waiting on a
> > > > >> discussion
> > > > >> > > before we release something? I really think we should go to a
> > vote
> > > > >> thread
> > > > >> > > now that we have a legacy whitelist plugin and a new style
> > > whitelist
> > > > >> > > plugin. We shouldn't keep constantly delaying this release
> > > because
> > > > of
> > > > >> > > what's happening on other platforms, especially since we
> already
> > > > >> > pluginized
> > > > >> > > the whitelist.
> > > > >> > >
> > > > >> > > Can we please release soon?
> > > > >> > >
> > > > >> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil Khandelwal <
> > > > >> > nikhilkh@microsoft.com>
> > > > >> > > wrote:
> > > > >> > >
> > > > >> > >> I know we discussed a couple of approaches implementing the
> > > default
> > > > >> > >> whitelist policy for Android/iOS - either every app would be
> > > > >> required to
> > > > >> > >> include the whitelist plugin or have it have smart defaults
> in
> > > the
> > > > >> > platform
> > > > >> > >> implementation and the plugin being able to override them.
> > > > >> > >>
> > > > >> > >> I don’t think that thread closed with any conclusions.
> > > > >> > >>
> > > > >> > >> Thanks,
> > > > >> > >> Nikhil
> > > > >> > >>
> > > > >> > >>
> > > > >> > >> -----Original Message-----
> > > > >> > >> From: Joe Bowser [mailto:bowserj@gmail.com]
> > > > >> > >> Sent: Thursday, March 12, 2015 11:23 AM
> > > > >> > >> To: dev
> > > > >> > >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > > > >> > >>
> > > > >> > >> OK, so right now it's just docs? How soon can we get a VOTE
> > > thread
> > > > >> > started
> > > > >> > >> for 4.0.0?
> > > > >> > >>
> > > > >> > >> On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <
> > > > agrieve@chromium.org>
> > > > >> > >> wrote:
> > > > >> > >>
> > > > >> > >> > mobilespec is now working again... Took longer than I would
> > > have
> > > > >> > >> > liked, but did you know that on Android FileReader triggers
> > > > >> > >> > shouldInterceptRequest() with Blob URLs!?
> > > > >> > >> >
> > > > >> > >> > Separate thread is already happening re: whitelists, so
> once
> > > > that's
> > > > >> > >> > figured out, it's just docs afaict.
> > > > >> > >> >
> > > > >> > >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian Clelland <
> > > > >> iclelland@chromium.org
> > > > >> > >
> > > > >> > >> > wrote:
> > > > >> > >> >
> > > > >> > >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <
> > > purplecabbage@gmail.com
> > > > >
> > > > >> > wrote:
> > > > >> > >> > >
> > > > >> > >> > > > We should start a new whitelist plugin related thread.
> > > > >> > >> > > >
> > > > >> > >> > > > Why is a plugin blocking a release? Default (aka
> > > no-plugin)
> > > > >> > >> > > > behavior should be to allow all network requests
> > shouldn't
> > > > it?
> > > > >> > >> > >
> > > > >> > >> > >
> > > > >> > >> > > Well, that just might be a blacklist then :)
> > > > >> > >> > >
> > > > >> > >> > >
> > > > >> > >> > > > This thread is a
> > > > >> > >> > > > month long, and not the first discussion of 4.0.0 for
> > > > Android.
> > > > >> > >> > > >
> > > > >> > >> > >
> > > > >> > >> > > Seriously, though -- the whitelist discussion is much
> > longer
> > > > than
> > > > >> > >> > > that,
> > > > >> > >> > and
> > > > >> > >> > > this isn't the first time that the default
> > no-network-access
> > > > >> policy
> > > > >> > >> > > has been brought up:
> > > > >> > >> > >
> > > > >> > >> > > (Here's the first question, from *July*:
> > > > >> > >> > > http://markmail.org/message/t4vj4saisem2mcgw
> > > > >> > >> > > Here's where I mentioned what the implemented policy was:
> > > > >> > >> > > http://markmail.org/message/s4necfnh4hnblpjm
> > > > >> > >> > > And in another discussion:
> > > > >> > >> > > http://markmail.org/message/ap7syhqysizmsvrz)
> > > > >> > >> > >
> > > > >> > >> > > If we want to reconsider that decision, then we should
> > > > certainly
> > > > >> do
> > > > >> > >> > > so before we cut a release. I think it would be a real
> > > problem
> > > > to
> > > > >> > >> > > change it afterwards, so let's get it right.
> > > > >> > >> > >
> > > > >> > >> > > Also, it's not the plugin itself that's blocking the
> > release,
> > > > >> it's
> > > > >> > >> > > us making sure that we've implemented the core hooks
> > > correctly
> > > > so
> > > > >> > >> > > that the plugin can actually do its job, and that people
> > who
> > > > >> don't
> > > > >> > >> > > want that particular plugin can make a better one.
> > > > >> > >> > >
> > > > >> > >> > > (It is also an issue that a plugin, required for
> > > > cordova-android
> > > > >> > >> > > 4.0.0, breaks apps which are also building for
> cordova-ios
> > > > 3.8.0.
> > > > >> > >> > > I'll take a
> > > > >> > >> > look
> > > > >> > >> > > at that, and either remove the ios-native portions of the
> > > > >> whitelist
> > > > >> > >> > plugin,
> > > > >> > >> > > or neuter it so that it doesn't interfere with an ios app
> > if
> > > > it's
> > > > >> > >> > > not on the unplug-whitelist branch of that repo.)
> > > > >> > >> > >
> > > > >> > >> > > Ian
> > > > >> > >> > >
> > > > >> > >> > >
> > > > >> > >> > > > @purplecabbage
> > > > >> > >> > > > risingj.com
> > > > >> > >> > > >
> > > > >> > >> > > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <
> > shazron@gmail.com
> > > >
> > > > >> > wrote:
> > > > >> > >> > > >
> > > > >> > >> > > > > legacy-whitelist-plugin should be fixed so that it
> > > compiles
> > > > >> on
> > > > >> > >> > > > > cordova-ios@3.8.0. It shouldn't be a problem to fix
> > this
> > > > at
> > > > >> > >> > > > > compile
> > > > >> > >> > or
> > > > >> > >> > > > > run-time (whichever is applicable here related to the
> > > > compile
> > > > >> > >> > > > > error)
> > > > >> > >> > > > >
> > > > >> > >> > > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue
> > > > >> > >> > > > > <dv...@gmail.com>
> > > > >> > >> > > > wrote:
> > > > >> > >> > > > > > On 2 March 2015 at 13:37, Joe Bowser <
> > > bowserj@gmail.com>
> > > > >> > wrote:
> > > > >> > >> > > > > >> So, right now the whitelist changes are what's
> > holding
> > > > up
> > > > >> the
> > > > >> > >> > 4.0.0
> > > > >> > >> > > > > release
> > > > >> > >> > > > > >> now? Is this really the only thing that's holding
> > up
> > > > this
> > > > >> > >> > release?
> > > > >> > >> > > > > >>
> > > > >> > >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve <
> > > > >> > >> > > agrieve@chromium.org>
> > > > >> > >> > > > > wrote:
> > > > >> > >> > > > > >>
> > > > >> > >> > > > > >>> I think we'll also need to finish with the
> > whitelist
> > > > >> changes
> > > > >> > >> > > > > >>> &
> > > > >> > >> > have
> > > > >> > >> > > > > both
> > > > >> > >> > > > > >>> the legacy and new-way whitelist plugins released
> > > > before
> > > > >> we
> > > > >> > >> > > > > >>> can
> > > > >> > >> > do
> > > > >> > >> > > a
> > > > >> > >> > > > > 4.0.0
> > > > >> > >> > > > > >>> release (otherwise you wouldn't be able to write
> an
> > > app
> > > > >> that
> > > > >> > >> > > > > >>> hits
> > > > >> > >> > > the
> > > > >> > >> > > > > >>> network)
> > > > >> > >> > > > > >>>
> > > > >> > >> > > > > >
> > > > >> > >> > > > > > Just FYI, the whitelist stuff is proving to be a
> bit
> > > of a
> > > > >> pain
> > > > >> > >> > point.
> > > > >> > >> > > > > > I'm using cordova-android@master, and need to
> > install
> > > > the
> > > > >> > >> > > > > > legacy-whitelist plugin in order to make network
> > > > requests.
> > > > >> > >> > > > > > Once the plugin is installed, everything seems to
> > work.
> > > > >> > >> > > > > >
> > > > >> > >> > > > > > The problem is that the legacy-whitelist plugin
> > > generates
> > > > >> > >> > > > > > compile errors with cordova-ios@3.8.0, so now I
> > can't
> > > > just
> > > > >> > run
> > > > >> > >> > > > > > `cordova build`, I need to split the platforms up
> and
> > > > >> > >> > > > > > install/uninstall the plugin in between. If someone
> > > > makes a
> > > > >> > >> > > > > > dev build for Android and forgets the plugin, it
> will
> > > > >> appear
> > > > >> > >> > > > > > to build successfully but not actually function
> > > properly
> > > > >> due
> > > > >> > to
> > > > >> > >> the whitelist.
> > > > >> > >> > > > > >
> > > > >> > >> > > > > > I know, this is all pre-release, so pain is
> somewhat
> > > > >> expected
> > > > >> > >> > > > > > right now. I'm worried about the case where
> > > > >> > >> > > > > > cordova-android@4.0.0 is released and
> > > cordova-ios@3.8.0
> > > > is
> > > > >> > >> > > > > > still current, and how people
> > > > >> > >> > can
> > > > >> > >> > > > > > avoid whitelist breakage there.
> > > > >> > >> > > > > >
> > > > >> > >> > > > > >
> > > > >> ------------------------------------------------------------
> > > > >> > >> > ---------
> > > > >> > >> > > > > > To unsubscribe, e-mail:
> > > > dev-unsubscribe@cordova.apache.org
> > > > >> > >> > > > > > For additional commands, e-mail:
> > > > >> dev-help@cordova.apache.org
> > > > >> > >> > > > > >
> > > > >> > >> > > > >
> > > > >> > >> > > > >
> > > > ------------------------------------------------------------
> > > > >> > >> > ---------
> > > > >> > >> > > > > To unsubscribe, e-mail:
> > > dev-unsubscribe@cordova.apache.org
> > > > >> > >> > > > > For additional commands, e-mail:
> > > > dev-help@cordova.apache.org
> > > > >> > >> > > > >
> > > > >> > >> > > > >
> > > > >> > >> > > >
> > > > >> > >> > >
> > > > >> > >> >
> > > > >> > >>
> > > > >> >
> > > > >> >
> > > ---------------------------------------------------------------------
> > > > >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > >> > For additional commands, e-mail: dev-help@cordova.apache.org
> > > > >> >
> > > > >> >
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Carlos Santana
> > > <cs...@gmail.com>
> > >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Joe Bowser <bo...@gmail.com>.
So, I think we should put off the embedder's guide until after the
release. A lot of it has changed, and since we're still technically
obligated to support the 3.x release tree for six months, that should buy
us some time to figure out how that is going to work. Getting Cordova to
work with a vanilla Android Studio project is a non-trivial task.
Given that everything else appears to be done, should we start voting on an
RC for this? What do people think?
On Thu, Mar 19, 2015 at 10:31 AM Andrew Grieve <ag...@chromium.org> wrote:
> Here's issues:
> https://issues.apache.org/jira/browse/CB-8715 (docs)
> https://issues.apache.org/jira/browse/CB-8716 (whitelist)
> https://issues.apache.org/jira/browse/CB-8717 (write RELEASENOTES.md)
>
> On Tue, Mar 17, 2015 at 10:15 AM, Carlos Santana <cs...@gmail.com>
> wrote:
>
> > I would say let's start RC testing and voting, But not pin the version in
> > Cordova CLI until the tasks that Andrew mentioned are done.
> > Andrew can you create the JIRA Items for the tasks that need to be done.
> I
> > thought there was a discussion about creating JIRA Items to help track
> and
> > know what's left for release something.
> >
> > - upgrade guide,
> > - publishing whitelist plugins,
> > - and making it so that the default project template includes <plugin
> > name="cordova-plugin-whitelist" />)
> >
> >
> > On Mon, Mar 16, 2015 at 11:21 PM, Ian Clelland <ic...@chromium.org>
> > wrote:
> >
> > > We'll probably need at least an RC for the whitelist plugin, if not a
> > vote,
> > > to be able to vote on this.
> > >
> > > Or can we just include instructions like "Use
> > > cordova-plugin-whitelist@f70b1bc for testing" while we start the
> > official
> > > release process for the plugins?
> > >
> > > On Mon, Mar 16, 2015 at 11:17 PM, Ian Clelland <iclelland@chromium.org
> >
> > > wrote:
> > >
> > > > +1 -- Let's get this out the door :)
> > > > I'll see what I can get done to move it in that direction.
> > > >
> > > > On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <agrieve@chromium.org
> >
> > > > wrote:
> > > >
> > > >> Everything's ready afaik (minus upgrade guide, publishing whitelist
> > > >> plugins, and making it so that the default project template includes
> > > >> <plugin name="cordova-plugin-whitelist" />). Maybe let's do a RC
> while
> > > we
> > > >> wait on these things being finished up?
> > > >>
> > > >> If anyone wants to take on any of these tasks, that would be
> awesome.
> > > >>
> > > >> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <sh...@gmail.com> wrote:
> > > >>
> > > >> > +1 for vote thread, let's get this thing out so people (that are
> not
> > > >> > us) can test...
> > > >> >
> > > >> >
> > > >> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <bo...@gmail.com>
> > > wrote:
> > > >> > > OK, this is a three month old thread, and we're waiting on a
> > > >> discussion
> > > >> > > before we release something? I really think we should go to a
> vote
> > > >> thread
> > > >> > > now that we have a legacy whitelist plugin and a new style
> > whitelist
> > > >> > > plugin. We shouldn't keep constantly delaying this release
> > because
> > > of
> > > >> > > what's happening on other platforms, especially since we already
> > > >> > pluginized
> > > >> > > the whitelist.
> > > >> > >
> > > >> > > Can we please release soon?
> > > >> > >
> > > >> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil Khandelwal <
> > > >> > nikhilkh@microsoft.com>
> > > >> > > wrote:
> > > >> > >
> > > >> > >> I know we discussed a couple of approaches implementing the
> > default
> > > >> > >> whitelist policy for Android/iOS - either every app would be
> > > >> required to
> > > >> > >> include the whitelist plugin or have it have smart defaults in
> > the
> > > >> > platform
> > > >> > >> implementation and the plugin being able to override them.
> > > >> > >>
> > > >> > >> I don’t think that thread closed with any conclusions.
> > > >> > >>
> > > >> > >> Thanks,
> > > >> > >> Nikhil
> > > >> > >>
> > > >> > >>
> > > >> > >> -----Original Message-----
> > > >> > >> From: Joe Bowser [mailto:bowserj@gmail.com]
> > > >> > >> Sent: Thursday, March 12, 2015 11:23 AM
> > > >> > >> To: dev
> > > >> > >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > > >> > >>
> > > >> > >> OK, so right now it's just docs? How soon can we get a VOTE
> > thread
> > > >> > started
> > > >> > >> for 4.0.0?
> > > >> > >>
> > > >> > >> On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <
> > > agrieve@chromium.org>
> > > >> > >> wrote:
> > > >> > >>
> > > >> > >> > mobilespec is now working again... Took longer than I would
> > have
> > > >> > >> > liked, but did you know that on Android FileReader triggers
> > > >> > >> > shouldInterceptRequest() with Blob URLs!?
> > > >> > >> >
> > > >> > >> > Separate thread is already happening re: whitelists, so once
> > > that's
> > > >> > >> > figured out, it's just docs afaict.
> > > >> > >> >
> > > >> > >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian Clelland <
> > > >> iclelland@chromium.org
> > > >> > >
> > > >> > >> > wrote:
> > > >> > >> >
> > > >> > >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <
> > purplecabbage@gmail.com
> > > >
> > > >> > wrote:
> > > >> > >> > >
> > > >> > >> > > > We should start a new whitelist plugin related thread.
> > > >> > >> > > >
> > > >> > >> > > > Why is a plugin blocking a release? Default (aka
> > no-plugin)
> > > >> > >> > > > behavior should be to allow all network requests
> shouldn't
> > > it?
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > > Well, that just might be a blacklist then :)
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > > > This thread is a
> > > >> > >> > > > month long, and not the first discussion of 4.0.0 for
> > > Android.
> > > >> > >> > > >
> > > >> > >> > >
> > > >> > >> > > Seriously, though -- the whitelist discussion is much
> longer
> > > than
> > > >> > >> > > that,
> > > >> > >> > and
> > > >> > >> > > this isn't the first time that the default
> no-network-access
> > > >> policy
> > > >> > >> > > has been brought up:
> > > >> > >> > >
> > > >> > >> > > (Here's the first question, from *July*:
> > > >> > >> > > http://markmail.org/message/t4vj4saisem2mcgw
> > > >> > >> > > Here's where I mentioned what the implemented policy was:
> > > >> > >> > > http://markmail.org/message/s4necfnh4hnblpjm
> > > >> > >> > > And in another discussion:
> > > >> > >> > > http://markmail.org/message/ap7syhqysizmsvrz)
> > > >> > >> > >
> > > >> > >> > > If we want to reconsider that decision, then we should
> > > certainly
> > > >> do
> > > >> > >> > > so before we cut a release. I think it would be a real
> > problem
> > > to
> > > >> > >> > > change it afterwards, so let's get it right.
> > > >> > >> > >
> > > >> > >> > > Also, it's not the plugin itself that's blocking the
> release,
> > > >> it's
> > > >> > >> > > us making sure that we've implemented the core hooks
> > correctly
> > > so
> > > >> > >> > > that the plugin can actually do its job, and that people
> who
> > > >> don't
> > > >> > >> > > want that particular plugin can make a better one.
> > > >> > >> > >
> > > >> > >> > > (It is also an issue that a plugin, required for
> > > cordova-android
> > > >> > >> > > 4.0.0, breaks apps which are also building for cordova-ios
> > > 3.8.0.
> > > >> > >> > > I'll take a
> > > >> > >> > look
> > > >> > >> > > at that, and either remove the ios-native portions of the
> > > >> whitelist
> > > >> > >> > plugin,
> > > >> > >> > > or neuter it so that it doesn't interfere with an ios app
> if
> > > it's
> > > >> > >> > > not on the unplug-whitelist branch of that repo.)
> > > >> > >> > >
> > > >> > >> > > Ian
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > > > @purplecabbage
> > > >> > >> > > > risingj.com
> > > >> > >> > > >
> > > >> > >> > > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <
> shazron@gmail.com
> > >
> > > >> > wrote:
> > > >> > >> > > >
> > > >> > >> > > > > legacy-whitelist-plugin should be fixed so that it
> > compiles
> > > >> on
> > > >> > >> > > > > cordova-ios@3.8.0. It shouldn't be a problem to fix
> this
> > > at
> > > >> > >> > > > > compile
> > > >> > >> > or
> > > >> > >> > > > > run-time (whichever is applicable here related to the
> > > compile
> > > >> > >> > > > > error)
> > > >> > >> > > > >
> > > >> > >> > > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue
> > > >> > >> > > > > <dv...@gmail.com>
> > > >> > >> > > > wrote:
> > > >> > >> > > > > > On 2 March 2015 at 13:37, Joe Bowser <
> > bowserj@gmail.com>
> > > >> > wrote:
> > > >> > >> > > > > >> So, right now the whitelist changes are what's
> holding
> > > up
> > > >> the
> > > >> > >> > 4.0.0
> > > >> > >> > > > > release
> > > >> > >> > > > > >> now? Is this really the only thing that's holding
> up
> > > this
> > > >> > >> > release?
> > > >> > >> > > > > >>
> > > >> > >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve <
> > > >> > >> > > agrieve@chromium.org>
> > > >> > >> > > > > wrote:
> > > >> > >> > > > > >>
> > > >> > >> > > > > >>> I think we'll also need to finish with the
> whitelist
> > > >> changes
> > > >> > >> > > > > >>> &
> > > >> > >> > have
> > > >> > >> > > > > both
> > > >> > >> > > > > >>> the legacy and new-way whitelist plugins released
> > > before
> > > >> we
> > > >> > >> > > > > >>> can
> > > >> > >> > do
> > > >> > >> > > a
> > > >> > >> > > > > 4.0.0
> > > >> > >> > > > > >>> release (otherwise you wouldn't be able to write an
> > app
> > > >> that
> > > >> > >> > > > > >>> hits
> > > >> > >> > > the
> > > >> > >> > > > > >>> network)
> > > >> > >> > > > > >>>
> > > >> > >> > > > > >
> > > >> > >> > > > > > Just FYI, the whitelist stuff is proving to be a bit
> > of a
> > > >> pain
> > > >> > >> > point.
> > > >> > >> > > > > > I'm using cordova-android@master, and need to
> install
> > > the
> > > >> > >> > > > > > legacy-whitelist plugin in order to make network
> > > requests.
> > > >> > >> > > > > > Once the plugin is installed, everything seems to
> work.
> > > >> > >> > > > > >
> > > >> > >> > > > > > The problem is that the legacy-whitelist plugin
> > generates
> > > >> > >> > > > > > compile errors with cordova-ios@3.8.0, so now I
> can't
> > > just
> > > >> > run
> > > >> > >> > > > > > `cordova build`, I need to split the platforms up and
> > > >> > >> > > > > > install/uninstall the plugin in between. If someone
> > > makes a
> > > >> > >> > > > > > dev build for Android and forgets the plugin, it will
> > > >> appear
> > > >> > >> > > > > > to build successfully but not actually function
> > properly
> > > >> due
> > > >> > to
> > > >> > >> the whitelist.
> > > >> > >> > > > > >
> > > >> > >> > > > > > I know, this is all pre-release, so pain is somewhat
> > > >> expected
> > > >> > >> > > > > > right now. I'm worried about the case where
> > > >> > >> > > > > > cordova-android@4.0.0 is released and
> > cordova-ios@3.8.0
> > > is
> > > >> > >> > > > > > still current, and how people
> > > >> > >> > can
> > > >> > >> > > > > > avoid whitelist breakage there.
> > > >> > >> > > > > >
> > > >> > >> > > > > >
> > > >> ------------------------------------------------------------
> > > >> > >> > ---------
> > > >> > >> > > > > > To unsubscribe, e-mail:
> > > dev-unsubscribe@cordova.apache.org
> > > >> > >> > > > > > For additional commands, e-mail:
> > > >> dev-help@cordova.apache.org
> > > >> > >> > > > > >
> > > >> > >> > > > >
> > > >> > >> > > > >
> > > ------------------------------------------------------------
> > > >> > >> > ---------
> > > >> > >> > > > > To unsubscribe, e-mail:
> > dev-unsubscribe@cordova.apache.org
> > > >> > >> > > > > For additional commands, e-mail:
> > > dev-help@cordova.apache.org
> > > >> > >> > > > >
> > > >> > >> > > > >
> > > >> > >> > > >
> > > >> > >> > >
> > > >> > >> >
> > > >> > >>
> > > >> >
> > > >> >
> > ---------------------------------------------------------------------
> > > >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > >> > For additional commands, e-mail: dev-help@cordova.apache.org
> > > >> >
> > > >> >
> > > >>
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > Carlos Santana
> > <cs...@gmail.com>
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Here's issues:
https://issues.apache.org/jira/browse/CB-8715 (docs)
https://issues.apache.org/jira/browse/CB-8716 (whitelist)
https://issues.apache.org/jira/browse/CB-8717 (write RELEASENOTES.md)
On Tue, Mar 17, 2015 at 10:15 AM, Carlos Santana <cs...@gmail.com>
wrote:
> I would say let's start RC testing and voting, But not pin the version in
> Cordova CLI until the tasks that Andrew mentioned are done.
> Andrew can you create the JIRA Items for the tasks that need to be done. I
> thought there was a discussion about creating JIRA Items to help track and
> know what's left for release something.
>
> - upgrade guide,
> - publishing whitelist plugins,
> - and making it so that the default project template includes <plugin
> name="cordova-plugin-whitelist" />)
>
>
> On Mon, Mar 16, 2015 at 11:21 PM, Ian Clelland <ic...@chromium.org>
> wrote:
>
> > We'll probably need at least an RC for the whitelist plugin, if not a
> vote,
> > to be able to vote on this.
> >
> > Or can we just include instructions like "Use
> > cordova-plugin-whitelist@f70b1bc for testing" while we start the
> official
> > release process for the plugins?
> >
> > On Mon, Mar 16, 2015 at 11:17 PM, Ian Clelland <ic...@chromium.org>
> > wrote:
> >
> > > +1 -- Let's get this out the door :)
> > > I'll see what I can get done to move it in that direction.
> > >
> > > On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <ag...@chromium.org>
> > > wrote:
> > >
> > >> Everything's ready afaik (minus upgrade guide, publishing whitelist
> > >> plugins, and making it so that the default project template includes
> > >> <plugin name="cordova-plugin-whitelist" />). Maybe let's do a RC while
> > we
> > >> wait on these things being finished up?
> > >>
> > >> If anyone wants to take on any of these tasks, that would be awesome.
> > >>
> > >> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <sh...@gmail.com> wrote:
> > >>
> > >> > +1 for vote thread, let's get this thing out so people (that are not
> > >> > us) can test...
> > >> >
> > >> >
> > >> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <bo...@gmail.com>
> > wrote:
> > >> > > OK, this is a three month old thread, and we're waiting on a
> > >> discussion
> > >> > > before we release something? I really think we should go to a vote
> > >> thread
> > >> > > now that we have a legacy whitelist plugin and a new style
> whitelist
> > >> > > plugin. We shouldn't keep constantly delaying this release
> because
> > of
> > >> > > what's happening on other platforms, especially since we already
> > >> > pluginized
> > >> > > the whitelist.
> > >> > >
> > >> > > Can we please release soon?
> > >> > >
> > >> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil Khandelwal <
> > >> > nikhilkh@microsoft.com>
> > >> > > wrote:
> > >> > >
> > >> > >> I know we discussed a couple of approaches implementing the
> default
> > >> > >> whitelist policy for Android/iOS - either every app would be
> > >> required to
> > >> > >> include the whitelist plugin or have it have smart defaults in
> the
> > >> > platform
> > >> > >> implementation and the plugin being able to override them.
> > >> > >>
> > >> > >> I don’t think that thread closed with any conclusions.
> > >> > >>
> > >> > >> Thanks,
> > >> > >> Nikhil
> > >> > >>
> > >> > >>
> > >> > >> -----Original Message-----
> > >> > >> From: Joe Bowser [mailto:bowserj@gmail.com]
> > >> > >> Sent: Thursday, March 12, 2015 11:23 AM
> > >> > >> To: dev
> > >> > >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > >> > >>
> > >> > >> OK, so right now it's just docs? How soon can we get a VOTE
> thread
> > >> > started
> > >> > >> for 4.0.0?
> > >> > >>
> > >> > >> On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <
> > agrieve@chromium.org>
> > >> > >> wrote:
> > >> > >>
> > >> > >> > mobilespec is now working again... Took longer than I would
> have
> > >> > >> > liked, but did you know that on Android FileReader triggers
> > >> > >> > shouldInterceptRequest() with Blob URLs!?
> > >> > >> >
> > >> > >> > Separate thread is already happening re: whitelists, so once
> > that's
> > >> > >> > figured out, it's just docs afaict.
> > >> > >> >
> > >> > >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian Clelland <
> > >> iclelland@chromium.org
> > >> > >
> > >> > >> > wrote:
> > >> > >> >
> > >> > >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <
> purplecabbage@gmail.com
> > >
> > >> > wrote:
> > >> > >> > >
> > >> > >> > > > We should start a new whitelist plugin related thread.
> > >> > >> > > >
> > >> > >> > > > Why is a plugin blocking a release? Default (aka
> no-plugin)
> > >> > >> > > > behavior should be to allow all network requests shouldn't
> > it?
> > >> > >> > >
> > >> > >> > >
> > >> > >> > > Well, that just might be a blacklist then :)
> > >> > >> > >
> > >> > >> > >
> > >> > >> > > > This thread is a
> > >> > >> > > > month long, and not the first discussion of 4.0.0 for
> > Android.
> > >> > >> > > >
> > >> > >> > >
> > >> > >> > > Seriously, though -- the whitelist discussion is much longer
> > than
> > >> > >> > > that,
> > >> > >> > and
> > >> > >> > > this isn't the first time that the default no-network-access
> > >> policy
> > >> > >> > > has been brought up:
> > >> > >> > >
> > >> > >> > > (Here's the first question, from *July*:
> > >> > >> > > http://markmail.org/message/t4vj4saisem2mcgw
> > >> > >> > > Here's where I mentioned what the implemented policy was:
> > >> > >> > > http://markmail.org/message/s4necfnh4hnblpjm
> > >> > >> > > And in another discussion:
> > >> > >> > > http://markmail.org/message/ap7syhqysizmsvrz)
> > >> > >> > >
> > >> > >> > > If we want to reconsider that decision, then we should
> > certainly
> > >> do
> > >> > >> > > so before we cut a release. I think it would be a real
> problem
> > to
> > >> > >> > > change it afterwards, so let's get it right.
> > >> > >> > >
> > >> > >> > > Also, it's not the plugin itself that's blocking the release,
> > >> it's
> > >> > >> > > us making sure that we've implemented the core hooks
> correctly
> > so
> > >> > >> > > that the plugin can actually do its job, and that people who
> > >> don't
> > >> > >> > > want that particular plugin can make a better one.
> > >> > >> > >
> > >> > >> > > (It is also an issue that a plugin, required for
> > cordova-android
> > >> > >> > > 4.0.0, breaks apps which are also building for cordova-ios
> > 3.8.0.
> > >> > >> > > I'll take a
> > >> > >> > look
> > >> > >> > > at that, and either remove the ios-native portions of the
> > >> whitelist
> > >> > >> > plugin,
> > >> > >> > > or neuter it so that it doesn't interfere with an ios app if
> > it's
> > >> > >> > > not on the unplug-whitelist branch of that repo.)
> > >> > >> > >
> > >> > >> > > Ian
> > >> > >> > >
> > >> > >> > >
> > >> > >> > > > @purplecabbage
> > >> > >> > > > risingj.com
> > >> > >> > > >
> > >> > >> > > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <shazron@gmail.com
> >
> > >> > wrote:
> > >> > >> > > >
> > >> > >> > > > > legacy-whitelist-plugin should be fixed so that it
> compiles
> > >> on
> > >> > >> > > > > cordova-ios@3.8.0. It shouldn't be a problem to fix this
> > at
> > >> > >> > > > > compile
> > >> > >> > or
> > >> > >> > > > > run-time (whichever is applicable here related to the
> > compile
> > >> > >> > > > > error)
> > >> > >> > > > >
> > >> > >> > > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue
> > >> > >> > > > > <dv...@gmail.com>
> > >> > >> > > > wrote:
> > >> > >> > > > > > On 2 March 2015 at 13:37, Joe Bowser <
> bowserj@gmail.com>
> > >> > wrote:
> > >> > >> > > > > >> So, right now the whitelist changes are what's holding
> > up
> > >> the
> > >> > >> > 4.0.0
> > >> > >> > > > > release
> > >> > >> > > > > >> now? Is this really the only thing that's holding up
> > this
> > >> > >> > release?
> > >> > >> > > > > >>
> > >> > >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve <
> > >> > >> > > agrieve@chromium.org>
> > >> > >> > > > > wrote:
> > >> > >> > > > > >>
> > >> > >> > > > > >>> I think we'll also need to finish with the whitelist
> > >> changes
> > >> > >> > > > > >>> &
> > >> > >> > have
> > >> > >> > > > > both
> > >> > >> > > > > >>> the legacy and new-way whitelist plugins released
> > before
> > >> we
> > >> > >> > > > > >>> can
> > >> > >> > do
> > >> > >> > > a
> > >> > >> > > > > 4.0.0
> > >> > >> > > > > >>> release (otherwise you wouldn't be able to write an
> app
> > >> that
> > >> > >> > > > > >>> hits
> > >> > >> > > the
> > >> > >> > > > > >>> network)
> > >> > >> > > > > >>>
> > >> > >> > > > > >
> > >> > >> > > > > > Just FYI, the whitelist stuff is proving to be a bit
> of a
> > >> pain
> > >> > >> > point.
> > >> > >> > > > > > I'm using cordova-android@master, and need to install
> > the
> > >> > >> > > > > > legacy-whitelist plugin in order to make network
> > requests.
> > >> > >> > > > > > Once the plugin is installed, everything seems to work.
> > >> > >> > > > > >
> > >> > >> > > > > > The problem is that the legacy-whitelist plugin
> generates
> > >> > >> > > > > > compile errors with cordova-ios@3.8.0, so now I can't
> > just
> > >> > run
> > >> > >> > > > > > `cordova build`, I need to split the platforms up and
> > >> > >> > > > > > install/uninstall the plugin in between. If someone
> > makes a
> > >> > >> > > > > > dev build for Android and forgets the plugin, it will
> > >> appear
> > >> > >> > > > > > to build successfully but not actually function
> properly
> > >> due
> > >> > to
> > >> > >> the whitelist.
> > >> > >> > > > > >
> > >> > >> > > > > > I know, this is all pre-release, so pain is somewhat
> > >> expected
> > >> > >> > > > > > right now. I'm worried about the case where
> > >> > >> > > > > > cordova-android@4.0.0 is released and
> cordova-ios@3.8.0
> > is
> > >> > >> > > > > > still current, and how people
> > >> > >> > can
> > >> > >> > > > > > avoid whitelist breakage there.
> > >> > >> > > > > >
> > >> > >> > > > > >
> > >> ------------------------------------------------------------
> > >> > >> > ---------
> > >> > >> > > > > > To unsubscribe, e-mail:
> > dev-unsubscribe@cordova.apache.org
> > >> > >> > > > > > For additional commands, e-mail:
> > >> dev-help@cordova.apache.org
> > >> > >> > > > > >
> > >> > >> > > > >
> > >> > >> > > > >
> > ------------------------------------------------------------
> > >> > >> > ---------
> > >> > >> > > > > To unsubscribe, e-mail:
> dev-unsubscribe@cordova.apache.org
> > >> > >> > > > > For additional commands, e-mail:
> > dev-help@cordova.apache.org
> > >> > >> > > > >
> > >> > >> > > > >
> > >> > >> > > >
> > >> > >> > >
> > >> > >> >
> > >> > >>
> > >> >
> > >> >
> ---------------------------------------------------------------------
> > >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > >> > For additional commands, e-mail: dev-help@cordova.apache.org
> > >> >
> > >> >
> > >>
> > >
> > >
> >
>
>
>
> --
> Carlos Santana
> <cs...@gmail.com>
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Carlos Santana <cs...@gmail.com>.
I would say let's start RC testing and voting, But not pin the version in
Cordova CLI until the tasks that Andrew mentioned are done.
Andrew can you create the JIRA Items for the tasks that need to be done. I
thought there was a discussion about creating JIRA Items to help track and
know what's left for release something.
- upgrade guide,
- publishing whitelist plugins,
- and making it so that the default project template includes <plugin
name="cordova-plugin-whitelist" />)
On Mon, Mar 16, 2015 at 11:21 PM, Ian Clelland <ic...@chromium.org>
wrote:
> We'll probably need at least an RC for the whitelist plugin, if not a vote,
> to be able to vote on this.
>
> Or can we just include instructions like "Use
> cordova-plugin-whitelist@f70b1bc for testing" while we start the official
> release process for the plugins?
>
> On Mon, Mar 16, 2015 at 11:17 PM, Ian Clelland <ic...@chromium.org>
> wrote:
>
> > +1 -- Let's get this out the door :)
> > I'll see what I can get done to move it in that direction.
> >
> > On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <ag...@chromium.org>
> > wrote:
> >
> >> Everything's ready afaik (minus upgrade guide, publishing whitelist
> >> plugins, and making it so that the default project template includes
> >> <plugin name="cordova-plugin-whitelist" />). Maybe let's do a RC while
> we
> >> wait on these things being finished up?
> >>
> >> If anyone wants to take on any of these tasks, that would be awesome.
> >>
> >> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <sh...@gmail.com> wrote:
> >>
> >> > +1 for vote thread, let's get this thing out so people (that are not
> >> > us) can test...
> >> >
> >> >
> >> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <bo...@gmail.com>
> wrote:
> >> > > OK, this is a three month old thread, and we're waiting on a
> >> discussion
> >> > > before we release something? I really think we should go to a vote
> >> thread
> >> > > now that we have a legacy whitelist plugin and a new style whitelist
> >> > > plugin. We shouldn't keep constantly delaying this release because
> of
> >> > > what's happening on other platforms, especially since we already
> >> > pluginized
> >> > > the whitelist.
> >> > >
> >> > > Can we please release soon?
> >> > >
> >> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil Khandelwal <
> >> > nikhilkh@microsoft.com>
> >> > > wrote:
> >> > >
> >> > >> I know we discussed a couple of approaches implementing the default
> >> > >> whitelist policy for Android/iOS - either every app would be
> >> required to
> >> > >> include the whitelist plugin or have it have smart defaults in the
> >> > platform
> >> > >> implementation and the plugin being able to override them.
> >> > >>
> >> > >> I don’t think that thread closed with any conclusions.
> >> > >>
> >> > >> Thanks,
> >> > >> Nikhil
> >> > >>
> >> > >>
> >> > >> -----Original Message-----
> >> > >> From: Joe Bowser [mailto:bowserj@gmail.com]
> >> > >> Sent: Thursday, March 12, 2015 11:23 AM
> >> > >> To: dev
> >> > >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> >> > >>
> >> > >> OK, so right now it's just docs? How soon can we get a VOTE thread
> >> > started
> >> > >> for 4.0.0?
> >> > >>
> >> > >> On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <
> agrieve@chromium.org>
> >> > >> wrote:
> >> > >>
> >> > >> > mobilespec is now working again... Took longer than I would have
> >> > >> > liked, but did you know that on Android FileReader triggers
> >> > >> > shouldInterceptRequest() with Blob URLs!?
> >> > >> >
> >> > >> > Separate thread is already happening re: whitelists, so once
> that's
> >> > >> > figured out, it's just docs afaict.
> >> > >> >
> >> > >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian Clelland <
> >> iclelland@chromium.org
> >> > >
> >> > >> > wrote:
> >> > >> >
> >> > >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <purplecabbage@gmail.com
> >
> >> > wrote:
> >> > >> > >
> >> > >> > > > We should start a new whitelist plugin related thread.
> >> > >> > > >
> >> > >> > > > Why is a plugin blocking a release? Default (aka no-plugin)
> >> > >> > > > behavior should be to allow all network requests shouldn't
> it?
> >> > >> > >
> >> > >> > >
> >> > >> > > Well, that just might be a blacklist then :)
> >> > >> > >
> >> > >> > >
> >> > >> > > > This thread is a
> >> > >> > > > month long, and not the first discussion of 4.0.0 for
> Android.
> >> > >> > > >
> >> > >> > >
> >> > >> > > Seriously, though -- the whitelist discussion is much longer
> than
> >> > >> > > that,
> >> > >> > and
> >> > >> > > this isn't the first time that the default no-network-access
> >> policy
> >> > >> > > has been brought up:
> >> > >> > >
> >> > >> > > (Here's the first question, from *July*:
> >> > >> > > http://markmail.org/message/t4vj4saisem2mcgw
> >> > >> > > Here's where I mentioned what the implemented policy was:
> >> > >> > > http://markmail.org/message/s4necfnh4hnblpjm
> >> > >> > > And in another discussion:
> >> > >> > > http://markmail.org/message/ap7syhqysizmsvrz)
> >> > >> > >
> >> > >> > > If we want to reconsider that decision, then we should
> certainly
> >> do
> >> > >> > > so before we cut a release. I think it would be a real problem
> to
> >> > >> > > change it afterwards, so let's get it right.
> >> > >> > >
> >> > >> > > Also, it's not the plugin itself that's blocking the release,
> >> it's
> >> > >> > > us making sure that we've implemented the core hooks correctly
> so
> >> > >> > > that the plugin can actually do its job, and that people who
> >> don't
> >> > >> > > want that particular plugin can make a better one.
> >> > >> > >
> >> > >> > > (It is also an issue that a plugin, required for
> cordova-android
> >> > >> > > 4.0.0, breaks apps which are also building for cordova-ios
> 3.8.0.
> >> > >> > > I'll take a
> >> > >> > look
> >> > >> > > at that, and either remove the ios-native portions of the
> >> whitelist
> >> > >> > plugin,
> >> > >> > > or neuter it so that it doesn't interfere with an ios app if
> it's
> >> > >> > > not on the unplug-whitelist branch of that repo.)
> >> > >> > >
> >> > >> > > Ian
> >> > >> > >
> >> > >> > >
> >> > >> > > > @purplecabbage
> >> > >> > > > risingj.com
> >> > >> > > >
> >> > >> > > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <sh...@gmail.com>
> >> > wrote:
> >> > >> > > >
> >> > >> > > > > legacy-whitelist-plugin should be fixed so that it compiles
> >> on
> >> > >> > > > > cordova-ios@3.8.0. It shouldn't be a problem to fix this
> at
> >> > >> > > > > compile
> >> > >> > or
> >> > >> > > > > run-time (whichever is applicable here related to the
> compile
> >> > >> > > > > error)
> >> > >> > > > >
> >> > >> > > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue
> >> > >> > > > > <dv...@gmail.com>
> >> > >> > > > wrote:
> >> > >> > > > > > On 2 March 2015 at 13:37, Joe Bowser <bo...@gmail.com>
> >> > wrote:
> >> > >> > > > > >> So, right now the whitelist changes are what's holding
> up
> >> the
> >> > >> > 4.0.0
> >> > >> > > > > release
> >> > >> > > > > >> now? Is this really the only thing that's holding up
> this
> >> > >> > release?
> >> > >> > > > > >>
> >> > >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve <
> >> > >> > > agrieve@chromium.org>
> >> > >> > > > > wrote:
> >> > >> > > > > >>
> >> > >> > > > > >>> I think we'll also need to finish with the whitelist
> >> changes
> >> > >> > > > > >>> &
> >> > >> > have
> >> > >> > > > > both
> >> > >> > > > > >>> the legacy and new-way whitelist plugins released
> before
> >> we
> >> > >> > > > > >>> can
> >> > >> > do
> >> > >> > > a
> >> > >> > > > > 4.0.0
> >> > >> > > > > >>> release (otherwise you wouldn't be able to write an app
> >> that
> >> > >> > > > > >>> hits
> >> > >> > > the
> >> > >> > > > > >>> network)
> >> > >> > > > > >>>
> >> > >> > > > > >
> >> > >> > > > > > Just FYI, the whitelist stuff is proving to be a bit of a
> >> pain
> >> > >> > point.
> >> > >> > > > > > I'm using cordova-android@master, and need to install
> the
> >> > >> > > > > > legacy-whitelist plugin in order to make network
> requests.
> >> > >> > > > > > Once the plugin is installed, everything seems to work.
> >> > >> > > > > >
> >> > >> > > > > > The problem is that the legacy-whitelist plugin generates
> >> > >> > > > > > compile errors with cordova-ios@3.8.0, so now I can't
> just
> >> > run
> >> > >> > > > > > `cordova build`, I need to split the platforms up and
> >> > >> > > > > > install/uninstall the plugin in between. If someone
> makes a
> >> > >> > > > > > dev build for Android and forgets the plugin, it will
> >> appear
> >> > >> > > > > > to build successfully but not actually function properly
> >> due
> >> > to
> >> > >> the whitelist.
> >> > >> > > > > >
> >> > >> > > > > > I know, this is all pre-release, so pain is somewhat
> >> expected
> >> > >> > > > > > right now. I'm worried about the case where
> >> > >> > > > > > cordova-android@4.0.0 is released and cordova-ios@3.8.0
> is
> >> > >> > > > > > still current, and how people
> >> > >> > can
> >> > >> > > > > > avoid whitelist breakage there.
> >> > >> > > > > >
> >> > >> > > > > >
> >> ------------------------------------------------------------
> >> > >> > ---------
> >> > >> > > > > > To unsubscribe, e-mail:
> dev-unsubscribe@cordova.apache.org
> >> > >> > > > > > For additional commands, e-mail:
> >> dev-help@cordova.apache.org
> >> > >> > > > > >
> >> > >> > > > >
> >> > >> > > > >
> ------------------------------------------------------------
> >> > >> > ---------
> >> > >> > > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> > >> > > > > For additional commands, e-mail:
> dev-help@cordova.apache.org
> >> > >> > > > >
> >> > >> > > > >
> >> > >> > > >
> >> > >> > >
> >> > >> >
> >> > >>
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> > For additional commands, e-mail: dev-help@cordova.apache.org
> >> >
> >> >
> >>
> >
> >
>
--
Carlos Santana
<cs...@gmail.com>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Ian Clelland <ic...@chromium.org>.
We'll probably need at least an RC for the whitelist plugin, if not a vote,
to be able to vote on this.
Or can we just include instructions like "Use
cordova-plugin-whitelist@f70b1bc for testing" while we start the official
release process for the plugins?
On Mon, Mar 16, 2015 at 11:17 PM, Ian Clelland <ic...@chromium.org>
wrote:
> +1 -- Let's get this out the door :)
> I'll see what I can get done to move it in that direction.
>
> On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <ag...@chromium.org>
> wrote:
>
>> Everything's ready afaik (minus upgrade guide, publishing whitelist
>> plugins, and making it so that the default project template includes
>> <plugin name="cordova-plugin-whitelist" />). Maybe let's do a RC while we
>> wait on these things being finished up?
>>
>> If anyone wants to take on any of these tasks, that would be awesome.
>>
>> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <sh...@gmail.com> wrote:
>>
>> > +1 for vote thread, let's get this thing out so people (that are not
>> > us) can test...
>> >
>> >
>> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <bo...@gmail.com> wrote:
>> > > OK, this is a three month old thread, and we're waiting on a
>> discussion
>> > > before we release something? I really think we should go to a vote
>> thread
>> > > now that we have a legacy whitelist plugin and a new style whitelist
>> > > plugin. We shouldn't keep constantly delaying this release because of
>> > > what's happening on other platforms, especially since we already
>> > pluginized
>> > > the whitelist.
>> > >
>> > > Can we please release soon?
>> > >
>> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil Khandelwal <
>> > nikhilkh@microsoft.com>
>> > > wrote:
>> > >
>> > >> I know we discussed a couple of approaches implementing the default
>> > >> whitelist policy for Android/iOS - either every app would be
>> required to
>> > >> include the whitelist plugin or have it have smart defaults in the
>> > platform
>> > >> implementation and the plugin being able to override them.
>> > >>
>> > >> I don’t think that thread closed with any conclusions.
>> > >>
>> > >> Thanks,
>> > >> Nikhil
>> > >>
>> > >>
>> > >> -----Original Message-----
>> > >> From: Joe Bowser [mailto:bowserj@gmail.com]
>> > >> Sent: Thursday, March 12, 2015 11:23 AM
>> > >> To: dev
>> > >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
>> > >>
>> > >> OK, so right now it's just docs? How soon can we get a VOTE thread
>> > started
>> > >> for 4.0.0?
>> > >>
>> > >> On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <ag...@chromium.org>
>> > >> wrote:
>> > >>
>> > >> > mobilespec is now working again... Took longer than I would have
>> > >> > liked, but did you know that on Android FileReader triggers
>> > >> > shouldInterceptRequest() with Blob URLs!?
>> > >> >
>> > >> > Separate thread is already happening re: whitelists, so once that's
>> > >> > figured out, it's just docs afaict.
>> > >> >
>> > >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian Clelland <
>> iclelland@chromium.org
>> > >
>> > >> > wrote:
>> > >> >
>> > >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <pu...@gmail.com>
>> > wrote:
>> > >> > >
>> > >> > > > We should start a new whitelist plugin related thread.
>> > >> > > >
>> > >> > > > Why is a plugin blocking a release? Default (aka no-plugin)
>> > >> > > > behavior should be to allow all network requests shouldn't it?
>> > >> > >
>> > >> > >
>> > >> > > Well, that just might be a blacklist then :)
>> > >> > >
>> > >> > >
>> > >> > > > This thread is a
>> > >> > > > month long, and not the first discussion of 4.0.0 for Android.
>> > >> > > >
>> > >> > >
>> > >> > > Seriously, though -- the whitelist discussion is much longer than
>> > >> > > that,
>> > >> > and
>> > >> > > this isn't the first time that the default no-network-access
>> policy
>> > >> > > has been brought up:
>> > >> > >
>> > >> > > (Here's the first question, from *July*:
>> > >> > > http://markmail.org/message/t4vj4saisem2mcgw
>> > >> > > Here's where I mentioned what the implemented policy was:
>> > >> > > http://markmail.org/message/s4necfnh4hnblpjm
>> > >> > > And in another discussion:
>> > >> > > http://markmail.org/message/ap7syhqysizmsvrz)
>> > >> > >
>> > >> > > If we want to reconsider that decision, then we should certainly
>> do
>> > >> > > so before we cut a release. I think it would be a real problem to
>> > >> > > change it afterwards, so let's get it right.
>> > >> > >
>> > >> > > Also, it's not the plugin itself that's blocking the release,
>> it's
>> > >> > > us making sure that we've implemented the core hooks correctly so
>> > >> > > that the plugin can actually do its job, and that people who
>> don't
>> > >> > > want that particular plugin can make a better one.
>> > >> > >
>> > >> > > (It is also an issue that a plugin, required for cordova-android
>> > >> > > 4.0.0, breaks apps which are also building for cordova-ios 3.8.0.
>> > >> > > I'll take a
>> > >> > look
>> > >> > > at that, and either remove the ios-native portions of the
>> whitelist
>> > >> > plugin,
>> > >> > > or neuter it so that it doesn't interfere with an ios app if it's
>> > >> > > not on the unplug-whitelist branch of that repo.)
>> > >> > >
>> > >> > > Ian
>> > >> > >
>> > >> > >
>> > >> > > > @purplecabbage
>> > >> > > > risingj.com
>> > >> > > >
>> > >> > > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <sh...@gmail.com>
>> > wrote:
>> > >> > > >
>> > >> > > > > legacy-whitelist-plugin should be fixed so that it compiles
>> on
>> > >> > > > > cordova-ios@3.8.0. It shouldn't be a problem to fix this at
>> > >> > > > > compile
>> > >> > or
>> > >> > > > > run-time (whichever is applicable here related to the compile
>> > >> > > > > error)
>> > >> > > > >
>> > >> > > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue
>> > >> > > > > <dv...@gmail.com>
>> > >> > > > wrote:
>> > >> > > > > > On 2 March 2015 at 13:37, Joe Bowser <bo...@gmail.com>
>> > wrote:
>> > >> > > > > >> So, right now the whitelist changes are what's holding up
>> the
>> > >> > 4.0.0
>> > >> > > > > release
>> > >> > > > > >> now? Is this really the only thing that's holding up this
>> > >> > release?
>> > >> > > > > >>
>> > >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve <
>> > >> > > agrieve@chromium.org>
>> > >> > > > > wrote:
>> > >> > > > > >>
>> > >> > > > > >>> I think we'll also need to finish with the whitelist
>> changes
>> > >> > > > > >>> &
>> > >> > have
>> > >> > > > > both
>> > >> > > > > >>> the legacy and new-way whitelist plugins released before
>> we
>> > >> > > > > >>> can
>> > >> > do
>> > >> > > a
>> > >> > > > > 4.0.0
>> > >> > > > > >>> release (otherwise you wouldn't be able to write an app
>> that
>> > >> > > > > >>> hits
>> > >> > > the
>> > >> > > > > >>> network)
>> > >> > > > > >>>
>> > >> > > > > >
>> > >> > > > > > Just FYI, the whitelist stuff is proving to be a bit of a
>> pain
>> > >> > point.
>> > >> > > > > > I'm using cordova-android@master, and need to install the
>> > >> > > > > > legacy-whitelist plugin in order to make network requests.
>> > >> > > > > > Once the plugin is installed, everything seems to work.
>> > >> > > > > >
>> > >> > > > > > The problem is that the legacy-whitelist plugin generates
>> > >> > > > > > compile errors with cordova-ios@3.8.0, so now I can't just
>> > run
>> > >> > > > > > `cordova build`, I need to split the platforms up and
>> > >> > > > > > install/uninstall the plugin in between. If someone makes a
>> > >> > > > > > dev build for Android and forgets the plugin, it will
>> appear
>> > >> > > > > > to build successfully but not actually function properly
>> due
>> > to
>> > >> the whitelist.
>> > >> > > > > >
>> > >> > > > > > I know, this is all pre-release, so pain is somewhat
>> expected
>> > >> > > > > > right now. I'm worried about the case where
>> > >> > > > > > cordova-android@4.0.0 is released and cordova-ios@3.8.0 is
>> > >> > > > > > still current, and how people
>> > >> > can
>> > >> > > > > > avoid whitelist breakage there.
>> > >> > > > > >
>> > >> > > > > >
>> ------------------------------------------------------------
>> > >> > ---------
>> > >> > > > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> > >> > > > > > For additional commands, e-mail:
>> dev-help@cordova.apache.org
>> > >> > > > > >
>> > >> > > > >
>> > >> > > > > ------------------------------------------------------------
>> > >> > ---------
>> > >> > > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> > >> > > > > For additional commands, e-mail: dev-help@cordova.apache.org
>> > >> > > > >
>> > >> > > > >
>> > >> > > >
>> > >> > >
>> > >> >
>> > >>
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> > For additional commands, e-mail: dev-help@cordova.apache.org
>> >
>> >
>>
>
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Ian Clelland <ic...@chromium.org>.
+1 -- Let's get this out the door :)
I'll see what I can get done to move it in that direction.
On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <ag...@chromium.org> wrote:
> Everything's ready afaik (minus upgrade guide, publishing whitelist
> plugins, and making it so that the default project template includes
> <plugin name="cordova-plugin-whitelist" />). Maybe let's do a RC while we
> wait on these things being finished up?
>
> If anyone wants to take on any of these tasks, that would be awesome.
>
> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <sh...@gmail.com> wrote:
>
> > +1 for vote thread, let's get this thing out so people (that are not
> > us) can test...
> >
> >
> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <bo...@gmail.com> wrote:
> > > OK, this is a three month old thread, and we're waiting on a discussion
> > > before we release something? I really think we should go to a vote
> thread
> > > now that we have a legacy whitelist plugin and a new style whitelist
> > > plugin. We shouldn't keep constantly delaying this release because of
> > > what's happening on other platforms, especially since we already
> > pluginized
> > > the whitelist.
> > >
> > > Can we please release soon?
> > >
> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil Khandelwal <
> > nikhilkh@microsoft.com>
> > > wrote:
> > >
> > >> I know we discussed a couple of approaches implementing the default
> > >> whitelist policy for Android/iOS - either every app would be required
> to
> > >> include the whitelist plugin or have it have smart defaults in the
> > platform
> > >> implementation and the plugin being able to override them.
> > >>
> > >> I don’t think that thread closed with any conclusions.
> > >>
> > >> Thanks,
> > >> Nikhil
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: Joe Bowser [mailto:bowserj@gmail.com]
> > >> Sent: Thursday, March 12, 2015 11:23 AM
> > >> To: dev
> > >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > >>
> > >> OK, so right now it's just docs? How soon can we get a VOTE thread
> > started
> > >> for 4.0.0?
> > >>
> > >> On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <ag...@chromium.org>
> > >> wrote:
> > >>
> > >> > mobilespec is now working again... Took longer than I would have
> > >> > liked, but did you know that on Android FileReader triggers
> > >> > shouldInterceptRequest() with Blob URLs!?
> > >> >
> > >> > Separate thread is already happening re: whitelists, so once that's
> > >> > figured out, it's just docs afaict.
> > >> >
> > >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian Clelland <
> iclelland@chromium.org
> > >
> > >> > wrote:
> > >> >
> > >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <pu...@gmail.com>
> > wrote:
> > >> > >
> > >> > > > We should start a new whitelist plugin related thread.
> > >> > > >
> > >> > > > Why is a plugin blocking a release? Default (aka no-plugin)
> > >> > > > behavior should be to allow all network requests shouldn't it?
> > >> > >
> > >> > >
> > >> > > Well, that just might be a blacklist then :)
> > >> > >
> > >> > >
> > >> > > > This thread is a
> > >> > > > month long, and not the first discussion of 4.0.0 for Android.
> > >> > > >
> > >> > >
> > >> > > Seriously, though -- the whitelist discussion is much longer than
> > >> > > that,
> > >> > and
> > >> > > this isn't the first time that the default no-network-access
> policy
> > >> > > has been brought up:
> > >> > >
> > >> > > (Here's the first question, from *July*:
> > >> > > http://markmail.org/message/t4vj4saisem2mcgw
> > >> > > Here's where I mentioned what the implemented policy was:
> > >> > > http://markmail.org/message/s4necfnh4hnblpjm
> > >> > > And in another discussion:
> > >> > > http://markmail.org/message/ap7syhqysizmsvrz)
> > >> > >
> > >> > > If we want to reconsider that decision, then we should certainly
> do
> > >> > > so before we cut a release. I think it would be a real problem to
> > >> > > change it afterwards, so let's get it right.
> > >> > >
> > >> > > Also, it's not the plugin itself that's blocking the release, it's
> > >> > > us making sure that we've implemented the core hooks correctly so
> > >> > > that the plugin can actually do its job, and that people who don't
> > >> > > want that particular plugin can make a better one.
> > >> > >
> > >> > > (It is also an issue that a plugin, required for cordova-android
> > >> > > 4.0.0, breaks apps which are also building for cordova-ios 3.8.0.
> > >> > > I'll take a
> > >> > look
> > >> > > at that, and either remove the ios-native portions of the
> whitelist
> > >> > plugin,
> > >> > > or neuter it so that it doesn't interfere with an ios app if it's
> > >> > > not on the unplug-whitelist branch of that repo.)
> > >> > >
> > >> > > Ian
> > >> > >
> > >> > >
> > >> > > > @purplecabbage
> > >> > > > risingj.com
> > >> > > >
> > >> > > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <sh...@gmail.com>
> > wrote:
> > >> > > >
> > >> > > > > legacy-whitelist-plugin should be fixed so that it compiles on
> > >> > > > > cordova-ios@3.8.0. It shouldn't be a problem to fix this at
> > >> > > > > compile
> > >> > or
> > >> > > > > run-time (whichever is applicable here related to the compile
> > >> > > > > error)
> > >> > > > >
> > >> > > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue
> > >> > > > > <dv...@gmail.com>
> > >> > > > wrote:
> > >> > > > > > On 2 March 2015 at 13:37, Joe Bowser <bo...@gmail.com>
> > wrote:
> > >> > > > > >> So, right now the whitelist changes are what's holding up
> the
> > >> > 4.0.0
> > >> > > > > release
> > >> > > > > >> now? Is this really the only thing that's holding up this
> > >> > release?
> > >> > > > > >>
> > >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve <
> > >> > > agrieve@chromium.org>
> > >> > > > > wrote:
> > >> > > > > >>
> > >> > > > > >>> I think we'll also need to finish with the whitelist
> changes
> > >> > > > > >>> &
> > >> > have
> > >> > > > > both
> > >> > > > > >>> the legacy and new-way whitelist plugins released before
> we
> > >> > > > > >>> can
> > >> > do
> > >> > > a
> > >> > > > > 4.0.0
> > >> > > > > >>> release (otherwise you wouldn't be able to write an app
> that
> > >> > > > > >>> hits
> > >> > > the
> > >> > > > > >>> network)
> > >> > > > > >>>
> > >> > > > > >
> > >> > > > > > Just FYI, the whitelist stuff is proving to be a bit of a
> pain
> > >> > point.
> > >> > > > > > I'm using cordova-android@master, and need to install the
> > >> > > > > > legacy-whitelist plugin in order to make network requests.
> > >> > > > > > Once the plugin is installed, everything seems to work.
> > >> > > > > >
> > >> > > > > > The problem is that the legacy-whitelist plugin generates
> > >> > > > > > compile errors with cordova-ios@3.8.0, so now I can't just
> > run
> > >> > > > > > `cordova build`, I need to split the platforms up and
> > >> > > > > > install/uninstall the plugin in between. If someone makes a
> > >> > > > > > dev build for Android and forgets the plugin, it will appear
> > >> > > > > > to build successfully but not actually function properly due
> > to
> > >> the whitelist.
> > >> > > > > >
> > >> > > > > > I know, this is all pre-release, so pain is somewhat
> expected
> > >> > > > > > right now. I'm worried about the case where
> > >> > > > > > cordova-android@4.0.0 is released and cordova-ios@3.8.0 is
> > >> > > > > > still current, and how people
> > >> > can
> > >> > > > > > avoid whitelist breakage there.
> > >> > > > > >
> > >> > > > > > ------------------------------------------------------------
> > >> > ---------
> > >> > > > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > >> > > > > > For additional commands, e-mail:
> dev-help@cordova.apache.org
> > >> > > > > >
> > >> > > > >
> > >> > > > > ------------------------------------------------------------
> > >> > ---------
> > >> > > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > >> > > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > >> > > > >
> > >> > > > >
> > >> > > >
> > >> > >
> > >> >
> > >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Everything's ready afaik (minus upgrade guide, publishing whitelist
plugins, and making it so that the default project template includes
<plugin name="cordova-plugin-whitelist" />). Maybe let's do a RC while we
wait on these things being finished up?
If anyone wants to take on any of these tasks, that would be awesome.
On Mon, Mar 16, 2015 at 4:57 PM, Shazron <sh...@gmail.com> wrote:
> +1 for vote thread, let's get this thing out so people (that are not
> us) can test...
>
>
> On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <bo...@gmail.com> wrote:
> > OK, this is a three month old thread, and we're waiting on a discussion
> > before we release something? I really think we should go to a vote thread
> > now that we have a legacy whitelist plugin and a new style whitelist
> > plugin. We shouldn't keep constantly delaying this release because of
> > what's happening on other platforms, especially since we already
> pluginized
> > the whitelist.
> >
> > Can we please release soon?
> >
> > On Thu, Mar 12, 2015 at 2:20 PM Nikhil Khandelwal <
> nikhilkh@microsoft.com>
> > wrote:
> >
> >> I know we discussed a couple of approaches implementing the default
> >> whitelist policy for Android/iOS - either every app would be required to
> >> include the whitelist plugin or have it have smart defaults in the
> platform
> >> implementation and the plugin being able to override them.
> >>
> >> I don’t think that thread closed with any conclusions.
> >>
> >> Thanks,
> >> Nikhil
> >>
> >>
> >> -----Original Message-----
> >> From: Joe Bowser [mailto:bowserj@gmail.com]
> >> Sent: Thursday, March 12, 2015 11:23 AM
> >> To: dev
> >> Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> >>
> >> OK, so right now it's just docs? How soon can we get a VOTE thread
> started
> >> for 4.0.0?
> >>
> >> On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <ag...@chromium.org>
> >> wrote:
> >>
> >> > mobilespec is now working again... Took longer than I would have
> >> > liked, but did you know that on Android FileReader triggers
> >> > shouldInterceptRequest() with Blob URLs!?
> >> >
> >> > Separate thread is already happening re: whitelists, so once that's
> >> > figured out, it's just docs afaict.
> >> >
> >> > On Mon, Mar 2, 2015 at 10:52 PM, Ian Clelland <iclelland@chromium.org
> >
> >> > wrote:
> >> >
> >> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <pu...@gmail.com>
> wrote:
> >> > >
> >> > > > We should start a new whitelist plugin related thread.
> >> > > >
> >> > > > Why is a plugin blocking a release? Default (aka no-plugin)
> >> > > > behavior should be to allow all network requests shouldn't it?
> >> > >
> >> > >
> >> > > Well, that just might be a blacklist then :)
> >> > >
> >> > >
> >> > > > This thread is a
> >> > > > month long, and not the first discussion of 4.0.0 for Android.
> >> > > >
> >> > >
> >> > > Seriously, though -- the whitelist discussion is much longer than
> >> > > that,
> >> > and
> >> > > this isn't the first time that the default no-network-access policy
> >> > > has been brought up:
> >> > >
> >> > > (Here's the first question, from *July*:
> >> > > http://markmail.org/message/t4vj4saisem2mcgw
> >> > > Here's where I mentioned what the implemented policy was:
> >> > > http://markmail.org/message/s4necfnh4hnblpjm
> >> > > And in another discussion:
> >> > > http://markmail.org/message/ap7syhqysizmsvrz)
> >> > >
> >> > > If we want to reconsider that decision, then we should certainly do
> >> > > so before we cut a release. I think it would be a real problem to
> >> > > change it afterwards, so let's get it right.
> >> > >
> >> > > Also, it's not the plugin itself that's blocking the release, it's
> >> > > us making sure that we've implemented the core hooks correctly so
> >> > > that the plugin can actually do its job, and that people who don't
> >> > > want that particular plugin can make a better one.
> >> > >
> >> > > (It is also an issue that a plugin, required for cordova-android
> >> > > 4.0.0, breaks apps which are also building for cordova-ios 3.8.0.
> >> > > I'll take a
> >> > look
> >> > > at that, and either remove the ios-native portions of the whitelist
> >> > plugin,
> >> > > or neuter it so that it doesn't interfere with an ios app if it's
> >> > > not on the unplug-whitelist branch of that repo.)
> >> > >
> >> > > Ian
> >> > >
> >> > >
> >> > > > @purplecabbage
> >> > > > risingj.com
> >> > > >
> >> > > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <sh...@gmail.com>
> wrote:
> >> > > >
> >> > > > > legacy-whitelist-plugin should be fixed so that it compiles on
> >> > > > > cordova-ios@3.8.0. It shouldn't be a problem to fix this at
> >> > > > > compile
> >> > or
> >> > > > > run-time (whichever is applicable here related to the compile
> >> > > > > error)
> >> > > > >
> >> > > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue
> >> > > > > <dv...@gmail.com>
> >> > > > wrote:
> >> > > > > > On 2 March 2015 at 13:37, Joe Bowser <bo...@gmail.com>
> wrote:
> >> > > > > >> So, right now the whitelist changes are what's holding up the
> >> > 4.0.0
> >> > > > > release
> >> > > > > >> now? Is this really the only thing that's holding up this
> >> > release?
> >> > > > > >>
> >> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve <
> >> > > agrieve@chromium.org>
> >> > > > > wrote:
> >> > > > > >>
> >> > > > > >>> I think we'll also need to finish with the whitelist changes
> >> > > > > >>> &
> >> > have
> >> > > > > both
> >> > > > > >>> the legacy and new-way whitelist plugins released before we
> >> > > > > >>> can
> >> > do
> >> > > a
> >> > > > > 4.0.0
> >> > > > > >>> release (otherwise you wouldn't be able to write an app that
> >> > > > > >>> hits
> >> > > the
> >> > > > > >>> network)
> >> > > > > >>>
> >> > > > > >
> >> > > > > > Just FYI, the whitelist stuff is proving to be a bit of a pain
> >> > point.
> >> > > > > > I'm using cordova-android@master, and need to install the
> >> > > > > > legacy-whitelist plugin in order to make network requests.
> >> > > > > > Once the plugin is installed, everything seems to work.
> >> > > > > >
> >> > > > > > The problem is that the legacy-whitelist plugin generates
> >> > > > > > compile errors with cordova-ios@3.8.0, so now I can't just
> run
> >> > > > > > `cordova build`, I need to split the platforms up and
> >> > > > > > install/uninstall the plugin in between. If someone makes a
> >> > > > > > dev build for Android and forgets the plugin, it will appear
> >> > > > > > to build successfully but not actually function properly due
> to
> >> the whitelist.
> >> > > > > >
> >> > > > > > I know, this is all pre-release, so pain is somewhat expected
> >> > > > > > right now. I'm worried about the case where
> >> > > > > > cordova-android@4.0.0 is released and cordova-ios@3.8.0 is
> >> > > > > > still current, and how people
> >> > can
> >> > > > > > avoid whitelist breakage there.
> >> > > > > >
> >> > > > > > ------------------------------------------------------------
> >> > ---------
> >> > > > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> > > > > > For additional commands, e-mail: dev-help@cordova.apache.org
> >> > > > > >
> >> > > > >
> >> > > > > ------------------------------------------------------------
> >> > ---------
> >> > > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> > > > > For additional commands, e-mail: dev-help@cordova.apache.org
> >> > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Shazron <sh...@gmail.com>.
+1 for vote thread, let's get this thing out so people (that are not
us) can test...
On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <bo...@gmail.com> wrote:
> OK, this is a three month old thread, and we're waiting on a discussion
> before we release something? I really think we should go to a vote thread
> now that we have a legacy whitelist plugin and a new style whitelist
> plugin. We shouldn't keep constantly delaying this release because of
> what's happening on other platforms, especially since we already pluginized
> the whitelist.
>
> Can we please release soon?
>
> On Thu, Mar 12, 2015 at 2:20 PM Nikhil Khandelwal <ni...@microsoft.com>
> wrote:
>
>> I know we discussed a couple of approaches implementing the default
>> whitelist policy for Android/iOS - either every app would be required to
>> include the whitelist plugin or have it have smart defaults in the platform
>> implementation and the plugin being able to override them.
>>
>> I don’t think that thread closed with any conclusions.
>>
>> Thanks,
>> Nikhil
>>
>>
>> -----Original Message-----
>> From: Joe Bowser [mailto:bowserj@gmail.com]
>> Sent: Thursday, March 12, 2015 11:23 AM
>> To: dev
>> Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
>>
>> OK, so right now it's just docs? How soon can we get a VOTE thread started
>> for 4.0.0?
>>
>> On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <ag...@chromium.org>
>> wrote:
>>
>> > mobilespec is now working again... Took longer than I would have
>> > liked, but did you know that on Android FileReader triggers
>> > shouldInterceptRequest() with Blob URLs!?
>> >
>> > Separate thread is already happening re: whitelists, so once that's
>> > figured out, it's just docs afaict.
>> >
>> > On Mon, Mar 2, 2015 at 10:52 PM, Ian Clelland <ic...@chromium.org>
>> > wrote:
>> >
>> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <pu...@gmail.com> wrote:
>> > >
>> > > > We should start a new whitelist plugin related thread.
>> > > >
>> > > > Why is a plugin blocking a release? Default (aka no-plugin)
>> > > > behavior should be to allow all network requests shouldn't it?
>> > >
>> > >
>> > > Well, that just might be a blacklist then :)
>> > >
>> > >
>> > > > This thread is a
>> > > > month long, and not the first discussion of 4.0.0 for Android.
>> > > >
>> > >
>> > > Seriously, though -- the whitelist discussion is much longer than
>> > > that,
>> > and
>> > > this isn't the first time that the default no-network-access policy
>> > > has been brought up:
>> > >
>> > > (Here's the first question, from *July*:
>> > > http://markmail.org/message/t4vj4saisem2mcgw
>> > > Here's where I mentioned what the implemented policy was:
>> > > http://markmail.org/message/s4necfnh4hnblpjm
>> > > And in another discussion:
>> > > http://markmail.org/message/ap7syhqysizmsvrz)
>> > >
>> > > If we want to reconsider that decision, then we should certainly do
>> > > so before we cut a release. I think it would be a real problem to
>> > > change it afterwards, so let's get it right.
>> > >
>> > > Also, it's not the plugin itself that's blocking the release, it's
>> > > us making sure that we've implemented the core hooks correctly so
>> > > that the plugin can actually do its job, and that people who don't
>> > > want that particular plugin can make a better one.
>> > >
>> > > (It is also an issue that a plugin, required for cordova-android
>> > > 4.0.0, breaks apps which are also building for cordova-ios 3.8.0.
>> > > I'll take a
>> > look
>> > > at that, and either remove the ios-native portions of the whitelist
>> > plugin,
>> > > or neuter it so that it doesn't interfere with an ios app if it's
>> > > not on the unplug-whitelist branch of that repo.)
>> > >
>> > > Ian
>> > >
>> > >
>> > > > @purplecabbage
>> > > > risingj.com
>> > > >
>> > > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <sh...@gmail.com> wrote:
>> > > >
>> > > > > legacy-whitelist-plugin should be fixed so that it compiles on
>> > > > > cordova-ios@3.8.0. It shouldn't be a problem to fix this at
>> > > > > compile
>> > or
>> > > > > run-time (whichever is applicable here related to the compile
>> > > > > error)
>> > > > >
>> > > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue
>> > > > > <dv...@gmail.com>
>> > > > wrote:
>> > > > > > On 2 March 2015 at 13:37, Joe Bowser <bo...@gmail.com> wrote:
>> > > > > >> So, right now the whitelist changes are what's holding up the
>> > 4.0.0
>> > > > > release
>> > > > > >> now? Is this really the only thing that's holding up this
>> > release?
>> > > > > >>
>> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve <
>> > > agrieve@chromium.org>
>> > > > > wrote:
>> > > > > >>
>> > > > > >>> I think we'll also need to finish with the whitelist changes
>> > > > > >>> &
>> > have
>> > > > > both
>> > > > > >>> the legacy and new-way whitelist plugins released before we
>> > > > > >>> can
>> > do
>> > > a
>> > > > > 4.0.0
>> > > > > >>> release (otherwise you wouldn't be able to write an app that
>> > > > > >>> hits
>> > > the
>> > > > > >>> network)
>> > > > > >>>
>> > > > > >
>> > > > > > Just FYI, the whitelist stuff is proving to be a bit of a pain
>> > point.
>> > > > > > I'm using cordova-android@master, and need to install the
>> > > > > > legacy-whitelist plugin in order to make network requests.
>> > > > > > Once the plugin is installed, everything seems to work.
>> > > > > >
>> > > > > > The problem is that the legacy-whitelist plugin generates
>> > > > > > compile errors with cordova-ios@3.8.0, so now I can't just run
>> > > > > > `cordova build`, I need to split the platforms up and
>> > > > > > install/uninstall the plugin in between. If someone makes a
>> > > > > > dev build for Android and forgets the plugin, it will appear
>> > > > > > to build successfully but not actually function properly due to
>> the whitelist.
>> > > > > >
>> > > > > > I know, this is all pre-release, so pain is somewhat expected
>> > > > > > right now. I'm worried about the case where
>> > > > > > cordova-android@4.0.0 is released and cordova-ios@3.8.0 is
>> > > > > > still current, and how people
>> > can
>> > > > > > avoid whitelist breakage there.
>> > > > > >
>> > > > > > ------------------------------------------------------------
>> > ---------
>> > > > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> > > > > > For additional commands, e-mail: dev-help@cordova.apache.org
>> > > > > >
>> > > > >
>> > > > > ------------------------------------------------------------
>> > ---------
>> > > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> > > > > For additional commands, e-mail: dev-help@cordova.apache.org
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Joe Bowser <bo...@gmail.com>.
OK, this is a three month old thread, and we're waiting on a discussion
before we release something? I really think we should go to a vote thread
now that we have a legacy whitelist plugin and a new style whitelist
plugin. We shouldn't keep constantly delaying this release because of
what's happening on other platforms, especially since we already pluginized
the whitelist.
Can we please release soon?
On Thu, Mar 12, 2015 at 2:20 PM Nikhil Khandelwal <ni...@microsoft.com>
wrote:
> I know we discussed a couple of approaches implementing the default
> whitelist policy for Android/iOS - either every app would be required to
> include the whitelist plugin or have it have smart defaults in the platform
> implementation and the plugin being able to override them.
>
> I don’t think that thread closed with any conclusions.
>
> Thanks,
> Nikhil
>
>
> -----Original Message-----
> From: Joe Bowser [mailto:bowserj@gmail.com]
> Sent: Thursday, March 12, 2015 11:23 AM
> To: dev
> Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
>
> OK, so right now it's just docs? How soon can we get a VOTE thread started
> for 4.0.0?
>
> On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <ag...@chromium.org>
> wrote:
>
> > mobilespec is now working again... Took longer than I would have
> > liked, but did you know that on Android FileReader triggers
> > shouldInterceptRequest() with Blob URLs!?
> >
> > Separate thread is already happening re: whitelists, so once that's
> > figured out, it's just docs afaict.
> >
> > On Mon, Mar 2, 2015 at 10:52 PM, Ian Clelland <ic...@chromium.org>
> > wrote:
> >
> > > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <pu...@gmail.com> wrote:
> > >
> > > > We should start a new whitelist plugin related thread.
> > > >
> > > > Why is a plugin blocking a release? Default (aka no-plugin)
> > > > behavior should be to allow all network requests shouldn't it?
> > >
> > >
> > > Well, that just might be a blacklist then :)
> > >
> > >
> > > > This thread is a
> > > > month long, and not the first discussion of 4.0.0 for Android.
> > > >
> > >
> > > Seriously, though -- the whitelist discussion is much longer than
> > > that,
> > and
> > > this isn't the first time that the default no-network-access policy
> > > has been brought up:
> > >
> > > (Here's the first question, from *July*:
> > > http://markmail.org/message/t4vj4saisem2mcgw
> > > Here's where I mentioned what the implemented policy was:
> > > http://markmail.org/message/s4necfnh4hnblpjm
> > > And in another discussion:
> > > http://markmail.org/message/ap7syhqysizmsvrz)
> > >
> > > If we want to reconsider that decision, then we should certainly do
> > > so before we cut a release. I think it would be a real problem to
> > > change it afterwards, so let's get it right.
> > >
> > > Also, it's not the plugin itself that's blocking the release, it's
> > > us making sure that we've implemented the core hooks correctly so
> > > that the plugin can actually do its job, and that people who don't
> > > want that particular plugin can make a better one.
> > >
> > > (It is also an issue that a plugin, required for cordova-android
> > > 4.0.0, breaks apps which are also building for cordova-ios 3.8.0.
> > > I'll take a
> > look
> > > at that, and either remove the ios-native portions of the whitelist
> > plugin,
> > > or neuter it so that it doesn't interfere with an ios app if it's
> > > not on the unplug-whitelist branch of that repo.)
> > >
> > > Ian
> > >
> > >
> > > > @purplecabbage
> > > > risingj.com
> > > >
> > > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <sh...@gmail.com> wrote:
> > > >
> > > > > legacy-whitelist-plugin should be fixed so that it compiles on
> > > > > cordova-ios@3.8.0. It shouldn't be a problem to fix this at
> > > > > compile
> > or
> > > > > run-time (whichever is applicable here related to the compile
> > > > > error)
> > > > >
> > > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue
> > > > > <dv...@gmail.com>
> > > > wrote:
> > > > > > On 2 March 2015 at 13:37, Joe Bowser <bo...@gmail.com> wrote:
> > > > > >> So, right now the whitelist changes are what's holding up the
> > 4.0.0
> > > > > release
> > > > > >> now? Is this really the only thing that's holding up this
> > release?
> > > > > >>
> > > > > >> On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve <
> > > agrieve@chromium.org>
> > > > > wrote:
> > > > > >>
> > > > > >>> I think we'll also need to finish with the whitelist changes
> > > > > >>> &
> > have
> > > > > both
> > > > > >>> the legacy and new-way whitelist plugins released before we
> > > > > >>> can
> > do
> > > a
> > > > > 4.0.0
> > > > > >>> release (otherwise you wouldn't be able to write an app that
> > > > > >>> hits
> > > the
> > > > > >>> network)
> > > > > >>>
> > > > > >
> > > > > > Just FYI, the whitelist stuff is proving to be a bit of a pain
> > point.
> > > > > > I'm using cordova-android@master, and need to install the
> > > > > > legacy-whitelist plugin in order to make network requests.
> > > > > > Once the plugin is installed, everything seems to work.
> > > > > >
> > > > > > The problem is that the legacy-whitelist plugin generates
> > > > > > compile errors with cordova-ios@3.8.0, so now I can't just run
> > > > > > `cordova build`, I need to split the platforms up and
> > > > > > install/uninstall the plugin in between. If someone makes a
> > > > > > dev build for Android and forgets the plugin, it will appear
> > > > > > to build successfully but not actually function properly due to
> the whitelist.
> > > > > >
> > > > > > I know, this is all pre-release, so pain is somewhat expected
> > > > > > right now. I'm worried about the case where
> > > > > > cordova-android@4.0.0 is released and cordova-ios@3.8.0 is
> > > > > > still current, and how people
> > can
> > > > > > avoid whitelist breakage there.
> > > > > >
> > > > > > ------------------------------------------------------------
> > ---------
> > > > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > > > >
> > > > >
> > > > > ------------------------------------------------------------
> > ---------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > > >
> > > > >
> > > >
> > >
> >
>
RE: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Nikhil Khandelwal <ni...@microsoft.com>.
I know we discussed a couple of approaches implementing the default whitelist policy for Android/iOS - either every app would be required to include the whitelist plugin or have it have smart defaults in the platform implementation and the plugin being able to override them.
I don’t think that thread closed with any conclusions.
Thanks,
Nikhil
-----Original Message-----
From: Joe Bowser [mailto:bowserj@gmail.com]
Sent: Thursday, March 12, 2015 11:23 AM
To: dev
Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
OK, so right now it's just docs? How soon can we get a VOTE thread started for 4.0.0?
On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <ag...@chromium.org> wrote:
> mobilespec is now working again... Took longer than I would have
> liked, but did you know that on Android FileReader triggers
> shouldInterceptRequest() with Blob URLs!?
>
> Separate thread is already happening re: whitelists, so once that's
> figured out, it's just docs afaict.
>
> On Mon, Mar 2, 2015 at 10:52 PM, Ian Clelland <ic...@chromium.org>
> wrote:
>
> > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <pu...@gmail.com> wrote:
> >
> > > We should start a new whitelist plugin related thread.
> > >
> > > Why is a plugin blocking a release? Default (aka no-plugin)
> > > behavior should be to allow all network requests shouldn't it?
> >
> >
> > Well, that just might be a blacklist then :)
> >
> >
> > > This thread is a
> > > month long, and not the first discussion of 4.0.0 for Android.
> > >
> >
> > Seriously, though -- the whitelist discussion is much longer than
> > that,
> and
> > this isn't the first time that the default no-network-access policy
> > has been brought up:
> >
> > (Here's the first question, from *July*:
> > http://markmail.org/message/t4vj4saisem2mcgw
> > Here's where I mentioned what the implemented policy was:
> > http://markmail.org/message/s4necfnh4hnblpjm
> > And in another discussion:
> > http://markmail.org/message/ap7syhqysizmsvrz)
> >
> > If we want to reconsider that decision, then we should certainly do
> > so before we cut a release. I think it would be a real problem to
> > change it afterwards, so let's get it right.
> >
> > Also, it's not the plugin itself that's blocking the release, it's
> > us making sure that we've implemented the core hooks correctly so
> > that the plugin can actually do its job, and that people who don't
> > want that particular plugin can make a better one.
> >
> > (It is also an issue that a plugin, required for cordova-android
> > 4.0.0, breaks apps which are also building for cordova-ios 3.8.0.
> > I'll take a
> look
> > at that, and either remove the ios-native portions of the whitelist
> plugin,
> > or neuter it so that it doesn't interfere with an ios app if it's
> > not on the unplug-whitelist branch of that repo.)
> >
> > Ian
> >
> >
> > > @purplecabbage
> > > risingj.com
> > >
> > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <sh...@gmail.com> wrote:
> > >
> > > > legacy-whitelist-plugin should be fixed so that it compiles on
> > > > cordova-ios@3.8.0. It shouldn't be a problem to fix this at
> > > > compile
> or
> > > > run-time (whichever is applicable here related to the compile
> > > > error)
> > > >
> > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue
> > > > <dv...@gmail.com>
> > > wrote:
> > > > > On 2 March 2015 at 13:37, Joe Bowser <bo...@gmail.com> wrote:
> > > > >> So, right now the whitelist changes are what's holding up the
> 4.0.0
> > > > release
> > > > >> now? Is this really the only thing that's holding up this
> release?
> > > > >>
> > > > >> On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve <
> > agrieve@chromium.org>
> > > > wrote:
> > > > >>
> > > > >>> I think we'll also need to finish with the whitelist changes
> > > > >>> &
> have
> > > > both
> > > > >>> the legacy and new-way whitelist plugins released before we
> > > > >>> can
> do
> > a
> > > > 4.0.0
> > > > >>> release (otherwise you wouldn't be able to write an app that
> > > > >>> hits
> > the
> > > > >>> network)
> > > > >>>
> > > > >
> > > > > Just FYI, the whitelist stuff is proving to be a bit of a pain
> point.
> > > > > I'm using cordova-android@master, and need to install the
> > > > > legacy-whitelist plugin in order to make network requests.
> > > > > Once the plugin is installed, everything seems to work.
> > > > >
> > > > > The problem is that the legacy-whitelist plugin generates
> > > > > compile errors with cordova-ios@3.8.0, so now I can't just run
> > > > > `cordova build`, I need to split the platforms up and
> > > > > install/uninstall the plugin in between. If someone makes a
> > > > > dev build for Android and forgets the plugin, it will appear
> > > > > to build successfully but not actually function properly due to the whitelist.
> > > > >
> > > > > I know, this is all pre-release, so pain is somewhat expected
> > > > > right now. I'm worried about the case where
> > > > > cordova-android@4.0.0 is released and cordova-ios@3.8.0 is
> > > > > still current, and how people
> can
> > > > > avoid whitelist breakage there.
> > > > >
> > > > > ------------------------------------------------------------
> ---------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > > >
> > > >
> > > > ------------------------------------------------------------
> ---------
> > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Joe Bowser <bo...@gmail.com>.
OK, so right now it's just docs? How soon can we get a VOTE thread started
for 4.0.0?
On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve <ag...@chromium.org> wrote:
> mobilespec is now working again... Took longer than I would have liked, but
> did you know that on Android FileReader triggers shouldInterceptRequest()
> with Blob URLs!?
>
> Separate thread is already happening re: whitelists, so once that's figured
> out, it's just docs afaict.
>
> On Mon, Mar 2, 2015 at 10:52 PM, Ian Clelland <ic...@chromium.org>
> wrote:
>
> > On Mon, Mar 2, 2015 at 6:00 PM, Jesse <pu...@gmail.com> wrote:
> >
> > > We should start a new whitelist plugin related thread.
> > >
> > > Why is a plugin blocking a release? Default (aka no-plugin) behavior
> > > should be to allow all network requests shouldn't it?
> >
> >
> > Well, that just might be a blacklist then :)
> >
> >
> > > This thread is a
> > > month long, and not the first discussion of 4.0.0 for Android.
> > >
> >
> > Seriously, though -- the whitelist discussion is much longer than that,
> and
> > this isn't the first time that the default no-network-access policy has
> > been brought up:
> >
> > (Here's the first question, from *July*:
> > http://markmail.org/message/t4vj4saisem2mcgw
> > Here's where I mentioned what the implemented policy was:
> > http://markmail.org/message/s4necfnh4hnblpjm
> > And in another discussion: http://markmail.org/message/ap7syhqysizmsvrz)
> >
> > If we want to reconsider that decision, then we should certainly do so
> > before we cut a release. I think it would be a real problem to change it
> > afterwards, so let's get it right.
> >
> > Also, it's not the plugin itself that's blocking the release, it's us
> > making sure that we've implemented the core hooks correctly so that the
> > plugin can actually do its job, and that people who don't want that
> > particular plugin can make a better one.
> >
> > (It is also an issue that a plugin, required for cordova-android 4.0.0,
> > breaks apps which are also building for cordova-ios 3.8.0. I'll take a
> look
> > at that, and either remove the ios-native portions of the whitelist
> plugin,
> > or neuter it so that it doesn't interfere with an ios app if it's not on
> > the unplug-whitelist branch of that repo.)
> >
> > Ian
> >
> >
> > > @purplecabbage
> > > risingj.com
> > >
> > > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <sh...@gmail.com> wrote:
> > >
> > > > legacy-whitelist-plugin should be fixed so that it compiles on
> > > > cordova-ios@3.8.0. It shouldn't be a problem to fix this at compile
> or
> > > > run-time (whichever is applicable here related to the compile error)
> > > >
> > > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue <dv...@gmail.com>
> > > wrote:
> > > > > On 2 March 2015 at 13:37, Joe Bowser <bo...@gmail.com> wrote:
> > > > >> So, right now the whitelist changes are what's holding up the
> 4.0.0
> > > > release
> > > > >> now? Is this really the only thing that's holding up this
> release?
> > > > >>
> > > > >> On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve <
> > agrieve@chromium.org>
> > > > wrote:
> > > > >>
> > > > >>> I think we'll also need to finish with the whitelist changes &
> have
> > > > both
> > > > >>> the legacy and new-way whitelist plugins released before we can
> do
> > a
> > > > 4.0.0
> > > > >>> release (otherwise you wouldn't be able to write an app that hits
> > the
> > > > >>> network)
> > > > >>>
> > > > >
> > > > > Just FYI, the whitelist stuff is proving to be a bit of a pain
> point.
> > > > > I'm using cordova-android@master, and need to install the
> > > > > legacy-whitelist plugin in order to make network requests. Once the
> > > > > plugin is installed, everything seems to work.
> > > > >
> > > > > The problem is that the legacy-whitelist plugin generates compile
> > > > > errors with cordova-ios@3.8.0, so now I can't just run `cordova
> > > > > build`, I need to split the platforms up and install/uninstall the
> > > > > plugin in between. If someone makes a dev build for Android and
> > > > > forgets the plugin, it will appear to build successfully but not
> > > > > actually function properly due to the whitelist.
> > > > >
> > > > > I know, this is all pre-release, so pain is somewhat expected right
> > > > > now. I'm worried about the case where cordova-android@4.0.0 is
> > > > > released and cordova-ios@3.8.0 is still current, and how people
> can
> > > > > avoid whitelist breakage there.
> > > > >
> > > > > ------------------------------------------------------------
> ---------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > > >
> > > >
> > > > ------------------------------------------------------------
> ---------
> > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Andrew Grieve <ag...@chromium.org>.
mobilespec is now working again... Took longer than I would have liked, but
did you know that on Android FileReader triggers shouldInterceptRequest()
with Blob URLs!?
Separate thread is already happening re: whitelists, so once that's figured
out, it's just docs afaict.
On Mon, Mar 2, 2015 at 10:52 PM, Ian Clelland <ic...@chromium.org>
wrote:
> On Mon, Mar 2, 2015 at 6:00 PM, Jesse <pu...@gmail.com> wrote:
>
> > We should start a new whitelist plugin related thread.
> >
> > Why is a plugin blocking a release? Default (aka no-plugin) behavior
> > should be to allow all network requests shouldn't it?
>
>
> Well, that just might be a blacklist then :)
>
>
> > This thread is a
> > month long, and not the first discussion of 4.0.0 for Android.
> >
>
> Seriously, though -- the whitelist discussion is much longer than that, and
> this isn't the first time that the default no-network-access policy has
> been brought up:
>
> (Here's the first question, from *July*:
> http://markmail.org/message/t4vj4saisem2mcgw
> Here's where I mentioned what the implemented policy was:
> http://markmail.org/message/s4necfnh4hnblpjm
> And in another discussion: http://markmail.org/message/ap7syhqysizmsvrz)
>
> If we want to reconsider that decision, then we should certainly do so
> before we cut a release. I think it would be a real problem to change it
> afterwards, so let's get it right.
>
> Also, it's not the plugin itself that's blocking the release, it's us
> making sure that we've implemented the core hooks correctly so that the
> plugin can actually do its job, and that people who don't want that
> particular plugin can make a better one.
>
> (It is also an issue that a plugin, required for cordova-android 4.0.0,
> breaks apps which are also building for cordova-ios 3.8.0. I'll take a look
> at that, and either remove the ios-native portions of the whitelist plugin,
> or neuter it so that it doesn't interfere with an ios app if it's not on
> the unplug-whitelist branch of that repo.)
>
> Ian
>
>
> > @purplecabbage
> > risingj.com
> >
> > On Mon, Mar 2, 2015 at 2:02 PM, Shazron <sh...@gmail.com> wrote:
> >
> > > legacy-whitelist-plugin should be fixed so that it compiles on
> > > cordova-ios@3.8.0. It shouldn't be a problem to fix this at compile or
> > > run-time (whichever is applicable here related to the compile error)
> > >
> > > On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue <dv...@gmail.com>
> > wrote:
> > > > On 2 March 2015 at 13:37, Joe Bowser <bo...@gmail.com> wrote:
> > > >> So, right now the whitelist changes are what's holding up the 4.0.0
> > > release
> > > >> now? Is this really the only thing that's holding up this release?
> > > >>
> > > >> On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve <
> agrieve@chromium.org>
> > > wrote:
> > > >>
> > > >>> I think we'll also need to finish with the whitelist changes & have
> > > both
> > > >>> the legacy and new-way whitelist plugins released before we can do
> a
> > > 4.0.0
> > > >>> release (otherwise you wouldn't be able to write an app that hits
> the
> > > >>> network)
> > > >>>
> > > >
> > > > Just FYI, the whitelist stuff is proving to be a bit of a pain point.
> > > > I'm using cordova-android@master, and need to install the
> > > > legacy-whitelist plugin in order to make network requests. Once the
> > > > plugin is installed, everything seems to work.
> > > >
> > > > The problem is that the legacy-whitelist plugin generates compile
> > > > errors with cordova-ios@3.8.0, so now I can't just run `cordova
> > > > build`, I need to split the platforms up and install/uninstall the
> > > > plugin in between. If someone makes a dev build for Android and
> > > > forgets the plugin, it will appear to build successfully but not
> > > > actually function properly due to the whitelist.
> > > >
> > > > I know, this is all pre-release, so pain is somewhat expected right
> > > > now. I'm worried about the case where cordova-android@4.0.0 is
> > > > released and cordova-ios@3.8.0 is still current, and how people can
> > > > avoid whitelist breakage there.
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > For additional commands, e-mail: dev-help@cordova.apache.org
> > >
> > >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Ian Clelland <ic...@chromium.org>.
On Mon, Mar 2, 2015 at 6:00 PM, Jesse <pu...@gmail.com> wrote:
> We should start a new whitelist plugin related thread.
>
> Why is a plugin blocking a release? Default (aka no-plugin) behavior
> should be to allow all network requests shouldn't it?
Well, that just might be a blacklist then :)
> This thread is a
> month long, and not the first discussion of 4.0.0 for Android.
>
Seriously, though -- the whitelist discussion is much longer than that, and
this isn't the first time that the default no-network-access policy has
been brought up:
(Here's the first question, from *July*:
http://markmail.org/message/t4vj4saisem2mcgw
Here's where I mentioned what the implemented policy was:
http://markmail.org/message/s4necfnh4hnblpjm
And in another discussion: http://markmail.org/message/ap7syhqysizmsvrz)
If we want to reconsider that decision, then we should certainly do so
before we cut a release. I think it would be a real problem to change it
afterwards, so let's get it right.
Also, it's not the plugin itself that's blocking the release, it's us
making sure that we've implemented the core hooks correctly so that the
plugin can actually do its job, and that people who don't want that
particular plugin can make a better one.
(It is also an issue that a plugin, required for cordova-android 4.0.0,
breaks apps which are also building for cordova-ios 3.8.0. I'll take a look
at that, and either remove the ios-native portions of the whitelist plugin,
or neuter it so that it doesn't interfere with an ios app if it's not on
the unplug-whitelist branch of that repo.)
Ian
> @purplecabbage
> risingj.com
>
> On Mon, Mar 2, 2015 at 2:02 PM, Shazron <sh...@gmail.com> wrote:
>
> > legacy-whitelist-plugin should be fixed so that it compiles on
> > cordova-ios@3.8.0. It shouldn't be a problem to fix this at compile or
> > run-time (whichever is applicable here related to the compile error)
> >
> > On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue <dv...@gmail.com>
> wrote:
> > > On 2 March 2015 at 13:37, Joe Bowser <bo...@gmail.com> wrote:
> > >> So, right now the whitelist changes are what's holding up the 4.0.0
> > release
> > >> now? Is this really the only thing that's holding up this release?
> > >>
> > >> On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve <ag...@chromium.org>
> > wrote:
> > >>
> > >>> I think we'll also need to finish with the whitelist changes & have
> > both
> > >>> the legacy and new-way whitelist plugins released before we can do a
> > 4.0.0
> > >>> release (otherwise you wouldn't be able to write an app that hits the
> > >>> network)
> > >>>
> > >
> > > Just FYI, the whitelist stuff is proving to be a bit of a pain point.
> > > I'm using cordova-android@master, and need to install the
> > > legacy-whitelist plugin in order to make network requests. Once the
> > > plugin is installed, everything seems to work.
> > >
> > > The problem is that the legacy-whitelist plugin generates compile
> > > errors with cordova-ios@3.8.0, so now I can't just run `cordova
> > > build`, I need to split the platforms up and install/uninstall the
> > > plugin in between. If someone makes a dev build for Android and
> > > forgets the plugin, it will appear to build successfully but not
> > > actually function properly due to the whitelist.
> > >
> > > I know, this is all pre-release, so pain is somewhat expected right
> > > now. I'm worried about the case where cordova-android@4.0.0 is
> > > released and cordova-ios@3.8.0 is still current, and how people can
> > > avoid whitelist breakage there.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > For additional commands, e-mail: dev-help@cordova.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Andrew Grieve <ag...@chromium.org>.
I'm just about finished working through fixing mobilespec to work with the
latest whitelist changes. Once I've figured out things, I'll kick up a
discuss about how it works. Right now, on master, all network requests are
blocked without a plugin enabling them. But I think we should discuss
whether we want to change that default, and the merits of installing the
whitelist plugin by default.
On Mon, Mar 2, 2015 at 6:00 PM, Jesse <pu...@gmail.com> wrote:
> We should start a new whitelist plugin related thread.
>
> Why is a plugin blocking a release? Default (aka no-plugin) behavior
> should be to allow all network requests shouldn't it? This thread is a
> month long, and not the first discussion of 4.0.0 for Android.
>
> @purplecabbage
> risingj.com
>
> On Mon, Mar 2, 2015 at 2:02 PM, Shazron <sh...@gmail.com> wrote:
>
> > legacy-whitelist-plugin should be fixed so that it compiles on
> > cordova-ios@3.8.0. It shouldn't be a problem to fix this at compile or
> > run-time (whichever is applicable here related to the compile error)
> >
> > On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue <dv...@gmail.com>
> wrote:
> > > On 2 March 2015 at 13:37, Joe Bowser <bo...@gmail.com> wrote:
> > >> So, right now the whitelist changes are what's holding up the 4.0.0
> > release
> > >> now? Is this really the only thing that's holding up this release?
> > >>
> > >> On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve <ag...@chromium.org>
> > wrote:
> > >>
> > >>> I think we'll also need to finish with the whitelist changes & have
> > both
> > >>> the legacy and new-way whitelist plugins released before we can do a
> > 4.0.0
> > >>> release (otherwise you wouldn't be able to write an app that hits the
> > >>> network)
> > >>>
> > >
> > > Just FYI, the whitelist stuff is proving to be a bit of a pain point.
> > > I'm using cordova-android@master, and need to install the
> > > legacy-whitelist plugin in order to make network requests. Once the
> > > plugin is installed, everything seems to work.
> > >
> > > The problem is that the legacy-whitelist plugin generates compile
> > > errors with cordova-ios@3.8.0, so now I can't just run `cordova
> > > build`, I need to split the platforms up and install/uninstall the
> > > plugin in between. If someone makes a dev build for Android and
> > > forgets the plugin, it will appear to build successfully but not
> > > actually function properly due to the whitelist.
> > >
> > > I know, this is all pre-release, so pain is somewhat expected right
> > > now. I'm worried about the case where cordova-android@4.0.0 is
> > > released and cordova-ios@3.8.0 is still current, and how people can
> > > avoid whitelist breakage there.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > For additional commands, e-mail: dev-help@cordova.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Jesse <pu...@gmail.com>.
We should start a new whitelist plugin related thread.
Why is a plugin blocking a release? Default (aka no-plugin) behavior
should be to allow all network requests shouldn't it? This thread is a
month long, and not the first discussion of 4.0.0 for Android.
@purplecabbage
risingj.com
On Mon, Mar 2, 2015 at 2:02 PM, Shazron <sh...@gmail.com> wrote:
> legacy-whitelist-plugin should be fixed so that it compiles on
> cordova-ios@3.8.0. It shouldn't be a problem to fix this at compile or
> run-time (whichever is applicable here related to the compile error)
>
> On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue <dv...@gmail.com> wrote:
> > On 2 March 2015 at 13:37, Joe Bowser <bo...@gmail.com> wrote:
> >> So, right now the whitelist changes are what's holding up the 4.0.0
> release
> >> now? Is this really the only thing that's holding up this release?
> >>
> >> On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve <ag...@chromium.org>
> wrote:
> >>
> >>> I think we'll also need to finish with the whitelist changes & have
> both
> >>> the legacy and new-way whitelist plugins released before we can do a
> 4.0.0
> >>> release (otherwise you wouldn't be able to write an app that hits the
> >>> network)
> >>>
> >
> > Just FYI, the whitelist stuff is proving to be a bit of a pain point.
> > I'm using cordova-android@master, and need to install the
> > legacy-whitelist plugin in order to make network requests. Once the
> > plugin is installed, everything seems to work.
> >
> > The problem is that the legacy-whitelist plugin generates compile
> > errors with cordova-ios@3.8.0, so now I can't just run `cordova
> > build`, I need to split the platforms up and install/uninstall the
> > plugin in between. If someone makes a dev build for Android and
> > forgets the plugin, it will appear to build successfully but not
> > actually function properly due to the whitelist.
> >
> > I know, this is all pre-release, so pain is somewhat expected right
> > now. I'm worried about the case where cordova-android@4.0.0 is
> > released and cordova-ios@3.8.0 is still current, and how people can
> > avoid whitelist breakage there.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Joe Bowser <bo...@gmail.com>.
Why do we need both the legacy and new-style whitelists released before we
do a cordova-android 4.0.x release? Is there something that the new-style
whitelist needs to change in the API that would force us to do a 5.0.x
release?
On Mon Mar 02 2015 at 2:04:59 PM Shazron <sh...@gmail.com> wrote:
> legacy-whitelist-plugin should be fixed so that it compiles on
> cordova-ios@3.8.0. It shouldn't be a problem to fix this at compile or
> run-time (whichever is applicable here related to the compile error)
>
> On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue <dv...@gmail.com> wrote:
> > On 2 March 2015 at 13:37, Joe Bowser <bo...@gmail.com> wrote:
> >> So, right now the whitelist changes are what's holding up the 4.0.0
> release
> >> now? Is this really the only thing that's holding up this release?
> >>
> >> On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve <ag...@chromium.org>
> wrote:
> >>
> >>> I think we'll also need to finish with the whitelist changes & have
> both
> >>> the legacy and new-way whitelist plugins released before we can do a
> 4.0.0
> >>> release (otherwise you wouldn't be able to write an app that hits the
> >>> network)
> >>>
> >
> > Just FYI, the whitelist stuff is proving to be a bit of a pain point.
> > I'm using cordova-android@master, and need to install the
> > legacy-whitelist plugin in order to make network requests. Once the
> > plugin is installed, everything seems to work.
> >
> > The problem is that the legacy-whitelist plugin generates compile
> > errors with cordova-ios@3.8.0, so now I can't just run `cordova
> > build`, I need to split the platforms up and install/uninstall the
> > plugin in between. If someone makes a dev build for Android and
> > forgets the plugin, it will appear to build successfully but not
> > actually function properly due to the whitelist.
> >
> > I know, this is all pre-release, so pain is somewhat expected right
> > now. I'm worried about the case where cordova-android@4.0.0 is
> > released and cordova-ios@3.8.0 is still current, and how people can
> > avoid whitelist breakage there.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Shazron <sh...@gmail.com>.
legacy-whitelist-plugin should be fixed so that it compiles on
cordova-ios@3.8.0. It shouldn't be a problem to fix this at compile or
run-time (whichever is applicable here related to the compile error)
On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue <dv...@gmail.com> wrote:
> On 2 March 2015 at 13:37, Joe Bowser <bo...@gmail.com> wrote:
>> So, right now the whitelist changes are what's holding up the 4.0.0 release
>> now? Is this really the only thing that's holding up this release?
>>
>> On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve <ag...@chromium.org> wrote:
>>
>>> I think we'll also need to finish with the whitelist changes & have both
>>> the legacy and new-way whitelist plugins released before we can do a 4.0.0
>>> release (otherwise you wouldn't be able to write an app that hits the
>>> network)
>>>
>
> Just FYI, the whitelist stuff is proving to be a bit of a pain point.
> I'm using cordova-android@master, and need to install the
> legacy-whitelist plugin in order to make network requests. Once the
> plugin is installed, everything seems to work.
>
> The problem is that the legacy-whitelist plugin generates compile
> errors with cordova-ios@3.8.0, so now I can't just run `cordova
> build`, I need to split the platforms up and install/uninstall the
> plugin in between. If someone makes a dev build for Android and
> forgets the plugin, it will appear to build successfully but not
> actually function properly due to the whitelist.
>
> I know, this is all pre-release, so pain is somewhat expected right
> now. I'm worried about the case where cordova-android@4.0.0 is
> released and cordova-ios@3.8.0 is still current, and how people can
> avoid whitelist breakage there.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Darryl Pogue <dv...@gmail.com>.
On 2 March 2015 at 13:37, Joe Bowser <bo...@gmail.com> wrote:
> So, right now the whitelist changes are what's holding up the 4.0.0 release
> now? Is this really the only thing that's holding up this release?
>
> On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve <ag...@chromium.org> wrote:
>
>> I think we'll also need to finish with the whitelist changes & have both
>> the legacy and new-way whitelist plugins released before we can do a 4.0.0
>> release (otherwise you wouldn't be able to write an app that hits the
>> network)
>>
Just FYI, the whitelist stuff is proving to be a bit of a pain point.
I'm using cordova-android@master, and need to install the
legacy-whitelist plugin in order to make network requests. Once the
plugin is installed, everything seems to work.
The problem is that the legacy-whitelist plugin generates compile
errors with cordova-ios@3.8.0, so now I can't just run `cordova
build`, I need to split the platforms up and install/uninstall the
plugin in between. If someone makes a dev build for Android and
forgets the plugin, it will appear to build successfully but not
actually function properly due to the whitelist.
I know, this is all pre-release, so pain is somewhat expected right
now. I'm worried about the case where cordova-android@4.0.0 is
released and cordova-ios@3.8.0 is still current, and how people can
avoid whitelist breakage there.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Joe Bowser <bo...@gmail.com>.
So, right now the whitelist changes are what's holding up the 4.0.0 release
now? Is this really the only thing that's holding up this release?
On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve <ag...@chromium.org> wrote:
> I think we'll also need to finish with the whitelist changes & have both
> the legacy and new-way whitelist plugins released before we can do a 4.0.0
> release (otherwise you wouldn't be able to write an app that hits the
> network)
>
> On Wed, Feb 25, 2015 at 12:41 PM, Andrew Grieve <ag...@chromium.org>
> wrote:
>
> > Alright, branch is merged in and I fixed a couple other things I noticed
> > broken in the native test app (back button & background color). I've also
> > gone ahead with removing the LinearLayout and confirmed that both maps
> and
> > nativepagetransitions plugins are not affected at all.
> >
> > Might as well add in the key signing tweaks that have been agreed upon. I
> > can do that today.
> >
> > Would like your input on:
> > Deprecated show/hide customView
> > - At first I thought this was just view twiddling for video on old
> > androids that was not meant to be exposed
> > - I see now though that there is custom back button logic for it
> > - and that the maps plugin uses it to go fullscreen
> > - so I'm thinking let's not deprecate.
> >
> > We're also still waiting for a tools release to happen that will set
> 3.7.1
> > as the default platform (don't have cycles to do it this week myself)
> >
> >
> >
> >
> >
> >
> >
> > On Tue, Feb 24, 2015 at 7:39 PM, Joe Bowser <bo...@gmail.com> wrote:
> >
> >> I can't come up with any. Let's not delay the release on that. So,
> other
> >> than the platform docs, we should be good to go, right?
> >>
> >> On Thu Feb 19 2015 at 11:42:40 AM Andrew Grieve <ag...@chromium.org>
> >> wrote:
> >>
> >> > Thanks for the quick review. I'll have a look through your comments.
> >> Now's
> >> > a good time to change names, so feel free to suggest alternatives.
> >> >
> >> > On Thu, Feb 19, 2015 at 1:32 PM, Joe Bowser <bo...@gmail.com>
> wrote:
> >> >
> >> > > I've done a quick read of the pull request and left some comments in
> >> > > there. I'm in Salt Lake this week, so I haven't had a chance to
> >> really
> >> > > test this pull request yet, but while I'm not in love with the
> naming
> >> > > convention used, it looks mostly OK.
> >> > >
> >> > > On Thu Feb 19 2015 at 11:19:51 AM Andrew Grieve <
> agrieve@chromium.org
> >> >
> >> > > wrote:
> >> > >
> >> > > > They would need to do similar to the PR for xwalk. It's actually a
> >> lot
> >> > > less
> >> > > > code now to implement a custom engine, so I think it makes
> geckoview
> >> > much
> >> > > > more feasible.
> >> > > >
> >> > > > The embedded case (I'm guessing you mean layout xml?) is one of
> the
> >> > unit
> >> > > > tests. Have a look here:
> >> > > > https://github.com/agrieve/cordova-android/blob/engine/
> >> > > > test/src/org/apache/cordova/test/CordovaWebViewTestActivity.java
> >> > > >
> >> > > > If we delete LinearLayout, we just pass the WebView itself to
> >> > > > setContentView(). It will still have a FrameLayout as a parent
> >> (which
> >> > is
> >> > > > the unchangeable root View of all Activities)
> >> > > >
> >> > > > For reference, here's now NativePageTransitions inserts their own
> >> > Layout:
> >> > > > https://github.com/Telerik-Verified-Plugins/
> >> > NativePageTransitions/blob/
> >> > > > master/src/android/NativePageTransitions.java#L74
> >> > > >
> >> > > > On Thu, Feb 19, 2015 at 1:01 PM, Joe Bowser <bo...@gmail.com>
> >> wrote:
> >> > > >
> >> > > > > So, I know that XWalk is the only production-ready WebView right
> >> now,
> >> > > but
> >> > > > > what would other third party providers need to implement/change
> >> for
> >> > > their
> >> > > > > webviews to work? Also, I'm not clear how the embedded
> >> CordovaWebView
> >> > > use
> >> > > > > case would work in this scenario. If we delete the
> LinearLayout,
> >> > what
> >> > > do
> >> > > > > we attach our view for the default use case?
> >> > > > >
> >> > > > > On Thu Feb 19 2015 at 10:39:59 AM Andrew Grieve <
> >> > agrieve@chromium.org>
> >> > > > > wrote:
> >> > > > >
> >> > > > > > I've finished playing with third-party plugins. If anyone else
> >> > wants
> >> > > to
> >> > > > > > have fun with them, use --thirdpartyplugins in
> >> createmobilespec.js,
> >> > > and
> >> > > > > > then find the manual test for them.
> >> > > > > >
> >> > > > > > TLDR - most compiled/worked fine. Two that interacted with
> >> Views a
> >> > > lot
> >> > > > > had
> >> > > > > > lots of compile errors, but in the end I don't think there's a
> >> good
> >> > > way
> >> > > > > to
> >> > > > > > fix them on our end.
> >> > > > > >
> >> > > > > > I've also taken some time to try and eliminate copy & paste
> >> between
> >> > > > > > AndroidWebView and XWalkWebView. I'd love to get some feedback
> >> on
> >> > the
> >> > > > > > changes (and hopefully get them in). More info /w PRs here:
> >> > > > > >
> >> > > > > > https://issues.apache.org/jira/browse/CB-8510
> >> > > > > >
> >> > > > > > Another thing that came out of looking at these plugins is
> that
> >> > they
> >> > > > add
> >> > > > > in
> >> > > > > > their own Layout, or have logic to handle various parent
> layout.
> >> > > So...
> >> > > > I
> >> > > > > > think we'd be fine (and should) delete our top-level
> >> LinearLayout.
> >> > > > > Plugins
> >> > > > > > and embedders can easily add in layouts if they want.
> >> > > > > >
> >> > > > > > Still waiting on a tools release for 3.7.1.
> >> > > > > > Still need to update platform docs for 4.0.0
> >> > > > > >
> >> > > > > > But... I think that's it! (unless I'm missing something)
> >> > > > > >
> >> > > > > >
> >> > > > > >
> >> > > > > > On Wed, Feb 4, 2015 at 10:11 PM, Ian Clelland <
> >> > > iclelland@chromium.org>
> >> > > > > > wrote:
> >> > > > > >
> >> > > > > > > On Wed, Feb 4, 2015 at 7:58 PM, Fu, Junwei <
> >> junwei.fu@intel.com>
> >> > > > > wrote:
> >> > > > > > >
> >> > > > > > > > What are the test cases don't work for Crosswalk? I'd like
> >> to
> >> > do
> >> > > > > > whatever
> >> > > > > > > > I can to help.
> >> > > > > > > >
> >> > > > > > >
> >> > > > > > > So, Crosswalk 10 (and, I believe, 11) work great for
> Cordova.
> >> > There
> >> > > > is
> >> > > > > a
> >> > > > > > > failing test in File Transfer, though, that appears to be a
> >> > > threading
> >> > > > > > issue
> >> > > > > > > causing a NPE deep inside of OkHTTP.
> >> > > > > > >
> >> > > > > > > It's very similar to a bug we solved almost a year ago:
> >> > > > > > > https://issues.apache.org/jira/browse/CB-6378, except that
> >> it's
> >> > > > > > happening
> >> > > > > > > in a different method, and while the last time, the cause
> was
> >> > > obvious
> >> > > > > > > (connections opened on one thread, and closed on another),
> >> this
> >> > > time
> >> > > > > > > everything *should* be happening on the same thread.
> >> > > > > > >
> >> > > > > > > I've just created
> >> https://issues.apache.org/jira/browse/CB-8431
> >> > if
> >> > > > you
> >> > > > > > > want
> >> > > > > > > to take a look. I haven't had the chance to really dig into
> >> where
> >> > > the
> >> > > > > > error
> >> > > > > > > is coming from yet, but I'll take a closer look tomorrow.
> >> > > > > > >
> >> > > > > > > Ian
> >> > > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > >
> >> > > > > > > > -----Original Message-----
> >> > > > > > > > From: agrieve@google.com [mailto:agrieve@google.com] On
> >> Behalf
> >> > > Of
> >> > > > > > Andrew
> >> > > > > > > > Grieve
> >> > > > > > > > Sent: Thursday, February 05, 2015 3:43 AM
> >> > > > > > > > To: dev
> >> > > > > > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> >> > > > > > > >
> >> > > > > > > > On Wed, Feb 4, 2015 at 2:25 PM, Joe Bowser <
> >> bowserj@gmail.com>
> >> > > > > wrote:
> >> > > > > > > >
> >> > > > > > > > > OK, so since we're using e-mail to do a sprint, here's
> >> where
> >> > I
> >> > > > > think
> >> > > > > > > > > we're at so far.
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > - Ian's been working on getting crosswalk 10 working and
> >> is
> >> > > > hitting
> >> > > > > > > > > some FileTransfer crash issues.
> >> > > > > > > > > (Apparently Crosswalk-11 works? Ian, what's happening
> with
> >> > > this?)
> >> > > > > > > > > - Mobilespec really should be passing, let's investigate
> >> and
> >> > > fix
> >> > > > > > > > > plugins / tests if they are the issues.
> >> > > > > > > > >
> >> > > > > > > > > Has anyone done this yet?
> >> > > > > > > > >
> >> > > > > > > > Don't think so.
> >> > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > - Android's update script is not preserving artifacts of
> >> > > > <framework
> >> > > > > > > > > type="gradleReference"/> (hoping to work on this today)
> >> > > > > > > > >
> >> > > > > > > > > Did you get around to doing this?
> >> > > > > > > > >
> >> > > > > > > > Done!
> >> > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > - *LinearLayoutSoftKeyboardDetect - delete it!*
> >> > > > > > > > >
> >> > > > > > > > > It's apparently already gone on Master.
> >> > > > > > > > >
> >> > > > > > > > Done!
> >> > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > - Ensure that our gradle support is to the point where
> >> > plugins
> >> > > > can
> >> > > > > > > > > target android-sdk-provided libs (play services &
> -compat
> >> > libs)
> >> > > > > > > > >
> >> > > > > > > > > What needs to be done here? Is there a JIRA issue for
> >> this?
> >> > > > > > > > >
> >> > > > > > > > Done! Needs a tools release.
> >> > > > > > > > Haven't tested how bad the error messages are if you don't
> >> have
> >> > > > them
> >> > > > > > > > installed though. That seems like a can-be-done-after
> thing
> >> > (e.g.
> >> > > > If
> >> > > > > > the
> >> > > > > > > > error message sucks, we could: before build, pre-scan for
> >> > > existence
> >> > > > > of
> >> > > > > > > them
> >> > > > > > > > in the SDK directly.)
> >> > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > - Make CordovaActivity not implement CordovaInterface,
> but
> >> > > > instead
> >> > > > > > > > > provide CordovaInterface via an inner class (to solidify
> >> that
> >> > > you
> >> > > > > > > > > can't cast the activity to CordovaInterface and expect
> >> that
> >> > to
> >> > > > > work -
> >> > > > > > > > > some used to do this but I think we've cleaned it all up
> >> now)
> >> > > > > > > > >
> >> > > > > > > > done!
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > I know there's a vote pending for 3.7.1, and we still
> need
> >> > > people
> >> > > > > to
> >> > > > > > > > > vote on that (I'll get around to it before the voting
> >> period
> >> > > > ends),
> >> > > > > > > > > but I'm wondering how close we are to getting a 4.0.0
> vote
> >> > > > > happening?
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > > I'd like to do a bit more work with playing with third
> party
> >> > > > plugins
> >> > > > > in
> >> > > > > > > > mobilespec before we vote to release. Right now many of
> them
> >> > > don't
> >> > > > > > > compile,
> >> > > > > > > > and I think the main reason is that CordovaWebView is not
> a
> >> > view.
> >> > > > > > > Planning
> >> > > > > > > > on writing up a report of how many popular plugins break,
> >> and
> >> > how
> >> > > > bad
> >> > > > > > it
> >> > > > > > > is
> >> > > > > > > > to fix them.
> >> > > > > > > >
> >> > > > > > > > Also need to update embedder's guide in docs (maybe create
> >> an
> >> > > > > > > android-4.0.0
> >> > > > > > > > branch?)
> >> > > > > > > > Also need to do a plugins release for splashscreen (will
> >> start
> >> > > > > > shortly).
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > On Tue Feb 03 2015 at 7:20:29 PM Fu, Junwei <
> >> > > junwei.fu@intel.com
> >> > > > >
> >> > > > > > > wrote:
> >> > > > > > > > >
> >> > > > > > > > > > Crosswalk engine have been tested in mobile-spec and
> >> owned
> >> > > > > > > > > > functionality tests with Crosswalk-11, and it was our
> >> plan
> >> > to
> >> > > > be
> >> > > > > > > > > > released. I request a PR in here
> >> > > > > > > > > > https://github.com/MobileChromeApps/cordova-
> >> > > > > > > > > > crosswalk-engine/pull/17.
> >> > > > > > > > > >
> >> > > > > > > > > > Thanks,
> >> > > > > > > > > > Junwei.
> >> > > > > > > > > >
> >> > > > > > > > > > -----Original Message-----
> >> > > > > > > > > > From: agrieve@google.com [mailto:agrieve@google.com]
> On
> >> > > Behalf
> >> > > > > Of
> >> > > > > > > > > > Andrew Grieve
> >> > > > > > > > > > Sent: Wednesday, February 04, 2015 3:53 AM
> >> > > > > > > > > > To: dev
> >> > > > > > > > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> >> > > > > > > > > >
> >> > > > > > > > > > And, of course, for your FileTransfer change :P
> >> > > > > > > > > >
> >> > > > > > > > > > I just last night finished up the fixing of <framework
> >> > > > > > custom=false>
> >> > > > > > > > > > for gradle-based builds, so we're certainly nearing
> the
> >> > > finish
> >> > > > > line
> >> > > > > > > > > > for 4.0.0 known issues.
> >> > > > > > > > > >
> >> > > > > > > > > > Of the list from before, only remaining are:
> >> > > > > > > > > >
> >> > > > > > > > > > - Ian's been working on getting crosswalk 10 working
> >> and is
> >> > > > > hitting
> >> > > > > > > > > > some FileTransfer crash issues.
> >> > > > > > > > > > - Mobilespec really should be passing, let's
> investigate
> >> > and
> >> > > > fix
> >> > > > > > > > > > plugins
> >> > > > > > > > > /
> >> > > > > > > > > > tests if they are the issues.
> >> > > > > > > > > >
> >> > > > > > > > > >
> >> > > > > > > > > >
> >> > > > > > > > > >
> >> > > > > > > > > > On Tue, Feb 3, 2015 at 2:46 PM, Darryl Pogue <
> >> > > > > dvpdiner2@gmail.com>
> >> > > > > > > > > wrote:
> >> > > > > > > > > >
> >> > > > > > > > > > > I just remembered that there should be a plugins
> >> release
> >> > > > before
> >> > > > > > > > > > > Android 4.0.0 goes out because of the moving of the
> >> > > > > splashscreen
> >> > > > > > > > > > > logic out of the platform and into the plugin. As
> far
> >> as
> >> > I
> >> > > > can
> >> > > > > > > > > > > tell, that's still unreleased.
> >> > > > > > > > > > >
> >> > > > > > > > > > >
> >> > > ------------------------------------------------------------
> >> > > > > > ------
> >> > > > > > > > > > > --- To unsubscribe, e-mail: dev-unsubscribe@cordova.
> >> > > > apache.org
> >> > > > > > > > > > > For additional commands, e-mail:
> >> > > dev-help@cordova.apache.org
> >> > > > > > > > > > >
> >> > > > > > > > > > >
> >> > > > > > > > > >
> >> > > > > > > > > > ------------------------------
> >> > ------------------------------
> >> > > > > > --------
> >> > > > > > > > > > - To unsubscribe, e-mail: dev-unsubscribe@cordova.
> >> > apache.org
> >> > > > > > > > > > For additional commands, e-mail:
> >> > dev-help@cordova.apache.org
> >> > > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Andrew Grieve <ag...@chromium.org>.
I think we'll also need to finish with the whitelist changes & have both
the legacy and new-way whitelist plugins released before we can do a 4.0.0
release (otherwise you wouldn't be able to write an app that hits the
network)
On Wed, Feb 25, 2015 at 12:41 PM, Andrew Grieve <ag...@chromium.org>
wrote:
> Alright, branch is merged in and I fixed a couple other things I noticed
> broken in the native test app (back button & background color). I've also
> gone ahead with removing the LinearLayout and confirmed that both maps and
> nativepagetransitions plugins are not affected at all.
>
> Might as well add in the key signing tweaks that have been agreed upon. I
> can do that today.
>
> Would like your input on:
> Deprecated show/hide customView
> - At first I thought this was just view twiddling for video on old
> androids that was not meant to be exposed
> - I see now though that there is custom back button logic for it
> - and that the maps plugin uses it to go fullscreen
> - so I'm thinking let's not deprecate.
>
> We're also still waiting for a tools release to happen that will set 3.7.1
> as the default platform (don't have cycles to do it this week myself)
>
>
>
>
>
>
>
> On Tue, Feb 24, 2015 at 7:39 PM, Joe Bowser <bo...@gmail.com> wrote:
>
>> I can't come up with any. Let's not delay the release on that. So, other
>> than the platform docs, we should be good to go, right?
>>
>> On Thu Feb 19 2015 at 11:42:40 AM Andrew Grieve <ag...@chromium.org>
>> wrote:
>>
>> > Thanks for the quick review. I'll have a look through your comments.
>> Now's
>> > a good time to change names, so feel free to suggest alternatives.
>> >
>> > On Thu, Feb 19, 2015 at 1:32 PM, Joe Bowser <bo...@gmail.com> wrote:
>> >
>> > > I've done a quick read of the pull request and left some comments in
>> > > there. I'm in Salt Lake this week, so I haven't had a chance to
>> really
>> > > test this pull request yet, but while I'm not in love with the naming
>> > > convention used, it looks mostly OK.
>> > >
>> > > On Thu Feb 19 2015 at 11:19:51 AM Andrew Grieve <agrieve@chromium.org
>> >
>> > > wrote:
>> > >
>> > > > They would need to do similar to the PR for xwalk. It's actually a
>> lot
>> > > less
>> > > > code now to implement a custom engine, so I think it makes geckoview
>> > much
>> > > > more feasible.
>> > > >
>> > > > The embedded case (I'm guessing you mean layout xml?) is one of the
>> > unit
>> > > > tests. Have a look here:
>> > > > https://github.com/agrieve/cordova-android/blob/engine/
>> > > > test/src/org/apache/cordova/test/CordovaWebViewTestActivity.java
>> > > >
>> > > > If we delete LinearLayout, we just pass the WebView itself to
>> > > > setContentView(). It will still have a FrameLayout as a parent
>> (which
>> > is
>> > > > the unchangeable root View of all Activities)
>> > > >
>> > > > For reference, here's now NativePageTransitions inserts their own
>> > Layout:
>> > > > https://github.com/Telerik-Verified-Plugins/
>> > NativePageTransitions/blob/
>> > > > master/src/android/NativePageTransitions.java#L74
>> > > >
>> > > > On Thu, Feb 19, 2015 at 1:01 PM, Joe Bowser <bo...@gmail.com>
>> wrote:
>> > > >
>> > > > > So, I know that XWalk is the only production-ready WebView right
>> now,
>> > > but
>> > > > > what would other third party providers need to implement/change
>> for
>> > > their
>> > > > > webviews to work? Also, I'm not clear how the embedded
>> CordovaWebView
>> > > use
>> > > > > case would work in this scenario. If we delete the LinearLayout,
>> > what
>> > > do
>> > > > > we attach our view for the default use case?
>> > > > >
>> > > > > On Thu Feb 19 2015 at 10:39:59 AM Andrew Grieve <
>> > agrieve@chromium.org>
>> > > > > wrote:
>> > > > >
>> > > > > > I've finished playing with third-party plugins. If anyone else
>> > wants
>> > > to
>> > > > > > have fun with them, use --thirdpartyplugins in
>> createmobilespec.js,
>> > > and
>> > > > > > then find the manual test for them.
>> > > > > >
>> > > > > > TLDR - most compiled/worked fine. Two that interacted with
>> Views a
>> > > lot
>> > > > > had
>> > > > > > lots of compile errors, but in the end I don't think there's a
>> good
>> > > way
>> > > > > to
>> > > > > > fix them on our end.
>> > > > > >
>> > > > > > I've also taken some time to try and eliminate copy & paste
>> between
>> > > > > > AndroidWebView and XWalkWebView. I'd love to get some feedback
>> on
>> > the
>> > > > > > changes (and hopefully get them in). More info /w PRs here:
>> > > > > >
>> > > > > > https://issues.apache.org/jira/browse/CB-8510
>> > > > > >
>> > > > > > Another thing that came out of looking at these plugins is that
>> > they
>> > > > add
>> > > > > in
>> > > > > > their own Layout, or have logic to handle various parent layout.
>> > > So...
>> > > > I
>> > > > > > think we'd be fine (and should) delete our top-level
>> LinearLayout.
>> > > > > Plugins
>> > > > > > and embedders can easily add in layouts if they want.
>> > > > > >
>> > > > > > Still waiting on a tools release for 3.7.1.
>> > > > > > Still need to update platform docs for 4.0.0
>> > > > > >
>> > > > > > But... I think that's it! (unless I'm missing something)
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > On Wed, Feb 4, 2015 at 10:11 PM, Ian Clelland <
>> > > iclelland@chromium.org>
>> > > > > > wrote:
>> > > > > >
>> > > > > > > On Wed, Feb 4, 2015 at 7:58 PM, Fu, Junwei <
>> junwei.fu@intel.com>
>> > > > > wrote:
>> > > > > > >
>> > > > > > > > What are the test cases don't work for Crosswalk? I'd like
>> to
>> > do
>> > > > > > whatever
>> > > > > > > > I can to help.
>> > > > > > > >
>> > > > > > >
>> > > > > > > So, Crosswalk 10 (and, I believe, 11) work great for Cordova.
>> > There
>> > > > is
>> > > > > a
>> > > > > > > failing test in File Transfer, though, that appears to be a
>> > > threading
>> > > > > > issue
>> > > > > > > causing a NPE deep inside of OkHTTP.
>> > > > > > >
>> > > > > > > It's very similar to a bug we solved almost a year ago:
>> > > > > > > https://issues.apache.org/jira/browse/CB-6378, except that
>> it's
>> > > > > > happening
>> > > > > > > in a different method, and while the last time, the cause was
>> > > obvious
>> > > > > > > (connections opened on one thread, and closed on another),
>> this
>> > > time
>> > > > > > > everything *should* be happening on the same thread.
>> > > > > > >
>> > > > > > > I've just created
>> https://issues.apache.org/jira/browse/CB-8431
>> > if
>> > > > you
>> > > > > > > want
>> > > > > > > to take a look. I haven't had the chance to really dig into
>> where
>> > > the
>> > > > > > error
>> > > > > > > is coming from yet, but I'll take a closer look tomorrow.
>> > > > > > >
>> > > > > > > Ian
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > >
>> > > > > > > > -----Original Message-----
>> > > > > > > > From: agrieve@google.com [mailto:agrieve@google.com] On
>> Behalf
>> > > Of
>> > > > > > Andrew
>> > > > > > > > Grieve
>> > > > > > > > Sent: Thursday, February 05, 2015 3:43 AM
>> > > > > > > > To: dev
>> > > > > > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
>> > > > > > > >
>> > > > > > > > On Wed, Feb 4, 2015 at 2:25 PM, Joe Bowser <
>> bowserj@gmail.com>
>> > > > > wrote:
>> > > > > > > >
>> > > > > > > > > OK, so since we're using e-mail to do a sprint, here's
>> where
>> > I
>> > > > > think
>> > > > > > > > > we're at so far.
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > - Ian's been working on getting crosswalk 10 working and
>> is
>> > > > hitting
>> > > > > > > > > some FileTransfer crash issues.
>> > > > > > > > > (Apparently Crosswalk-11 works? Ian, what's happening with
>> > > this?)
>> > > > > > > > > - Mobilespec really should be passing, let's investigate
>> and
>> > > fix
>> > > > > > > > > plugins / tests if they are the issues.
>> > > > > > > > >
>> > > > > > > > > Has anyone done this yet?
>> > > > > > > > >
>> > > > > > > > Don't think so.
>> > > > > > > >
>> > > > > > > > >
>> > > > > > > > > - Android's update script is not preserving artifacts of
>> > > > <framework
>> > > > > > > > > type="gradleReference"/> (hoping to work on this today)
>> > > > > > > > >
>> > > > > > > > > Did you get around to doing this?
>> > > > > > > > >
>> > > > > > > > Done!
>> > > > > > > >
>> > > > > > > > >
>> > > > > > > > > - *LinearLayoutSoftKeyboardDetect - delete it!*
>> > > > > > > > >
>> > > > > > > > > It's apparently already gone on Master.
>> > > > > > > > >
>> > > > > > > > Done!
>> > > > > > > >
>> > > > > > > > >
>> > > > > > > > > - Ensure that our gradle support is to the point where
>> > plugins
>> > > > can
>> > > > > > > > > target android-sdk-provided libs (play services & -compat
>> > libs)
>> > > > > > > > >
>> > > > > > > > > What needs to be done here? Is there a JIRA issue for
>> this?
>> > > > > > > > >
>> > > > > > > > Done! Needs a tools release.
>> > > > > > > > Haven't tested how bad the error messages are if you don't
>> have
>> > > > them
>> > > > > > > > installed though. That seems like a can-be-done-after thing
>> > (e.g.
>> > > > If
>> > > > > > the
>> > > > > > > > error message sucks, we could: before build, pre-scan for
>> > > existence
>> > > > > of
>> > > > > > > them
>> > > > > > > > in the SDK directly.)
>> > > > > > > >
>> > > > > > > > >
>> > > > > > > > > - Make CordovaActivity not implement CordovaInterface, but
>> > > > instead
>> > > > > > > > > provide CordovaInterface via an inner class (to solidify
>> that
>> > > you
>> > > > > > > > > can't cast the activity to CordovaInterface and expect
>> that
>> > to
>> > > > > work -
>> > > > > > > > > some used to do this but I think we've cleaned it all up
>> now)
>> > > > > > > > >
>> > > > > > > > done!
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > >
>> > > > > > > > > I know there's a vote pending for 3.7.1, and we still need
>> > > people
>> > > > > to
>> > > > > > > > > vote on that (I'll get around to it before the voting
>> period
>> > > > ends),
>> > > > > > > > > but I'm wondering how close we are to getting a 4.0.0 vote
>> > > > > happening?
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > > I'd like to do a bit more work with playing with third party
>> > > > plugins
>> > > > > in
>> > > > > > > > mobilespec before we vote to release. Right now many of them
>> > > don't
>> > > > > > > compile,
>> > > > > > > > and I think the main reason is that CordovaWebView is not a
>> > view.
>> > > > > > > Planning
>> > > > > > > > on writing up a report of how many popular plugins break,
>> and
>> > how
>> > > > bad
>> > > > > > it
>> > > > > > > is
>> > > > > > > > to fix them.
>> > > > > > > >
>> > > > > > > > Also need to update embedder's guide in docs (maybe create
>> an
>> > > > > > > android-4.0.0
>> > > > > > > > branch?)
>> > > > > > > > Also need to do a plugins release for splashscreen (will
>> start
>> > > > > > shortly).
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > On Tue Feb 03 2015 at 7:20:29 PM Fu, Junwei <
>> > > junwei.fu@intel.com
>> > > > >
>> > > > > > > wrote:
>> > > > > > > > >
>> > > > > > > > > > Crosswalk engine have been tested in mobile-spec and
>> owned
>> > > > > > > > > > functionality tests with Crosswalk-11, and it was our
>> plan
>> > to
>> > > > be
>> > > > > > > > > > released. I request a PR in here
>> > > > > > > > > > https://github.com/MobileChromeApps/cordova-
>> > > > > > > > > > crosswalk-engine/pull/17.
>> > > > > > > > > >
>> > > > > > > > > > Thanks,
>> > > > > > > > > > Junwei.
>> > > > > > > > > >
>> > > > > > > > > > -----Original Message-----
>> > > > > > > > > > From: agrieve@google.com [mailto:agrieve@google.com] On
>> > > Behalf
>> > > > > Of
>> > > > > > > > > > Andrew Grieve
>> > > > > > > > > > Sent: Wednesday, February 04, 2015 3:53 AM
>> > > > > > > > > > To: dev
>> > > > > > > > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
>> > > > > > > > > >
>> > > > > > > > > > And, of course, for your FileTransfer change :P
>> > > > > > > > > >
>> > > > > > > > > > I just last night finished up the fixing of <framework
>> > > > > > custom=false>
>> > > > > > > > > > for gradle-based builds, so we're certainly nearing the
>> > > finish
>> > > > > line
>> > > > > > > > > > for 4.0.0 known issues.
>> > > > > > > > > >
>> > > > > > > > > > Of the list from before, only remaining are:
>> > > > > > > > > >
>> > > > > > > > > > - Ian's been working on getting crosswalk 10 working
>> and is
>> > > > > hitting
>> > > > > > > > > > some FileTransfer crash issues.
>> > > > > > > > > > - Mobilespec really should be passing, let's investigate
>> > and
>> > > > fix
>> > > > > > > > > > plugins
>> > > > > > > > > /
>> > > > > > > > > > tests if they are the issues.
>> > > > > > > > > >
>> > > > > > > > > >
>> > > > > > > > > >
>> > > > > > > > > >
>> > > > > > > > > > On Tue, Feb 3, 2015 at 2:46 PM, Darryl Pogue <
>> > > > > dvpdiner2@gmail.com>
>> > > > > > > > > wrote:
>> > > > > > > > > >
>> > > > > > > > > > > I just remembered that there should be a plugins
>> release
>> > > > before
>> > > > > > > > > > > Android 4.0.0 goes out because of the moving of the
>> > > > > splashscreen
>> > > > > > > > > > > logic out of the platform and into the plugin. As far
>> as
>> > I
>> > > > can
>> > > > > > > > > > > tell, that's still unreleased.
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > ------------------------------------------------------------
>> > > > > > ------
>> > > > > > > > > > > --- To unsubscribe, e-mail: dev-unsubscribe@cordova.
>> > > > apache.org
>> > > > > > > > > > > For additional commands, e-mail:
>> > > dev-help@cordova.apache.org
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > >
>> > > > > > > > > > ------------------------------
>> > ------------------------------
>> > > > > > --------
>> > > > > > > > > > - To unsubscribe, e-mail: dev-unsubscribe@cordova.
>> > apache.org
>> > > > > > > > > > For additional commands, e-mail:
>> > dev-help@cordova.apache.org
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Alright, branch is merged in and I fixed a couple other things I noticed
broken in the native test app (back button & background color). I've also
gone ahead with removing the LinearLayout and confirmed that both maps and
nativepagetransitions plugins are not affected at all.
Might as well add in the key signing tweaks that have been agreed upon. I
can do that today.
Would like your input on:
Deprecated show/hide customView
- At first I thought this was just view twiddling for video on old
androids that was not meant to be exposed
- I see now though that there is custom back button logic for it
- and that the maps plugin uses it to go fullscreen
- so I'm thinking let's not deprecate.
We're also still waiting for a tools release to happen that will set 3.7.1
as the default platform (don't have cycles to do it this week myself)
On Tue, Feb 24, 2015 at 7:39 PM, Joe Bowser <bo...@gmail.com> wrote:
> I can't come up with any. Let's not delay the release on that. So, other
> than the platform docs, we should be good to go, right?
>
> On Thu Feb 19 2015 at 11:42:40 AM Andrew Grieve <ag...@chromium.org>
> wrote:
>
> > Thanks for the quick review. I'll have a look through your comments.
> Now's
> > a good time to change names, so feel free to suggest alternatives.
> >
> > On Thu, Feb 19, 2015 at 1:32 PM, Joe Bowser <bo...@gmail.com> wrote:
> >
> > > I've done a quick read of the pull request and left some comments in
> > > there. I'm in Salt Lake this week, so I haven't had a chance to really
> > > test this pull request yet, but while I'm not in love with the naming
> > > convention used, it looks mostly OK.
> > >
> > > On Thu Feb 19 2015 at 11:19:51 AM Andrew Grieve <ag...@chromium.org>
> > > wrote:
> > >
> > > > They would need to do similar to the PR for xwalk. It's actually a
> lot
> > > less
> > > > code now to implement a custom engine, so I think it makes geckoview
> > much
> > > > more feasible.
> > > >
> > > > The embedded case (I'm guessing you mean layout xml?) is one of the
> > unit
> > > > tests. Have a look here:
> > > > https://github.com/agrieve/cordova-android/blob/engine/
> > > > test/src/org/apache/cordova/test/CordovaWebViewTestActivity.java
> > > >
> > > > If we delete LinearLayout, we just pass the WebView itself to
> > > > setContentView(). It will still have a FrameLayout as a parent (which
> > is
> > > > the unchangeable root View of all Activities)
> > > >
> > > > For reference, here's now NativePageTransitions inserts their own
> > Layout:
> > > > https://github.com/Telerik-Verified-Plugins/
> > NativePageTransitions/blob/
> > > > master/src/android/NativePageTransitions.java#L74
> > > >
> > > > On Thu, Feb 19, 2015 at 1:01 PM, Joe Bowser <bo...@gmail.com>
> wrote:
> > > >
> > > > > So, I know that XWalk is the only production-ready WebView right
> now,
> > > but
> > > > > what would other third party providers need to implement/change for
> > > their
> > > > > webviews to work? Also, I'm not clear how the embedded
> CordovaWebView
> > > use
> > > > > case would work in this scenario. If we delete the LinearLayout,
> > what
> > > do
> > > > > we attach our view for the default use case?
> > > > >
> > > > > On Thu Feb 19 2015 at 10:39:59 AM Andrew Grieve <
> > agrieve@chromium.org>
> > > > > wrote:
> > > > >
> > > > > > I've finished playing with third-party plugins. If anyone else
> > wants
> > > to
> > > > > > have fun with them, use --thirdpartyplugins in
> createmobilespec.js,
> > > and
> > > > > > then find the manual test for them.
> > > > > >
> > > > > > TLDR - most compiled/worked fine. Two that interacted with Views
> a
> > > lot
> > > > > had
> > > > > > lots of compile errors, but in the end I don't think there's a
> good
> > > way
> > > > > to
> > > > > > fix them on our end.
> > > > > >
> > > > > > I've also taken some time to try and eliminate copy & paste
> between
> > > > > > AndroidWebView and XWalkWebView. I'd love to get some feedback on
> > the
> > > > > > changes (and hopefully get them in). More info /w PRs here:
> > > > > >
> > > > > > https://issues.apache.org/jira/browse/CB-8510
> > > > > >
> > > > > > Another thing that came out of looking at these plugins is that
> > they
> > > > add
> > > > > in
> > > > > > their own Layout, or have logic to handle various parent layout.
> > > So...
> > > > I
> > > > > > think we'd be fine (and should) delete our top-level
> LinearLayout.
> > > > > Plugins
> > > > > > and embedders can easily add in layouts if they want.
> > > > > >
> > > > > > Still waiting on a tools release for 3.7.1.
> > > > > > Still need to update platform docs for 4.0.0
> > > > > >
> > > > > > But... I think that's it! (unless I'm missing something)
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Wed, Feb 4, 2015 at 10:11 PM, Ian Clelland <
> > > iclelland@chromium.org>
> > > > > > wrote:
> > > > > >
> > > > > > > On Wed, Feb 4, 2015 at 7:58 PM, Fu, Junwei <
> junwei.fu@intel.com>
> > > > > wrote:
> > > > > > >
> > > > > > > > What are the test cases don't work for Crosswalk? I'd like to
> > do
> > > > > > whatever
> > > > > > > > I can to help.
> > > > > > > >
> > > > > > >
> > > > > > > So, Crosswalk 10 (and, I believe, 11) work great for Cordova.
> > There
> > > > is
> > > > > a
> > > > > > > failing test in File Transfer, though, that appears to be a
> > > threading
> > > > > > issue
> > > > > > > causing a NPE deep inside of OkHTTP.
> > > > > > >
> > > > > > > It's very similar to a bug we solved almost a year ago:
> > > > > > > https://issues.apache.org/jira/browse/CB-6378, except that
> it's
> > > > > > happening
> > > > > > > in a different method, and while the last time, the cause was
> > > obvious
> > > > > > > (connections opened on one thread, and closed on another), this
> > > time
> > > > > > > everything *should* be happening on the same thread.
> > > > > > >
> > > > > > > I've just created
> https://issues.apache.org/jira/browse/CB-8431
> > if
> > > > you
> > > > > > > want
> > > > > > > to take a look. I haven't had the chance to really dig into
> where
> > > the
> > > > > > error
> > > > > > > is coming from yet, but I'll take a closer look tomorrow.
> > > > > > >
> > > > > > > Ian
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: agrieve@google.com [mailto:agrieve@google.com] On
> Behalf
> > > Of
> > > > > > Andrew
> > > > > > > > Grieve
> > > > > > > > Sent: Thursday, February 05, 2015 3:43 AM
> > > > > > > > To: dev
> > > > > > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > > > > > > >
> > > > > > > > On Wed, Feb 4, 2015 at 2:25 PM, Joe Bowser <
> bowserj@gmail.com>
> > > > > wrote:
> > > > > > > >
> > > > > > > > > OK, so since we're using e-mail to do a sprint, here's
> where
> > I
> > > > > think
> > > > > > > > > we're at so far.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > - Ian's been working on getting crosswalk 10 working and is
> > > > hitting
> > > > > > > > > some FileTransfer crash issues.
> > > > > > > > > (Apparently Crosswalk-11 works? Ian, what's happening with
> > > this?)
> > > > > > > > > - Mobilespec really should be passing, let's investigate
> and
> > > fix
> > > > > > > > > plugins / tests if they are the issues.
> > > > > > > > >
> > > > > > > > > Has anyone done this yet?
> > > > > > > > >
> > > > > > > > Don't think so.
> > > > > > > >
> > > > > > > > >
> > > > > > > > > - Android's update script is not preserving artifacts of
> > > > <framework
> > > > > > > > > type="gradleReference"/> (hoping to work on this today)
> > > > > > > > >
> > > > > > > > > Did you get around to doing this?
> > > > > > > > >
> > > > > > > > Done!
> > > > > > > >
> > > > > > > > >
> > > > > > > > > - *LinearLayoutSoftKeyboardDetect - delete it!*
> > > > > > > > >
> > > > > > > > > It's apparently already gone on Master.
> > > > > > > > >
> > > > > > > > Done!
> > > > > > > >
> > > > > > > > >
> > > > > > > > > - Ensure that our gradle support is to the point where
> > plugins
> > > > can
> > > > > > > > > target android-sdk-provided libs (play services & -compat
> > libs)
> > > > > > > > >
> > > > > > > > > What needs to be done here? Is there a JIRA issue for this?
> > > > > > > > >
> > > > > > > > Done! Needs a tools release.
> > > > > > > > Haven't tested how bad the error messages are if you don't
> have
> > > > them
> > > > > > > > installed though. That seems like a can-be-done-after thing
> > (e.g.
> > > > If
> > > > > > the
> > > > > > > > error message sucks, we could: before build, pre-scan for
> > > existence
> > > > > of
> > > > > > > them
> > > > > > > > in the SDK directly.)
> > > > > > > >
> > > > > > > > >
> > > > > > > > > - Make CordovaActivity not implement CordovaInterface, but
> > > > instead
> > > > > > > > > provide CordovaInterface via an inner class (to solidify
> that
> > > you
> > > > > > > > > can't cast the activity to CordovaInterface and expect that
> > to
> > > > > work -
> > > > > > > > > some used to do this but I think we've cleaned it all up
> now)
> > > > > > > > >
> > > > > > > > done!
> > > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > I know there's a vote pending for 3.7.1, and we still need
> > > people
> > > > > to
> > > > > > > > > vote on that (I'll get around to it before the voting
> period
> > > > ends),
> > > > > > > > > but I'm wondering how close we are to getting a 4.0.0 vote
> > > > > happening?
> > > > > > > > >
> > > > > > > >
> > > > > > > > I'd like to do a bit more work with playing with third party
> > > > plugins
> > > > > in
> > > > > > > > mobilespec before we vote to release. Right now many of them
> > > don't
> > > > > > > compile,
> > > > > > > > and I think the main reason is that CordovaWebView is not a
> > view.
> > > > > > > Planning
> > > > > > > > on writing up a report of how many popular plugins break, and
> > how
> > > > bad
> > > > > > it
> > > > > > > is
> > > > > > > > to fix them.
> > > > > > > >
> > > > > > > > Also need to update embedder's guide in docs (maybe create an
> > > > > > > android-4.0.0
> > > > > > > > branch?)
> > > > > > > > Also need to do a plugins release for splashscreen (will
> start
> > > > > > shortly).
> > > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Tue Feb 03 2015 at 7:20:29 PM Fu, Junwei <
> > > junwei.fu@intel.com
> > > > >
> > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Crosswalk engine have been tested in mobile-spec and
> owned
> > > > > > > > > > functionality tests with Crosswalk-11, and it was our
> plan
> > to
> > > > be
> > > > > > > > > > released. I request a PR in here
> > > > > > > > > > https://github.com/MobileChromeApps/cordova-
> > > > > > > > > > crosswalk-engine/pull/17.
> > > > > > > > > >
> > > > > > > > > > Thanks,
> > > > > > > > > > Junwei.
> > > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: agrieve@google.com [mailto:agrieve@google.com] On
> > > Behalf
> > > > > Of
> > > > > > > > > > Andrew Grieve
> > > > > > > > > > Sent: Wednesday, February 04, 2015 3:53 AM
> > > > > > > > > > To: dev
> > > > > > > > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > > > > > > > > >
> > > > > > > > > > And, of course, for your FileTransfer change :P
> > > > > > > > > >
> > > > > > > > > > I just last night finished up the fixing of <framework
> > > > > > custom=false>
> > > > > > > > > > for gradle-based builds, so we're certainly nearing the
> > > finish
> > > > > line
> > > > > > > > > > for 4.0.0 known issues.
> > > > > > > > > >
> > > > > > > > > > Of the list from before, only remaining are:
> > > > > > > > > >
> > > > > > > > > > - Ian's been working on getting crosswalk 10 working and
> is
> > > > > hitting
> > > > > > > > > > some FileTransfer crash issues.
> > > > > > > > > > - Mobilespec really should be passing, let's investigate
> > and
> > > > fix
> > > > > > > > > > plugins
> > > > > > > > > /
> > > > > > > > > > tests if they are the issues.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Tue, Feb 3, 2015 at 2:46 PM, Darryl Pogue <
> > > > > dvpdiner2@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > I just remembered that there should be a plugins
> release
> > > > before
> > > > > > > > > > > Android 4.0.0 goes out because of the moving of the
> > > > > splashscreen
> > > > > > > > > > > logic out of the platform and into the plugin. As far
> as
> > I
> > > > can
> > > > > > > > > > > tell, that's still unreleased.
> > > > > > > > > > >
> > > > > > > > > > >
> > > ------------------------------------------------------------
> > > > > > ------
> > > > > > > > > > > --- To unsubscribe, e-mail: dev-unsubscribe@cordova.
> > > > apache.org
> > > > > > > > > > > For additional commands, e-mail:
> > > dev-help@cordova.apache.org
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > ------------------------------
> > ------------------------------
> > > > > > --------
> > > > > > > > > > - To unsubscribe, e-mail: dev-unsubscribe@cordova.
> > apache.org
> > > > > > > > > > For additional commands, e-mail:
> > dev-help@cordova.apache.org
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Joe Bowser <bo...@gmail.com>.
I can't come up with any. Let's not delay the release on that. So, other
than the platform docs, we should be good to go, right?
On Thu Feb 19 2015 at 11:42:40 AM Andrew Grieve <ag...@chromium.org>
wrote:
> Thanks for the quick review. I'll have a look through your comments. Now's
> a good time to change names, so feel free to suggest alternatives.
>
> On Thu, Feb 19, 2015 at 1:32 PM, Joe Bowser <bo...@gmail.com> wrote:
>
> > I've done a quick read of the pull request and left some comments in
> > there. I'm in Salt Lake this week, so I haven't had a chance to really
> > test this pull request yet, but while I'm not in love with the naming
> > convention used, it looks mostly OK.
> >
> > On Thu Feb 19 2015 at 11:19:51 AM Andrew Grieve <ag...@chromium.org>
> > wrote:
> >
> > > They would need to do similar to the PR for xwalk. It's actually a lot
> > less
> > > code now to implement a custom engine, so I think it makes geckoview
> much
> > > more feasible.
> > >
> > > The embedded case (I'm guessing you mean layout xml?) is one of the
> unit
> > > tests. Have a look here:
> > > https://github.com/agrieve/cordova-android/blob/engine/
> > > test/src/org/apache/cordova/test/CordovaWebViewTestActivity.java
> > >
> > > If we delete LinearLayout, we just pass the WebView itself to
> > > setContentView(). It will still have a FrameLayout as a parent (which
> is
> > > the unchangeable root View of all Activities)
> > >
> > > For reference, here's now NativePageTransitions inserts their own
> Layout:
> > > https://github.com/Telerik-Verified-Plugins/
> NativePageTransitions/blob/
> > > master/src/android/NativePageTransitions.java#L74
> > >
> > > On Thu, Feb 19, 2015 at 1:01 PM, Joe Bowser <bo...@gmail.com> wrote:
> > >
> > > > So, I know that XWalk is the only production-ready WebView right now,
> > but
> > > > what would other third party providers need to implement/change for
> > their
> > > > webviews to work? Also, I'm not clear how the embedded CordovaWebView
> > use
> > > > case would work in this scenario. If we delete the LinearLayout,
> what
> > do
> > > > we attach our view for the default use case?
> > > >
> > > > On Thu Feb 19 2015 at 10:39:59 AM Andrew Grieve <
> agrieve@chromium.org>
> > > > wrote:
> > > >
> > > > > I've finished playing with third-party plugins. If anyone else
> wants
> > to
> > > > > have fun with them, use --thirdpartyplugins in createmobilespec.js,
> > and
> > > > > then find the manual test for them.
> > > > >
> > > > > TLDR - most compiled/worked fine. Two that interacted with Views a
> > lot
> > > > had
> > > > > lots of compile errors, but in the end I don't think there's a good
> > way
> > > > to
> > > > > fix them on our end.
> > > > >
> > > > > I've also taken some time to try and eliminate copy & paste between
> > > > > AndroidWebView and XWalkWebView. I'd love to get some feedback on
> the
> > > > > changes (and hopefully get them in). More info /w PRs here:
> > > > >
> > > > > https://issues.apache.org/jira/browse/CB-8510
> > > > >
> > > > > Another thing that came out of looking at these plugins is that
> they
> > > add
> > > > in
> > > > > their own Layout, or have logic to handle various parent layout.
> > So...
> > > I
> > > > > think we'd be fine (and should) delete our top-level LinearLayout.
> > > > Plugins
> > > > > and embedders can easily add in layouts if they want.
> > > > >
> > > > > Still waiting on a tools release for 3.7.1.
> > > > > Still need to update platform docs for 4.0.0
> > > > >
> > > > > But... I think that's it! (unless I'm missing something)
> > > > >
> > > > >
> > > > >
> > > > > On Wed, Feb 4, 2015 at 10:11 PM, Ian Clelland <
> > iclelland@chromium.org>
> > > > > wrote:
> > > > >
> > > > > > On Wed, Feb 4, 2015 at 7:58 PM, Fu, Junwei <ju...@intel.com>
> > > > wrote:
> > > > > >
> > > > > > > What are the test cases don't work for Crosswalk? I'd like to
> do
> > > > > whatever
> > > > > > > I can to help.
> > > > > > >
> > > > > >
> > > > > > So, Crosswalk 10 (and, I believe, 11) work great for Cordova.
> There
> > > is
> > > > a
> > > > > > failing test in File Transfer, though, that appears to be a
> > threading
> > > > > issue
> > > > > > causing a NPE deep inside of OkHTTP.
> > > > > >
> > > > > > It's very similar to a bug we solved almost a year ago:
> > > > > > https://issues.apache.org/jira/browse/CB-6378, except that it's
> > > > > happening
> > > > > > in a different method, and while the last time, the cause was
> > obvious
> > > > > > (connections opened on one thread, and closed on another), this
> > time
> > > > > > everything *should* be happening on the same thread.
> > > > > >
> > > > > > I've just created https://issues.apache.org/jira/browse/CB-8431
> if
> > > you
> > > > > > want
> > > > > > to take a look. I haven't had the chance to really dig into where
> > the
> > > > > error
> > > > > > is coming from yet, but I'll take a closer look tomorrow.
> > > > > >
> > > > > > Ian
> > > > > >
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: agrieve@google.com [mailto:agrieve@google.com] On Behalf
> > Of
> > > > > Andrew
> > > > > > > Grieve
> > > > > > > Sent: Thursday, February 05, 2015 3:43 AM
> > > > > > > To: dev
> > > > > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > > > > > >
> > > > > > > On Wed, Feb 4, 2015 at 2:25 PM, Joe Bowser <bo...@gmail.com>
> > > > wrote:
> > > > > > >
> > > > > > > > OK, so since we're using e-mail to do a sprint, here's where
> I
> > > > think
> > > > > > > > we're at so far.
> > > > > > > >
> > > > > > > >
> > > > > > > > - Ian's been working on getting crosswalk 10 working and is
> > > hitting
> > > > > > > > some FileTransfer crash issues.
> > > > > > > > (Apparently Crosswalk-11 works? Ian, what's happening with
> > this?)
> > > > > > > > - Mobilespec really should be passing, let's investigate and
> > fix
> > > > > > > > plugins / tests if they are the issues.
> > > > > > > >
> > > > > > > > Has anyone done this yet?
> > > > > > > >
> > > > > > > Don't think so.
> > > > > > >
> > > > > > > >
> > > > > > > > - Android's update script is not preserving artifacts of
> > > <framework
> > > > > > > > type="gradleReference"/> (hoping to work on this today)
> > > > > > > >
> > > > > > > > Did you get around to doing this?
> > > > > > > >
> > > > > > > Done!
> > > > > > >
> > > > > > > >
> > > > > > > > - *LinearLayoutSoftKeyboardDetect - delete it!*
> > > > > > > >
> > > > > > > > It's apparently already gone on Master.
> > > > > > > >
> > > > > > > Done!
> > > > > > >
> > > > > > > >
> > > > > > > > - Ensure that our gradle support is to the point where
> plugins
> > > can
> > > > > > > > target android-sdk-provided libs (play services & -compat
> libs)
> > > > > > > >
> > > > > > > > What needs to be done here? Is there a JIRA issue for this?
> > > > > > > >
> > > > > > > Done! Needs a tools release.
> > > > > > > Haven't tested how bad the error messages are if you don't have
> > > them
> > > > > > > installed though. That seems like a can-be-done-after thing
> (e.g.
> > > If
> > > > > the
> > > > > > > error message sucks, we could: before build, pre-scan for
> > existence
> > > > of
> > > > > > them
> > > > > > > in the SDK directly.)
> > > > > > >
> > > > > > > >
> > > > > > > > - Make CordovaActivity not implement CordovaInterface, but
> > > instead
> > > > > > > > provide CordovaInterface via an inner class (to solidify that
> > you
> > > > > > > > can't cast the activity to CordovaInterface and expect that
> to
> > > > work -
> > > > > > > > some used to do this but I think we've cleaned it all up now)
> > > > > > > >
> > > > > > > done!
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > I know there's a vote pending for 3.7.1, and we still need
> > people
> > > > to
> > > > > > > > vote on that (I'll get around to it before the voting period
> > > ends),
> > > > > > > > but I'm wondering how close we are to getting a 4.0.0 vote
> > > > happening?
> > > > > > > >
> > > > > > >
> > > > > > > I'd like to do a bit more work with playing with third party
> > > plugins
> > > > in
> > > > > > > mobilespec before we vote to release. Right now many of them
> > don't
> > > > > > compile,
> > > > > > > and I think the main reason is that CordovaWebView is not a
> view.
> > > > > > Planning
> > > > > > > on writing up a report of how many popular plugins break, and
> how
> > > bad
> > > > > it
> > > > > > is
> > > > > > > to fix them.
> > > > > > >
> > > > > > > Also need to update embedder's guide in docs (maybe create an
> > > > > > android-4.0.0
> > > > > > > branch?)
> > > > > > > Also need to do a plugins release for splashscreen (will start
> > > > > shortly).
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Tue Feb 03 2015 at 7:20:29 PM Fu, Junwei <
> > junwei.fu@intel.com
> > > >
> > > > > > wrote:
> > > > > > > >
> > > > > > > > > Crosswalk engine have been tested in mobile-spec and owned
> > > > > > > > > functionality tests with Crosswalk-11, and it was our plan
> to
> > > be
> > > > > > > > > released. I request a PR in here
> > > > > > > > > https://github.com/MobileChromeApps/cordova-
> > > > > > > > > crosswalk-engine/pull/17.
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > Junwei.
> > > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: agrieve@google.com [mailto:agrieve@google.com] On
> > Behalf
> > > > Of
> > > > > > > > > Andrew Grieve
> > > > > > > > > Sent: Wednesday, February 04, 2015 3:53 AM
> > > > > > > > > To: dev
> > > > > > > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > > > > > > > >
> > > > > > > > > And, of course, for your FileTransfer change :P
> > > > > > > > >
> > > > > > > > > I just last night finished up the fixing of <framework
> > > > > custom=false>
> > > > > > > > > for gradle-based builds, so we're certainly nearing the
> > finish
> > > > line
> > > > > > > > > for 4.0.0 known issues.
> > > > > > > > >
> > > > > > > > > Of the list from before, only remaining are:
> > > > > > > > >
> > > > > > > > > - Ian's been working on getting crosswalk 10 working and is
> > > > hitting
> > > > > > > > > some FileTransfer crash issues.
> > > > > > > > > - Mobilespec really should be passing, let's investigate
> and
> > > fix
> > > > > > > > > plugins
> > > > > > > > /
> > > > > > > > > tests if they are the issues.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Tue, Feb 3, 2015 at 2:46 PM, Darryl Pogue <
> > > > dvpdiner2@gmail.com>
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > I just remembered that there should be a plugins release
> > > before
> > > > > > > > > > Android 4.0.0 goes out because of the moving of the
> > > > splashscreen
> > > > > > > > > > logic out of the platform and into the plugin. As far as
> I
> > > can
> > > > > > > > > > tell, that's still unreleased.
> > > > > > > > > >
> > > > > > > > > >
> > ------------------------------------------------------------
> > > > > ------
> > > > > > > > > > --- To unsubscribe, e-mail: dev-unsubscribe@cordova.
> > > apache.org
> > > > > > > > > > For additional commands, e-mail:
> > dev-help@cordova.apache.org
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > ------------------------------
> ------------------------------
> > > > > --------
> > > > > > > > > - To unsubscribe, e-mail: dev-unsubscribe@cordova.
> apache.org
> > > > > > > > > For additional commands, e-mail:
> dev-help@cordova.apache.org
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Thanks for the quick review. I'll have a look through your comments. Now's
a good time to change names, so feel free to suggest alternatives.
On Thu, Feb 19, 2015 at 1:32 PM, Joe Bowser <bo...@gmail.com> wrote:
> I've done a quick read of the pull request and left some comments in
> there. I'm in Salt Lake this week, so I haven't had a chance to really
> test this pull request yet, but while I'm not in love with the naming
> convention used, it looks mostly OK.
>
> On Thu Feb 19 2015 at 11:19:51 AM Andrew Grieve <ag...@chromium.org>
> wrote:
>
> > They would need to do similar to the PR for xwalk. It's actually a lot
> less
> > code now to implement a custom engine, so I think it makes geckoview much
> > more feasible.
> >
> > The embedded case (I'm guessing you mean layout xml?) is one of the unit
> > tests. Have a look here:
> > https://github.com/agrieve/cordova-android/blob/engine/
> > test/src/org/apache/cordova/test/CordovaWebViewTestActivity.java
> >
> > If we delete LinearLayout, we just pass the WebView itself to
> > setContentView(). It will still have a FrameLayout as a parent (which is
> > the unchangeable root View of all Activities)
> >
> > For reference, here's now NativePageTransitions inserts their own Layout:
> > https://github.com/Telerik-Verified-Plugins/NativePageTransitions/blob/
> > master/src/android/NativePageTransitions.java#L74
> >
> > On Thu, Feb 19, 2015 at 1:01 PM, Joe Bowser <bo...@gmail.com> wrote:
> >
> > > So, I know that XWalk is the only production-ready WebView right now,
> but
> > > what would other third party providers need to implement/change for
> their
> > > webviews to work? Also, I'm not clear how the embedded CordovaWebView
> use
> > > case would work in this scenario. If we delete the LinearLayout, what
> do
> > > we attach our view for the default use case?
> > >
> > > On Thu Feb 19 2015 at 10:39:59 AM Andrew Grieve <ag...@chromium.org>
> > > wrote:
> > >
> > > > I've finished playing with third-party plugins. If anyone else wants
> to
> > > > have fun with them, use --thirdpartyplugins in createmobilespec.js,
> and
> > > > then find the manual test for them.
> > > >
> > > > TLDR - most compiled/worked fine. Two that interacted with Views a
> lot
> > > had
> > > > lots of compile errors, but in the end I don't think there's a good
> way
> > > to
> > > > fix them on our end.
> > > >
> > > > I've also taken some time to try and eliminate copy & paste between
> > > > AndroidWebView and XWalkWebView. I'd love to get some feedback on the
> > > > changes (and hopefully get them in). More info /w PRs here:
> > > >
> > > > https://issues.apache.org/jira/browse/CB-8510
> > > >
> > > > Another thing that came out of looking at these plugins is that they
> > add
> > > in
> > > > their own Layout, or have logic to handle various parent layout.
> So...
> > I
> > > > think we'd be fine (and should) delete our top-level LinearLayout.
> > > Plugins
> > > > and embedders can easily add in layouts if they want.
> > > >
> > > > Still waiting on a tools release for 3.7.1.
> > > > Still need to update platform docs for 4.0.0
> > > >
> > > > But... I think that's it! (unless I'm missing something)
> > > >
> > > >
> > > >
> > > > On Wed, Feb 4, 2015 at 10:11 PM, Ian Clelland <
> iclelland@chromium.org>
> > > > wrote:
> > > >
> > > > > On Wed, Feb 4, 2015 at 7:58 PM, Fu, Junwei <ju...@intel.com>
> > > wrote:
> > > > >
> > > > > > What are the test cases don't work for Crosswalk? I'd like to do
> > > > whatever
> > > > > > I can to help.
> > > > > >
> > > > >
> > > > > So, Crosswalk 10 (and, I believe, 11) work great for Cordova. There
> > is
> > > a
> > > > > failing test in File Transfer, though, that appears to be a
> threading
> > > > issue
> > > > > causing a NPE deep inside of OkHTTP.
> > > > >
> > > > > It's very similar to a bug we solved almost a year ago:
> > > > > https://issues.apache.org/jira/browse/CB-6378, except that it's
> > > > happening
> > > > > in a different method, and while the last time, the cause was
> obvious
> > > > > (connections opened on one thread, and closed on another), this
> time
> > > > > everything *should* be happening on the same thread.
> > > > >
> > > > > I've just created https://issues.apache.org/jira/browse/CB-8431 if
> > you
> > > > > want
> > > > > to take a look. I haven't had the chance to really dig into where
> the
> > > > error
> > > > > is coming from yet, but I'll take a closer look tomorrow.
> > > > >
> > > > > Ian
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: agrieve@google.com [mailto:agrieve@google.com] On Behalf
> Of
> > > > Andrew
> > > > > > Grieve
> > > > > > Sent: Thursday, February 05, 2015 3:43 AM
> > > > > > To: dev
> > > > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > > > > >
> > > > > > On Wed, Feb 4, 2015 at 2:25 PM, Joe Bowser <bo...@gmail.com>
> > > wrote:
> > > > > >
> > > > > > > OK, so since we're using e-mail to do a sprint, here's where I
> > > think
> > > > > > > we're at so far.
> > > > > > >
> > > > > > >
> > > > > > > - Ian's been working on getting crosswalk 10 working and is
> > hitting
> > > > > > > some FileTransfer crash issues.
> > > > > > > (Apparently Crosswalk-11 works? Ian, what's happening with
> this?)
> > > > > > > - Mobilespec really should be passing, let's investigate and
> fix
> > > > > > > plugins / tests if they are the issues.
> > > > > > >
> > > > > > > Has anyone done this yet?
> > > > > > >
> > > > > > Don't think so.
> > > > > >
> > > > > > >
> > > > > > > - Android's update script is not preserving artifacts of
> > <framework
> > > > > > > type="gradleReference"/> (hoping to work on this today)
> > > > > > >
> > > > > > > Did you get around to doing this?
> > > > > > >
> > > > > > Done!
> > > > > >
> > > > > > >
> > > > > > > - *LinearLayoutSoftKeyboardDetect - delete it!*
> > > > > > >
> > > > > > > It's apparently already gone on Master.
> > > > > > >
> > > > > > Done!
> > > > > >
> > > > > > >
> > > > > > > - Ensure that our gradle support is to the point where plugins
> > can
> > > > > > > target android-sdk-provided libs (play services & -compat libs)
> > > > > > >
> > > > > > > What needs to be done here? Is there a JIRA issue for this?
> > > > > > >
> > > > > > Done! Needs a tools release.
> > > > > > Haven't tested how bad the error messages are if you don't have
> > them
> > > > > > installed though. That seems like a can-be-done-after thing (e.g.
> > If
> > > > the
> > > > > > error message sucks, we could: before build, pre-scan for
> existence
> > > of
> > > > > them
> > > > > > in the SDK directly.)
> > > > > >
> > > > > > >
> > > > > > > - Make CordovaActivity not implement CordovaInterface, but
> > instead
> > > > > > > provide CordovaInterface via an inner class (to solidify that
> you
> > > > > > > can't cast the activity to CordovaInterface and expect that to
> > > work -
> > > > > > > some used to do this but I think we've cleaned it all up now)
> > > > > > >
> > > > > > done!
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > I know there's a vote pending for 3.7.1, and we still need
> people
> > > to
> > > > > > > vote on that (I'll get around to it before the voting period
> > ends),
> > > > > > > but I'm wondering how close we are to getting a 4.0.0 vote
> > > happening?
> > > > > > >
> > > > > >
> > > > > > I'd like to do a bit more work with playing with third party
> > plugins
> > > in
> > > > > > mobilespec before we vote to release. Right now many of them
> don't
> > > > > compile,
> > > > > > and I think the main reason is that CordovaWebView is not a view.
> > > > > Planning
> > > > > > on writing up a report of how many popular plugins break, and how
> > bad
> > > > it
> > > > > is
> > > > > > to fix them.
> > > > > >
> > > > > > Also need to update embedder's guide in docs (maybe create an
> > > > > android-4.0.0
> > > > > > branch?)
> > > > > > Also need to do a plugins release for splashscreen (will start
> > > > shortly).
> > > > > >
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Tue Feb 03 2015 at 7:20:29 PM Fu, Junwei <
> junwei.fu@intel.com
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > > Crosswalk engine have been tested in mobile-spec and owned
> > > > > > > > functionality tests with Crosswalk-11, and it was our plan to
> > be
> > > > > > > > released. I request a PR in here
> > > > > > > > https://github.com/MobileChromeApps/cordova-
> > > > > > > > crosswalk-engine/pull/17.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Junwei.
> > > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: agrieve@google.com [mailto:agrieve@google.com] On
> Behalf
> > > Of
> > > > > > > > Andrew Grieve
> > > > > > > > Sent: Wednesday, February 04, 2015 3:53 AM
> > > > > > > > To: dev
> > > > > > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > > > > > > >
> > > > > > > > And, of course, for your FileTransfer change :P
> > > > > > > >
> > > > > > > > I just last night finished up the fixing of <framework
> > > > custom=false>
> > > > > > > > for gradle-based builds, so we're certainly nearing the
> finish
> > > line
> > > > > > > > for 4.0.0 known issues.
> > > > > > > >
> > > > > > > > Of the list from before, only remaining are:
> > > > > > > >
> > > > > > > > - Ian's been working on getting crosswalk 10 working and is
> > > hitting
> > > > > > > > some FileTransfer crash issues.
> > > > > > > > - Mobilespec really should be passing, let's investigate and
> > fix
> > > > > > > > plugins
> > > > > > > /
> > > > > > > > tests if they are the issues.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Tue, Feb 3, 2015 at 2:46 PM, Darryl Pogue <
> > > dvpdiner2@gmail.com>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > > I just remembered that there should be a plugins release
> > before
> > > > > > > > > Android 4.0.0 goes out because of the moving of the
> > > splashscreen
> > > > > > > > > logic out of the platform and into the plugin. As far as I
> > can
> > > > > > > > > tell, that's still unreleased.
> > > > > > > > >
> > > > > > > > >
> ------------------------------------------------------------
> > > > ------
> > > > > > > > > --- To unsubscribe, e-mail: dev-unsubscribe@cordova.
> > apache.org
> > > > > > > > > For additional commands, e-mail:
> dev-help@cordova.apache.org
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > > ------------------------------------------------------------
> > > > --------
> > > > > > > > - To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > > > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Yes, did some no-op changes on master to make the PR diff smaller / more
readable. Are you saying some relate to existing JIRA issues, or that some
should make JIRA issues for? Not saying none are deserving of one, just
want to clarify what you're thinking.
On Thu, Feb 19, 2015 at 1:38 PM, Joe Bowser <bo...@gmail.com> wrote:
> Andrew, I noticed a bunch of commits done 3 hours ago that were added.
> They're minor, but some should have some record in JIRA. I know that JIRA
> is a mess, but since we've talked about the issues on the list, we should
> probably track them.
>
> On Thu Feb 19 2015 at 11:32:07 AM Joe Bowser <bo...@gmail.com> wrote:
>
> > I've done a quick read of the pull request and left some comments in
> > there. I'm in Salt Lake this week, so I haven't had a chance to really
> > test this pull request yet, but while I'm not in love with the naming
> > convention used, it looks mostly OK.
> >
> > On Thu Feb 19 2015 at 11:19:51 AM Andrew Grieve <ag...@chromium.org>
> > wrote:
> >
> >> They would need to do similar to the PR for xwalk. It's actually a lot
> >> less
> >> code now to implement a custom engine, so I think it makes geckoview
> much
> >> more feasible.
> >>
> >> The embedded case (I'm guessing you mean layout xml?) is one of the unit
> >> tests. Have a look here:
> >> https://github.com/agrieve/cordova-android/blob/engine/test/
> >> src/org/apache/cordova/test/CordovaWebViewTestActivity.java
> >>
> >> If we delete LinearLayout, we just pass the WebView itself to
> >> setContentView(). It will still have a FrameLayout as a parent (which is
> >> the unchangeable root View of all Activities)
> >>
> >> For reference, here's now NativePageTransitions inserts their own
> Layout:
> >> https://github.com/Telerik-Verified-Plugins/NativePageTransitions/blob/
> >> master/src/android/NativePageTransitions.java#L74
> >>
> >> On Thu, Feb 19, 2015 at 1:01 PM, Joe Bowser <bo...@gmail.com> wrote:
> >>
> >> > So, I know that XWalk is the only production-ready WebView right now,
> >> but
> >> > what would other third party providers need to implement/change for
> >> their
> >> > webviews to work? Also, I'm not clear how the embedded CordovaWebView
> >> use
> >> > case would work in this scenario. If we delete the LinearLayout, what
> >> do
> >> > we attach our view for the default use case?
> >> >
> >> > On Thu Feb 19 2015 at 10:39:59 AM Andrew Grieve <agrieve@chromium.org
> >
> >> > wrote:
> >> >
> >> > > I've finished playing with third-party plugins. If anyone else wants
> >> to
> >> > > have fun with them, use --thirdpartyplugins in createmobilespec.js,
> >> and
> >> > > then find the manual test for them.
> >> > >
> >> > > TLDR - most compiled/worked fine. Two that interacted with Views a
> lot
> >> > had
> >> > > lots of compile errors, but in the end I don't think there's a good
> >> way
> >> > to
> >> > > fix them on our end.
> >> > >
> >> > > I've also taken some time to try and eliminate copy & paste between
> >> > > AndroidWebView and XWalkWebView. I'd love to get some feedback on
> the
> >> > > changes (and hopefully get them in). More info /w PRs here:
> >> > >
> >> > > https://issues.apache.org/jira/browse/CB-8510
> >> > >
> >> > > Another thing that came out of looking at these plugins is that they
> >> add
> >> > in
> >> > > their own Layout, or have logic to handle various parent layout.
> >> So... I
> >> > > think we'd be fine (and should) delete our top-level LinearLayout.
> >> > Plugins
> >> > > and embedders can easily add in layouts if they want.
> >> > >
> >> > > Still waiting on a tools release for 3.7.1.
> >> > > Still need to update platform docs for 4.0.0
> >> > >
> >> > > But... I think that's it! (unless I'm missing something)
> >> > >
> >> > >
> >> > >
> >> > > On Wed, Feb 4, 2015 at 10:11 PM, Ian Clelland <
> iclelland@chromium.org
> >> >
> >> > > wrote:
> >> > >
> >> > > > On Wed, Feb 4, 2015 at 7:58 PM, Fu, Junwei <ju...@intel.com>
> >> > wrote:
> >> > > >
> >> > > > > What are the test cases don't work for Crosswalk? I'd like to do
> >> > > whatever
> >> > > > > I can to help.
> >> > > > >
> >> > > >
> >> > > > So, Crosswalk 10 (and, I believe, 11) work great for Cordova.
> There
> >> is
> >> > a
> >> > > > failing test in File Transfer, though, that appears to be a
> >> threading
> >> > > issue
> >> > > > causing a NPE deep inside of OkHTTP.
> >> > > >
> >> > > > It's very similar to a bug we solved almost a year ago:
> >> > > > https://issues.apache.org/jira/browse/CB-6378, except that it's
> >> > > happening
> >> > > > in a different method, and while the last time, the cause was
> >> obvious
> >> > > > (connections opened on one thread, and closed on another), this
> time
> >> > > > everything *should* be happening on the same thread.
> >> > > >
> >> > > > I've just created https://issues.apache.org/jira/browse/CB-8431
> if
> >> you
> >> > > > want
> >> > > > to take a look. I haven't had the chance to really dig into where
> >> the
> >> > > error
> >> > > > is coming from yet, but I'll take a closer look tomorrow.
> >> > > >
> >> > > > Ian
> >> > > >
> >> > > >
> >> > > >
> >> > > > >
> >> > > > > -----Original Message-----
> >> > > > > From: agrieve@google.com [mailto:agrieve@google.com] On Behalf
> Of
> >> > > Andrew
> >> > > > > Grieve
> >> > > > > Sent: Thursday, February 05, 2015 3:43 AM
> >> > > > > To: dev
> >> > > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> >> > > > >
> >> > > > > On Wed, Feb 4, 2015 at 2:25 PM, Joe Bowser <bo...@gmail.com>
> >> > wrote:
> >> > > > >
> >> > > > > > OK, so since we're using e-mail to do a sprint, here's where I
> >> > think
> >> > > > > > we're at so far.
> >> > > > > >
> >> > > > > >
> >> > > > > > - Ian's been working on getting crosswalk 10 working and is
> >> hitting
> >> > > > > > some FileTransfer crash issues.
> >> > > > > > (Apparently Crosswalk-11 works? Ian, what's happening with
> >> this?)
> >> > > > > > - Mobilespec really should be passing, let's investigate and
> fix
> >> > > > > > plugins / tests if they are the issues.
> >> > > > > >
> >> > > > > > Has anyone done this yet?
> >> > > > > >
> >> > > > > Don't think so.
> >> > > > >
> >> > > > > >
> >> > > > > > - Android's update script is not preserving artifacts of
> >> <framework
> >> > > > > > type="gradleReference"/> (hoping to work on this today)
> >> > > > > >
> >> > > > > > Did you get around to doing this?
> >> > > > > >
> >> > > > > Done!
> >> > > > >
> >> > > > > >
> >> > > > > > - *LinearLayoutSoftKeyboardDetect - delete it!*
> >> > > > > >
> >> > > > > > It's apparently already gone on Master.
> >> > > > > >
> >> > > > > Done!
> >> > > > >
> >> > > > > >
> >> > > > > > - Ensure that our gradle support is to the point where plugins
> >> can
> >> > > > > > target android-sdk-provided libs (play services & -compat
> libs)
> >> > > > > >
> >> > > > > > What needs to be done here? Is there a JIRA issue for this?
> >> > > > > >
> >> > > > > Done! Needs a tools release.
> >> > > > > Haven't tested how bad the error messages are if you don't have
> >> them
> >> > > > > installed though. That seems like a can-be-done-after thing
> (e.g.
> >> If
> >> > > the
> >> > > > > error message sucks, we could: before build, pre-scan for
> >> existence
> >> > of
> >> > > > them
> >> > > > > in the SDK directly.)
> >> > > > >
> >> > > > > >
> >> > > > > > - Make CordovaActivity not implement CordovaInterface, but
> >> instead
> >> > > > > > provide CordovaInterface via an inner class (to solidify that
> >> you
> >> > > > > > can't cast the activity to CordovaInterface and expect that to
> >> > work -
> >> > > > > > some used to do this but I think we've cleaned it all up now)
> >> > > > > >
> >> > > > > done!
> >> > > > >
> >> > > > >
> >> > > > > >
> >> > > > > > I know there's a vote pending for 3.7.1, and we still need
> >> people
> >> > to
> >> > > > > > vote on that (I'll get around to it before the voting period
> >> ends),
> >> > > > > > but I'm wondering how close we are to getting a 4.0.0 vote
> >> > happening?
> >> > > > > >
> >> > > > >
> >> > > > > I'd like to do a bit more work with playing with third party
> >> plugins
> >> > in
> >> > > > > mobilespec before we vote to release. Right now many of them
> don't
> >> > > > compile,
> >> > > > > and I think the main reason is that CordovaWebView is not a
> view.
> >> > > > Planning
> >> > > > > on writing up a report of how many popular plugins break, and
> how
> >> bad
> >> > > it
> >> > > > is
> >> > > > > to fix them.
> >> > > > >
> >> > > > > Also need to update embedder's guide in docs (maybe create an
> >> > > > android-4.0.0
> >> > > > > branch?)
> >> > > > > Also need to do a plugins release for splashscreen (will start
> >> > > shortly).
> >> > > > >
> >> > > > >
> >> > > > > >
> >> > > > > >
> >> > > > > >
> >> > > > > > On Tue Feb 03 2015 at 7:20:29 PM Fu, Junwei <
> >> junwei.fu@intel.com>
> >> > > > wrote:
> >> > > > > >
> >> > > > > > > Crosswalk engine have been tested in mobile-spec and owned
> >> > > > > > > functionality tests with Crosswalk-11, and it was our plan
> to
> >> be
> >> > > > > > > released. I request a PR in here
> >> > > > > > > https://github.com/MobileChromeApps/cordova-
> >> > > > > > > crosswalk-engine/pull/17.
> >> > > > > > >
> >> > > > > > > Thanks,
> >> > > > > > > Junwei.
> >> > > > > > >
> >> > > > > > > -----Original Message-----
> >> > > > > > > From: agrieve@google.com [mailto:agrieve@google.com] On
> >> Behalf
> >> > Of
> >> > > > > > > Andrew Grieve
> >> > > > > > > Sent: Wednesday, February 04, 2015 3:53 AM
> >> > > > > > > To: dev
> >> > > > > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> >> > > > > > >
> >> > > > > > > And, of course, for your FileTransfer change :P
> >> > > > > > >
> >> > > > > > > I just last night finished up the fixing of <framework
> >> > > custom=false>
> >> > > > > > > for gradle-based builds, so we're certainly nearing the
> finish
> >> > line
> >> > > > > > > for 4.0.0 known issues.
> >> > > > > > >
> >> > > > > > > Of the list from before, only remaining are:
> >> > > > > > >
> >> > > > > > > - Ian's been working on getting crosswalk 10 working and is
> >> > hitting
> >> > > > > > > some FileTransfer crash issues.
> >> > > > > > > - Mobilespec really should be passing, let's investigate and
> >> fix
> >> > > > > > > plugins
> >> > > > > > /
> >> > > > > > > tests if they are the issues.
> >> > > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > On Tue, Feb 3, 2015 at 2:46 PM, Darryl Pogue <
> >> > dvpdiner2@gmail.com>
> >> > > > > > wrote:
> >> > > > > > >
> >> > > > > > > > I just remembered that there should be a plugins release
> >> before
> >> > > > > > > > Android 4.0.0 goes out because of the moving of the
> >> > splashscreen
> >> > > > > > > > logic out of the platform and into the plugin. As far as I
> >> can
> >> > > > > > > > tell, that's still unreleased.
> >> > > > > > > >
> >> > > > > > > > ------------------------------
> >> ------------------------------
> >> > > ------
> >> > > > > > > > --- To unsubscribe, e-mail: dev-unsubscribe@cordova.apache
> >> .org
> >> > > > > > > > For additional commands, e-mail:
> >> dev-help@cordova.apache.org
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > > > ------------------------------------------------------------
> >> > > --------
> >> > > > > > > - To unsubscribe, e-mail:
> dev-unsubscribe@cordova.apache.org
> >> > > > > > > For additional commands, e-mail:
> dev-help@cordova.apache.org
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Joe Bowser <bo...@gmail.com>.
Andrew, I noticed a bunch of commits done 3 hours ago that were added.
They're minor, but some should have some record in JIRA. I know that JIRA
is a mess, but since we've talked about the issues on the list, we should
probably track them.
On Thu Feb 19 2015 at 11:32:07 AM Joe Bowser <bo...@gmail.com> wrote:
> I've done a quick read of the pull request and left some comments in
> there. I'm in Salt Lake this week, so I haven't had a chance to really
> test this pull request yet, but while I'm not in love with the naming
> convention used, it looks mostly OK.
>
> On Thu Feb 19 2015 at 11:19:51 AM Andrew Grieve <ag...@chromium.org>
> wrote:
>
>> They would need to do similar to the PR for xwalk. It's actually a lot
>> less
>> code now to implement a custom engine, so I think it makes geckoview much
>> more feasible.
>>
>> The embedded case (I'm guessing you mean layout xml?) is one of the unit
>> tests. Have a look here:
>> https://github.com/agrieve/cordova-android/blob/engine/test/
>> src/org/apache/cordova/test/CordovaWebViewTestActivity.java
>>
>> If we delete LinearLayout, we just pass the WebView itself to
>> setContentView(). It will still have a FrameLayout as a parent (which is
>> the unchangeable root View of all Activities)
>>
>> For reference, here's now NativePageTransitions inserts their own Layout:
>> https://github.com/Telerik-Verified-Plugins/NativePageTransitions/blob/
>> master/src/android/NativePageTransitions.java#L74
>>
>> On Thu, Feb 19, 2015 at 1:01 PM, Joe Bowser <bo...@gmail.com> wrote:
>>
>> > So, I know that XWalk is the only production-ready WebView right now,
>> but
>> > what would other third party providers need to implement/change for
>> their
>> > webviews to work? Also, I'm not clear how the embedded CordovaWebView
>> use
>> > case would work in this scenario. If we delete the LinearLayout, what
>> do
>> > we attach our view for the default use case?
>> >
>> > On Thu Feb 19 2015 at 10:39:59 AM Andrew Grieve <ag...@chromium.org>
>> > wrote:
>> >
>> > > I've finished playing with third-party plugins. If anyone else wants
>> to
>> > > have fun with them, use --thirdpartyplugins in createmobilespec.js,
>> and
>> > > then find the manual test for them.
>> > >
>> > > TLDR - most compiled/worked fine. Two that interacted with Views a lot
>> > had
>> > > lots of compile errors, but in the end I don't think there's a good
>> way
>> > to
>> > > fix them on our end.
>> > >
>> > > I've also taken some time to try and eliminate copy & paste between
>> > > AndroidWebView and XWalkWebView. I'd love to get some feedback on the
>> > > changes (and hopefully get them in). More info /w PRs here:
>> > >
>> > > https://issues.apache.org/jira/browse/CB-8510
>> > >
>> > > Another thing that came out of looking at these plugins is that they
>> add
>> > in
>> > > their own Layout, or have logic to handle various parent layout.
>> So... I
>> > > think we'd be fine (and should) delete our top-level LinearLayout.
>> > Plugins
>> > > and embedders can easily add in layouts if they want.
>> > >
>> > > Still waiting on a tools release for 3.7.1.
>> > > Still need to update platform docs for 4.0.0
>> > >
>> > > But... I think that's it! (unless I'm missing something)
>> > >
>> > >
>> > >
>> > > On Wed, Feb 4, 2015 at 10:11 PM, Ian Clelland <iclelland@chromium.org
>> >
>> > > wrote:
>> > >
>> > > > On Wed, Feb 4, 2015 at 7:58 PM, Fu, Junwei <ju...@intel.com>
>> > wrote:
>> > > >
>> > > > > What are the test cases don't work for Crosswalk? I'd like to do
>> > > whatever
>> > > > > I can to help.
>> > > > >
>> > > >
>> > > > So, Crosswalk 10 (and, I believe, 11) work great for Cordova. There
>> is
>> > a
>> > > > failing test in File Transfer, though, that appears to be a
>> threading
>> > > issue
>> > > > causing a NPE deep inside of OkHTTP.
>> > > >
>> > > > It's very similar to a bug we solved almost a year ago:
>> > > > https://issues.apache.org/jira/browse/CB-6378, except that it's
>> > > happening
>> > > > in a different method, and while the last time, the cause was
>> obvious
>> > > > (connections opened on one thread, and closed on another), this time
>> > > > everything *should* be happening on the same thread.
>> > > >
>> > > > I've just created https://issues.apache.org/jira/browse/CB-8431 if
>> you
>> > > > want
>> > > > to take a look. I haven't had the chance to really dig into where
>> the
>> > > error
>> > > > is coming from yet, but I'll take a closer look tomorrow.
>> > > >
>> > > > Ian
>> > > >
>> > > >
>> > > >
>> > > > >
>> > > > > -----Original Message-----
>> > > > > From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of
>> > > Andrew
>> > > > > Grieve
>> > > > > Sent: Thursday, February 05, 2015 3:43 AM
>> > > > > To: dev
>> > > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
>> > > > >
>> > > > > On Wed, Feb 4, 2015 at 2:25 PM, Joe Bowser <bo...@gmail.com>
>> > wrote:
>> > > > >
>> > > > > > OK, so since we're using e-mail to do a sprint, here's where I
>> > think
>> > > > > > we're at so far.
>> > > > > >
>> > > > > >
>> > > > > > - Ian's been working on getting crosswalk 10 working and is
>> hitting
>> > > > > > some FileTransfer crash issues.
>> > > > > > (Apparently Crosswalk-11 works? Ian, what's happening with
>> this?)
>> > > > > > - Mobilespec really should be passing, let's investigate and fix
>> > > > > > plugins / tests if they are the issues.
>> > > > > >
>> > > > > > Has anyone done this yet?
>> > > > > >
>> > > > > Don't think so.
>> > > > >
>> > > > > >
>> > > > > > - Android's update script is not preserving artifacts of
>> <framework
>> > > > > > type="gradleReference"/> (hoping to work on this today)
>> > > > > >
>> > > > > > Did you get around to doing this?
>> > > > > >
>> > > > > Done!
>> > > > >
>> > > > > >
>> > > > > > - *LinearLayoutSoftKeyboardDetect - delete it!*
>> > > > > >
>> > > > > > It's apparently already gone on Master.
>> > > > > >
>> > > > > Done!
>> > > > >
>> > > > > >
>> > > > > > - Ensure that our gradle support is to the point where plugins
>> can
>> > > > > > target android-sdk-provided libs (play services & -compat libs)
>> > > > > >
>> > > > > > What needs to be done here? Is there a JIRA issue for this?
>> > > > > >
>> > > > > Done! Needs a tools release.
>> > > > > Haven't tested how bad the error messages are if you don't have
>> them
>> > > > > installed though. That seems like a can-be-done-after thing (e.g.
>> If
>> > > the
>> > > > > error message sucks, we could: before build, pre-scan for
>> existence
>> > of
>> > > > them
>> > > > > in the SDK directly.)
>> > > > >
>> > > > > >
>> > > > > > - Make CordovaActivity not implement CordovaInterface, but
>> instead
>> > > > > > provide CordovaInterface via an inner class (to solidify that
>> you
>> > > > > > can't cast the activity to CordovaInterface and expect that to
>> > work -
>> > > > > > some used to do this but I think we've cleaned it all up now)
>> > > > > >
>> > > > > done!
>> > > > >
>> > > > >
>> > > > > >
>> > > > > > I know there's a vote pending for 3.7.1, and we still need
>> people
>> > to
>> > > > > > vote on that (I'll get around to it before the voting period
>> ends),
>> > > > > > but I'm wondering how close we are to getting a 4.0.0 vote
>> > happening?
>> > > > > >
>> > > > >
>> > > > > I'd like to do a bit more work with playing with third party
>> plugins
>> > in
>> > > > > mobilespec before we vote to release. Right now many of them don't
>> > > > compile,
>> > > > > and I think the main reason is that CordovaWebView is not a view.
>> > > > Planning
>> > > > > on writing up a report of how many popular plugins break, and how
>> bad
>> > > it
>> > > > is
>> > > > > to fix them.
>> > > > >
>> > > > > Also need to update embedder's guide in docs (maybe create an
>> > > > android-4.0.0
>> > > > > branch?)
>> > > > > Also need to do a plugins release for splashscreen (will start
>> > > shortly).
>> > > > >
>> > > > >
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > On Tue Feb 03 2015 at 7:20:29 PM Fu, Junwei <
>> junwei.fu@intel.com>
>> > > > wrote:
>> > > > > >
>> > > > > > > Crosswalk engine have been tested in mobile-spec and owned
>> > > > > > > functionality tests with Crosswalk-11, and it was our plan to
>> be
>> > > > > > > released. I request a PR in here
>> > > > > > > https://github.com/MobileChromeApps/cordova-
>> > > > > > > crosswalk-engine/pull/17.
>> > > > > > >
>> > > > > > > Thanks,
>> > > > > > > Junwei.
>> > > > > > >
>> > > > > > > -----Original Message-----
>> > > > > > > From: agrieve@google.com [mailto:agrieve@google.com] On
>> Behalf
>> > Of
>> > > > > > > Andrew Grieve
>> > > > > > > Sent: Wednesday, February 04, 2015 3:53 AM
>> > > > > > > To: dev
>> > > > > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
>> > > > > > >
>> > > > > > > And, of course, for your FileTransfer change :P
>> > > > > > >
>> > > > > > > I just last night finished up the fixing of <framework
>> > > custom=false>
>> > > > > > > for gradle-based builds, so we're certainly nearing the finish
>> > line
>> > > > > > > for 4.0.0 known issues.
>> > > > > > >
>> > > > > > > Of the list from before, only remaining are:
>> > > > > > >
>> > > > > > > - Ian's been working on getting crosswalk 10 working and is
>> > hitting
>> > > > > > > some FileTransfer crash issues.
>> > > > > > > - Mobilespec really should be passing, let's investigate and
>> fix
>> > > > > > > plugins
>> > > > > > /
>> > > > > > > tests if they are the issues.
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > On Tue, Feb 3, 2015 at 2:46 PM, Darryl Pogue <
>> > dvpdiner2@gmail.com>
>> > > > > > wrote:
>> > > > > > >
>> > > > > > > > I just remembered that there should be a plugins release
>> before
>> > > > > > > > Android 4.0.0 goes out because of the moving of the
>> > splashscreen
>> > > > > > > > logic out of the platform and into the plugin. As far as I
>> can
>> > > > > > > > tell, that's still unreleased.
>> > > > > > > >
>> > > > > > > > ------------------------------
>> ------------------------------
>> > > ------
>> > > > > > > > --- To unsubscribe, e-mail: dev-unsubscribe@cordova.apache
>> .org
>> > > > > > > > For additional commands, e-mail:
>> dev-help@cordova.apache.org
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > > > ------------------------------------------------------------
>> > > --------
>> > > > > > > - To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> > > > > > > For additional commands, e-mail: dev-help@cordova.apache.org
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Joe Bowser <bo...@gmail.com>.
I've done a quick read of the pull request and left some comments in
there. I'm in Salt Lake this week, so I haven't had a chance to really
test this pull request yet, but while I'm not in love with the naming
convention used, it looks mostly OK.
On Thu Feb 19 2015 at 11:19:51 AM Andrew Grieve <ag...@chromium.org>
wrote:
> They would need to do similar to the PR for xwalk. It's actually a lot less
> code now to implement a custom engine, so I think it makes geckoview much
> more feasible.
>
> The embedded case (I'm guessing you mean layout xml?) is one of the unit
> tests. Have a look here:
> https://github.com/agrieve/cordova-android/blob/engine/
> test/src/org/apache/cordova/test/CordovaWebViewTestActivity.java
>
> If we delete LinearLayout, we just pass the WebView itself to
> setContentView(). It will still have a FrameLayout as a parent (which is
> the unchangeable root View of all Activities)
>
> For reference, here's now NativePageTransitions inserts their own Layout:
> https://github.com/Telerik-Verified-Plugins/NativePageTransitions/blob/
> master/src/android/NativePageTransitions.java#L74
>
> On Thu, Feb 19, 2015 at 1:01 PM, Joe Bowser <bo...@gmail.com> wrote:
>
> > So, I know that XWalk is the only production-ready WebView right now, but
> > what would other third party providers need to implement/change for their
> > webviews to work? Also, I'm not clear how the embedded CordovaWebView use
> > case would work in this scenario. If we delete the LinearLayout, what do
> > we attach our view for the default use case?
> >
> > On Thu Feb 19 2015 at 10:39:59 AM Andrew Grieve <ag...@chromium.org>
> > wrote:
> >
> > > I've finished playing with third-party plugins. If anyone else wants to
> > > have fun with them, use --thirdpartyplugins in createmobilespec.js, and
> > > then find the manual test for them.
> > >
> > > TLDR - most compiled/worked fine. Two that interacted with Views a lot
> > had
> > > lots of compile errors, but in the end I don't think there's a good way
> > to
> > > fix them on our end.
> > >
> > > I've also taken some time to try and eliminate copy & paste between
> > > AndroidWebView and XWalkWebView. I'd love to get some feedback on the
> > > changes (and hopefully get them in). More info /w PRs here:
> > >
> > > https://issues.apache.org/jira/browse/CB-8510
> > >
> > > Another thing that came out of looking at these plugins is that they
> add
> > in
> > > their own Layout, or have logic to handle various parent layout. So...
> I
> > > think we'd be fine (and should) delete our top-level LinearLayout.
> > Plugins
> > > and embedders can easily add in layouts if they want.
> > >
> > > Still waiting on a tools release for 3.7.1.
> > > Still need to update platform docs for 4.0.0
> > >
> > > But... I think that's it! (unless I'm missing something)
> > >
> > >
> > >
> > > On Wed, Feb 4, 2015 at 10:11 PM, Ian Clelland <ic...@chromium.org>
> > > wrote:
> > >
> > > > On Wed, Feb 4, 2015 at 7:58 PM, Fu, Junwei <ju...@intel.com>
> > wrote:
> > > >
> > > > > What are the test cases don't work for Crosswalk? I'd like to do
> > > whatever
> > > > > I can to help.
> > > > >
> > > >
> > > > So, Crosswalk 10 (and, I believe, 11) work great for Cordova. There
> is
> > a
> > > > failing test in File Transfer, though, that appears to be a threading
> > > issue
> > > > causing a NPE deep inside of OkHTTP.
> > > >
> > > > It's very similar to a bug we solved almost a year ago:
> > > > https://issues.apache.org/jira/browse/CB-6378, except that it's
> > > happening
> > > > in a different method, and while the last time, the cause was obvious
> > > > (connections opened on one thread, and closed on another), this time
> > > > everything *should* be happening on the same thread.
> > > >
> > > > I've just created https://issues.apache.org/jira/browse/CB-8431 if
> you
> > > > want
> > > > to take a look. I haven't had the chance to really dig into where the
> > > error
> > > > is coming from yet, but I'll take a closer look tomorrow.
> > > >
> > > > Ian
> > > >
> > > >
> > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of
> > > Andrew
> > > > > Grieve
> > > > > Sent: Thursday, February 05, 2015 3:43 AM
> > > > > To: dev
> > > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > > > >
> > > > > On Wed, Feb 4, 2015 at 2:25 PM, Joe Bowser <bo...@gmail.com>
> > wrote:
> > > > >
> > > > > > OK, so since we're using e-mail to do a sprint, here's where I
> > think
> > > > > > we're at so far.
> > > > > >
> > > > > >
> > > > > > - Ian's been working on getting crosswalk 10 working and is
> hitting
> > > > > > some FileTransfer crash issues.
> > > > > > (Apparently Crosswalk-11 works? Ian, what's happening with this?)
> > > > > > - Mobilespec really should be passing, let's investigate and fix
> > > > > > plugins / tests if they are the issues.
> > > > > >
> > > > > > Has anyone done this yet?
> > > > > >
> > > > > Don't think so.
> > > > >
> > > > > >
> > > > > > - Android's update script is not preserving artifacts of
> <framework
> > > > > > type="gradleReference"/> (hoping to work on this today)
> > > > > >
> > > > > > Did you get around to doing this?
> > > > > >
> > > > > Done!
> > > > >
> > > > > >
> > > > > > - *LinearLayoutSoftKeyboardDetect - delete it!*
> > > > > >
> > > > > > It's apparently already gone on Master.
> > > > > >
> > > > > Done!
> > > > >
> > > > > >
> > > > > > - Ensure that our gradle support is to the point where plugins
> can
> > > > > > target android-sdk-provided libs (play services & -compat libs)
> > > > > >
> > > > > > What needs to be done here? Is there a JIRA issue for this?
> > > > > >
> > > > > Done! Needs a tools release.
> > > > > Haven't tested how bad the error messages are if you don't have
> them
> > > > > installed though. That seems like a can-be-done-after thing (e.g.
> If
> > > the
> > > > > error message sucks, we could: before build, pre-scan for existence
> > of
> > > > them
> > > > > in the SDK directly.)
> > > > >
> > > > > >
> > > > > > - Make CordovaActivity not implement CordovaInterface, but
> instead
> > > > > > provide CordovaInterface via an inner class (to solidify that you
> > > > > > can't cast the activity to CordovaInterface and expect that to
> > work -
> > > > > > some used to do this but I think we've cleaned it all up now)
> > > > > >
> > > > > done!
> > > > >
> > > > >
> > > > > >
> > > > > > I know there's a vote pending for 3.7.1, and we still need people
> > to
> > > > > > vote on that (I'll get around to it before the voting period
> ends),
> > > > > > but I'm wondering how close we are to getting a 4.0.0 vote
> > happening?
> > > > > >
> > > > >
> > > > > I'd like to do a bit more work with playing with third party
> plugins
> > in
> > > > > mobilespec before we vote to release. Right now many of them don't
> > > > compile,
> > > > > and I think the main reason is that CordovaWebView is not a view.
> > > > Planning
> > > > > on writing up a report of how many popular plugins break, and how
> bad
> > > it
> > > > is
> > > > > to fix them.
> > > > >
> > > > > Also need to update embedder's guide in docs (maybe create an
> > > > android-4.0.0
> > > > > branch?)
> > > > > Also need to do a plugins release for splashscreen (will start
> > > shortly).
> > > > >
> > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Tue Feb 03 2015 at 7:20:29 PM Fu, Junwei <junwei.fu@intel.com
> >
> > > > wrote:
> > > > > >
> > > > > > > Crosswalk engine have been tested in mobile-spec and owned
> > > > > > > functionality tests with Crosswalk-11, and it was our plan to
> be
> > > > > > > released. I request a PR in here
> > > > > > > https://github.com/MobileChromeApps/cordova-
> > > > > > > crosswalk-engine/pull/17.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Junwei.
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: agrieve@google.com [mailto:agrieve@google.com] On Behalf
> > Of
> > > > > > > Andrew Grieve
> > > > > > > Sent: Wednesday, February 04, 2015 3:53 AM
> > > > > > > To: dev
> > > > > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > > > > > >
> > > > > > > And, of course, for your FileTransfer change :P
> > > > > > >
> > > > > > > I just last night finished up the fixing of <framework
> > > custom=false>
> > > > > > > for gradle-based builds, so we're certainly nearing the finish
> > line
> > > > > > > for 4.0.0 known issues.
> > > > > > >
> > > > > > > Of the list from before, only remaining are:
> > > > > > >
> > > > > > > - Ian's been working on getting crosswalk 10 working and is
> > hitting
> > > > > > > some FileTransfer crash issues.
> > > > > > > - Mobilespec really should be passing, let's investigate and
> fix
> > > > > > > plugins
> > > > > > /
> > > > > > > tests if they are the issues.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Tue, Feb 3, 2015 at 2:46 PM, Darryl Pogue <
> > dvpdiner2@gmail.com>
> > > > > > wrote:
> > > > > > >
> > > > > > > > I just remembered that there should be a plugins release
> before
> > > > > > > > Android 4.0.0 goes out because of the moving of the
> > splashscreen
> > > > > > > > logic out of the platform and into the plugin. As far as I
> can
> > > > > > > > tell, that's still unreleased.
> > > > > > > >
> > > > > > > > ------------------------------------------------------------
> > > ------
> > > > > > > > --- To unsubscribe, e-mail: dev-unsubscribe@cordova.
> apache.org
> > > > > > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > > ------------------------------------------------------------
> > > --------
> > > > > > > - To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Andrew Grieve <ag...@chromium.org>.
They would need to do similar to the PR for xwalk. It's actually a lot less
code now to implement a custom engine, so I think it makes geckoview much
more feasible.
The embedded case (I'm guessing you mean layout xml?) is one of the unit
tests. Have a look here:
https://github.com/agrieve/cordova-android/blob/engine/test/src/org/apache/cordova/test/CordovaWebViewTestActivity.java
If we delete LinearLayout, we just pass the WebView itself to
setContentView(). It will still have a FrameLayout as a parent (which is
the unchangeable root View of all Activities)
For reference, here's now NativePageTransitions inserts their own Layout:
https://github.com/Telerik-Verified-Plugins/NativePageTransitions/blob/master/src/android/NativePageTransitions.java#L74
On Thu, Feb 19, 2015 at 1:01 PM, Joe Bowser <bo...@gmail.com> wrote:
> So, I know that XWalk is the only production-ready WebView right now, but
> what would other third party providers need to implement/change for their
> webviews to work? Also, I'm not clear how the embedded CordovaWebView use
> case would work in this scenario. If we delete the LinearLayout, what do
> we attach our view for the default use case?
>
> On Thu Feb 19 2015 at 10:39:59 AM Andrew Grieve <ag...@chromium.org>
> wrote:
>
> > I've finished playing with third-party plugins. If anyone else wants to
> > have fun with them, use --thirdpartyplugins in createmobilespec.js, and
> > then find the manual test for them.
> >
> > TLDR - most compiled/worked fine. Two that interacted with Views a lot
> had
> > lots of compile errors, but in the end I don't think there's a good way
> to
> > fix them on our end.
> >
> > I've also taken some time to try and eliminate copy & paste between
> > AndroidWebView and XWalkWebView. I'd love to get some feedback on the
> > changes (and hopefully get them in). More info /w PRs here:
> >
> > https://issues.apache.org/jira/browse/CB-8510
> >
> > Another thing that came out of looking at these plugins is that they add
> in
> > their own Layout, or have logic to handle various parent layout. So... I
> > think we'd be fine (and should) delete our top-level LinearLayout.
> Plugins
> > and embedders can easily add in layouts if they want.
> >
> > Still waiting on a tools release for 3.7.1.
> > Still need to update platform docs for 4.0.0
> >
> > But... I think that's it! (unless I'm missing something)
> >
> >
> >
> > On Wed, Feb 4, 2015 at 10:11 PM, Ian Clelland <ic...@chromium.org>
> > wrote:
> >
> > > On Wed, Feb 4, 2015 at 7:58 PM, Fu, Junwei <ju...@intel.com>
> wrote:
> > >
> > > > What are the test cases don't work for Crosswalk? I'd like to do
> > whatever
> > > > I can to help.
> > > >
> > >
> > > So, Crosswalk 10 (and, I believe, 11) work great for Cordova. There is
> a
> > > failing test in File Transfer, though, that appears to be a threading
> > issue
> > > causing a NPE deep inside of OkHTTP.
> > >
> > > It's very similar to a bug we solved almost a year ago:
> > > https://issues.apache.org/jira/browse/CB-6378, except that it's
> > happening
> > > in a different method, and while the last time, the cause was obvious
> > > (connections opened on one thread, and closed on another), this time
> > > everything *should* be happening on the same thread.
> > >
> > > I've just created https://issues.apache.org/jira/browse/CB-8431 if you
> > > want
> > > to take a look. I haven't had the chance to really dig into where the
> > error
> > > is coming from yet, but I'll take a closer look tomorrow.
> > >
> > > Ian
> > >
> > >
> > >
> > > >
> > > > -----Original Message-----
> > > > From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of
> > Andrew
> > > > Grieve
> > > > Sent: Thursday, February 05, 2015 3:43 AM
> > > > To: dev
> > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > > >
> > > > On Wed, Feb 4, 2015 at 2:25 PM, Joe Bowser <bo...@gmail.com>
> wrote:
> > > >
> > > > > OK, so since we're using e-mail to do a sprint, here's where I
> think
> > > > > we're at so far.
> > > > >
> > > > >
> > > > > - Ian's been working on getting crosswalk 10 working and is hitting
> > > > > some FileTransfer crash issues.
> > > > > (Apparently Crosswalk-11 works? Ian, what's happening with this?)
> > > > > - Mobilespec really should be passing, let's investigate and fix
> > > > > plugins / tests if they are the issues.
> > > > >
> > > > > Has anyone done this yet?
> > > > >
> > > > Don't think so.
> > > >
> > > > >
> > > > > - Android's update script is not preserving artifacts of <framework
> > > > > type="gradleReference"/> (hoping to work on this today)
> > > > >
> > > > > Did you get around to doing this?
> > > > >
> > > > Done!
> > > >
> > > > >
> > > > > - *LinearLayoutSoftKeyboardDetect - delete it!*
> > > > >
> > > > > It's apparently already gone on Master.
> > > > >
> > > > Done!
> > > >
> > > > >
> > > > > - Ensure that our gradle support is to the point where plugins can
> > > > > target android-sdk-provided libs (play services & -compat libs)
> > > > >
> > > > > What needs to be done here? Is there a JIRA issue for this?
> > > > >
> > > > Done! Needs a tools release.
> > > > Haven't tested how bad the error messages are if you don't have them
> > > > installed though. That seems like a can-be-done-after thing (e.g. If
> > the
> > > > error message sucks, we could: before build, pre-scan for existence
> of
> > > them
> > > > in the SDK directly.)
> > > >
> > > > >
> > > > > - Make CordovaActivity not implement CordovaInterface, but instead
> > > > > provide CordovaInterface via an inner class (to solidify that you
> > > > > can't cast the activity to CordovaInterface and expect that to
> work -
> > > > > some used to do this but I think we've cleaned it all up now)
> > > > >
> > > > done!
> > > >
> > > >
> > > > >
> > > > > I know there's a vote pending for 3.7.1, and we still need people
> to
> > > > > vote on that (I'll get around to it before the voting period ends),
> > > > > but I'm wondering how close we are to getting a 4.0.0 vote
> happening?
> > > > >
> > > >
> > > > I'd like to do a bit more work with playing with third party plugins
> in
> > > > mobilespec before we vote to release. Right now many of them don't
> > > compile,
> > > > and I think the main reason is that CordovaWebView is not a view.
> > > Planning
> > > > on writing up a report of how many popular plugins break, and how bad
> > it
> > > is
> > > > to fix them.
> > > >
> > > > Also need to update embedder's guide in docs (maybe create an
> > > android-4.0.0
> > > > branch?)
> > > > Also need to do a plugins release for splashscreen (will start
> > shortly).
> > > >
> > > >
> > > > >
> > > > >
> > > > >
> > > > > On Tue Feb 03 2015 at 7:20:29 PM Fu, Junwei <ju...@intel.com>
> > > wrote:
> > > > >
> > > > > > Crosswalk engine have been tested in mobile-spec and owned
> > > > > > functionality tests with Crosswalk-11, and it was our plan to be
> > > > > > released. I request a PR in here
> > > > > > https://github.com/MobileChromeApps/cordova-
> > > > > > crosswalk-engine/pull/17.
> > > > > >
> > > > > > Thanks,
> > > > > > Junwei.
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: agrieve@google.com [mailto:agrieve@google.com] On Behalf
> Of
> > > > > > Andrew Grieve
> > > > > > Sent: Wednesday, February 04, 2015 3:53 AM
> > > > > > To: dev
> > > > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > > > > >
> > > > > > And, of course, for your FileTransfer change :P
> > > > > >
> > > > > > I just last night finished up the fixing of <framework
> > custom=false>
> > > > > > for gradle-based builds, so we're certainly nearing the finish
> line
> > > > > > for 4.0.0 known issues.
> > > > > >
> > > > > > Of the list from before, only remaining are:
> > > > > >
> > > > > > - Ian's been working on getting crosswalk 10 working and is
> hitting
> > > > > > some FileTransfer crash issues.
> > > > > > - Mobilespec really should be passing, let's investigate and fix
> > > > > > plugins
> > > > > /
> > > > > > tests if they are the issues.
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Tue, Feb 3, 2015 at 2:46 PM, Darryl Pogue <
> dvpdiner2@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > > I just remembered that there should be a plugins release before
> > > > > > > Android 4.0.0 goes out because of the moving of the
> splashscreen
> > > > > > > logic out of the platform and into the plugin. As far as I can
> > > > > > > tell, that's still unreleased.
> > > > > > >
> > > > > > > ------------------------------------------------------------
> > ------
> > > > > > > --- To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > ------------------------------------------------------------
> > --------
> > > > > > - To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Joe Bowser <bo...@gmail.com>.
So, I know that XWalk is the only production-ready WebView right now, but
what would other third party providers need to implement/change for their
webviews to work? Also, I'm not clear how the embedded CordovaWebView use
case would work in this scenario. If we delete the LinearLayout, what do
we attach our view for the default use case?
On Thu Feb 19 2015 at 10:39:59 AM Andrew Grieve <ag...@chromium.org>
wrote:
> I've finished playing with third-party plugins. If anyone else wants to
> have fun with them, use --thirdpartyplugins in createmobilespec.js, and
> then find the manual test for them.
>
> TLDR - most compiled/worked fine. Two that interacted with Views a lot had
> lots of compile errors, but in the end I don't think there's a good way to
> fix them on our end.
>
> I've also taken some time to try and eliminate copy & paste between
> AndroidWebView and XWalkWebView. I'd love to get some feedback on the
> changes (and hopefully get them in). More info /w PRs here:
>
> https://issues.apache.org/jira/browse/CB-8510
>
> Another thing that came out of looking at these plugins is that they add in
> their own Layout, or have logic to handle various parent layout. So... I
> think we'd be fine (and should) delete our top-level LinearLayout. Plugins
> and embedders can easily add in layouts if they want.
>
> Still waiting on a tools release for 3.7.1.
> Still need to update platform docs for 4.0.0
>
> But... I think that's it! (unless I'm missing something)
>
>
>
> On Wed, Feb 4, 2015 at 10:11 PM, Ian Clelland <ic...@chromium.org>
> wrote:
>
> > On Wed, Feb 4, 2015 at 7:58 PM, Fu, Junwei <ju...@intel.com> wrote:
> >
> > > What are the test cases don't work for Crosswalk? I'd like to do
> whatever
> > > I can to help.
> > >
> >
> > So, Crosswalk 10 (and, I believe, 11) work great for Cordova. There is a
> > failing test in File Transfer, though, that appears to be a threading
> issue
> > causing a NPE deep inside of OkHTTP.
> >
> > It's very similar to a bug we solved almost a year ago:
> > https://issues.apache.org/jira/browse/CB-6378, except that it's
> happening
> > in a different method, and while the last time, the cause was obvious
> > (connections opened on one thread, and closed on another), this time
> > everything *should* be happening on the same thread.
> >
> > I've just created https://issues.apache.org/jira/browse/CB-8431 if you
> > want
> > to take a look. I haven't had the chance to really dig into where the
> error
> > is coming from yet, but I'll take a closer look tomorrow.
> >
> > Ian
> >
> >
> >
> > >
> > > -----Original Message-----
> > > From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of
> Andrew
> > > Grieve
> > > Sent: Thursday, February 05, 2015 3:43 AM
> > > To: dev
> > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > >
> > > On Wed, Feb 4, 2015 at 2:25 PM, Joe Bowser <bo...@gmail.com> wrote:
> > >
> > > > OK, so since we're using e-mail to do a sprint, here's where I think
> > > > we're at so far.
> > > >
> > > >
> > > > - Ian's been working on getting crosswalk 10 working and is hitting
> > > > some FileTransfer crash issues.
> > > > (Apparently Crosswalk-11 works? Ian, what's happening with this?)
> > > > - Mobilespec really should be passing, let's investigate and fix
> > > > plugins / tests if they are the issues.
> > > >
> > > > Has anyone done this yet?
> > > >
> > > Don't think so.
> > >
> > > >
> > > > - Android's update script is not preserving artifacts of <framework
> > > > type="gradleReference"/> (hoping to work on this today)
> > > >
> > > > Did you get around to doing this?
> > > >
> > > Done!
> > >
> > > >
> > > > - *LinearLayoutSoftKeyboardDetect - delete it!*
> > > >
> > > > It's apparently already gone on Master.
> > > >
> > > Done!
> > >
> > > >
> > > > - Ensure that our gradle support is to the point where plugins can
> > > > target android-sdk-provided libs (play services & -compat libs)
> > > >
> > > > What needs to be done here? Is there a JIRA issue for this?
> > > >
> > > Done! Needs a tools release.
> > > Haven't tested how bad the error messages are if you don't have them
> > > installed though. That seems like a can-be-done-after thing (e.g. If
> the
> > > error message sucks, we could: before build, pre-scan for existence of
> > them
> > > in the SDK directly.)
> > >
> > > >
> > > > - Make CordovaActivity not implement CordovaInterface, but instead
> > > > provide CordovaInterface via an inner class (to solidify that you
> > > > can't cast the activity to CordovaInterface and expect that to work -
> > > > some used to do this but I think we've cleaned it all up now)
> > > >
> > > done!
> > >
> > >
> > > >
> > > > I know there's a vote pending for 3.7.1, and we still need people to
> > > > vote on that (I'll get around to it before the voting period ends),
> > > > but I'm wondering how close we are to getting a 4.0.0 vote happening?
> > > >
> > >
> > > I'd like to do a bit more work with playing with third party plugins in
> > > mobilespec before we vote to release. Right now many of them don't
> > compile,
> > > and I think the main reason is that CordovaWebView is not a view.
> > Planning
> > > on writing up a report of how many popular plugins break, and how bad
> it
> > is
> > > to fix them.
> > >
> > > Also need to update embedder's guide in docs (maybe create an
> > android-4.0.0
> > > branch?)
> > > Also need to do a plugins release for splashscreen (will start
> shortly).
> > >
> > >
> > > >
> > > >
> > > >
> > > > On Tue Feb 03 2015 at 7:20:29 PM Fu, Junwei <ju...@intel.com>
> > wrote:
> > > >
> > > > > Crosswalk engine have been tested in mobile-spec and owned
> > > > > functionality tests with Crosswalk-11, and it was our plan to be
> > > > > released. I request a PR in here
> > > > > https://github.com/MobileChromeApps/cordova-
> > > > > crosswalk-engine/pull/17.
> > > > >
> > > > > Thanks,
> > > > > Junwei.
> > > > >
> > > > > -----Original Message-----
> > > > > From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of
> > > > > Andrew Grieve
> > > > > Sent: Wednesday, February 04, 2015 3:53 AM
> > > > > To: dev
> > > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > > > >
> > > > > And, of course, for your FileTransfer change :P
> > > > >
> > > > > I just last night finished up the fixing of <framework
> custom=false>
> > > > > for gradle-based builds, so we're certainly nearing the finish line
> > > > > for 4.0.0 known issues.
> > > > >
> > > > > Of the list from before, only remaining are:
> > > > >
> > > > > - Ian's been working on getting crosswalk 10 working and is hitting
> > > > > some FileTransfer crash issues.
> > > > > - Mobilespec really should be passing, let's investigate and fix
> > > > > plugins
> > > > /
> > > > > tests if they are the issues.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Tue, Feb 3, 2015 at 2:46 PM, Darryl Pogue <dv...@gmail.com>
> > > > wrote:
> > > > >
> > > > > > I just remembered that there should be a plugins release before
> > > > > > Android 4.0.0 goes out because of the moving of the splashscreen
> > > > > > logic out of the platform and into the plugin. As far as I can
> > > > > > tell, that's still unreleased.
> > > > > >
> > > > > > ------------------------------------------------------------
> ------
> > > > > > --- To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > > > >
> > > > > >
> > > > >
> > > > > ------------------------------------------------------------
> --------
> > > > > - To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Andrew Grieve <ag...@chromium.org>.
I've finished playing with third-party plugins. If anyone else wants to
have fun with them, use --thirdpartyplugins in createmobilespec.js, and
then find the manual test for them.
TLDR - most compiled/worked fine. Two that interacted with Views a lot had
lots of compile errors, but in the end I don't think there's a good way to
fix them on our end.
I've also taken some time to try and eliminate copy & paste between
AndroidWebView and XWalkWebView. I'd love to get some feedback on the
changes (and hopefully get them in). More info /w PRs here:
https://issues.apache.org/jira/browse/CB-8510
Another thing that came out of looking at these plugins is that they add in
their own Layout, or have logic to handle various parent layout. So... I
think we'd be fine (and should) delete our top-level LinearLayout. Plugins
and embedders can easily add in layouts if they want.
Still waiting on a tools release for 3.7.1.
Still need to update platform docs for 4.0.0
But... I think that's it! (unless I'm missing something)
On Wed, Feb 4, 2015 at 10:11 PM, Ian Clelland <ic...@chromium.org>
wrote:
> On Wed, Feb 4, 2015 at 7:58 PM, Fu, Junwei <ju...@intel.com> wrote:
>
> > What are the test cases don't work for Crosswalk? I'd like to do whatever
> > I can to help.
> >
>
> So, Crosswalk 10 (and, I believe, 11) work great for Cordova. There is a
> failing test in File Transfer, though, that appears to be a threading issue
> causing a NPE deep inside of OkHTTP.
>
> It's very similar to a bug we solved almost a year ago:
> https://issues.apache.org/jira/browse/CB-6378, except that it's happening
> in a different method, and while the last time, the cause was obvious
> (connections opened on one thread, and closed on another), this time
> everything *should* be happening on the same thread.
>
> I've just created https://issues.apache.org/jira/browse/CB-8431 if you
> want
> to take a look. I haven't had the chance to really dig into where the error
> is coming from yet, but I'll take a closer look tomorrow.
>
> Ian
>
>
>
> >
> > -----Original Message-----
> > From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of Andrew
> > Grieve
> > Sent: Thursday, February 05, 2015 3:43 AM
> > To: dev
> > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> >
> > On Wed, Feb 4, 2015 at 2:25 PM, Joe Bowser <bo...@gmail.com> wrote:
> >
> > > OK, so since we're using e-mail to do a sprint, here's where I think
> > > we're at so far.
> > >
> > >
> > > - Ian's been working on getting crosswalk 10 working and is hitting
> > > some FileTransfer crash issues.
> > > (Apparently Crosswalk-11 works? Ian, what's happening with this?)
> > > - Mobilespec really should be passing, let's investigate and fix
> > > plugins / tests if they are the issues.
> > >
> > > Has anyone done this yet?
> > >
> > Don't think so.
> >
> > >
> > > - Android's update script is not preserving artifacts of <framework
> > > type="gradleReference"/> (hoping to work on this today)
> > >
> > > Did you get around to doing this?
> > >
> > Done!
> >
> > >
> > > - *LinearLayoutSoftKeyboardDetect - delete it!*
> > >
> > > It's apparently already gone on Master.
> > >
> > Done!
> >
> > >
> > > - Ensure that our gradle support is to the point where plugins can
> > > target android-sdk-provided libs (play services & -compat libs)
> > >
> > > What needs to be done here? Is there a JIRA issue for this?
> > >
> > Done! Needs a tools release.
> > Haven't tested how bad the error messages are if you don't have them
> > installed though. That seems like a can-be-done-after thing (e.g. If the
> > error message sucks, we could: before build, pre-scan for existence of
> them
> > in the SDK directly.)
> >
> > >
> > > - Make CordovaActivity not implement CordovaInterface, but instead
> > > provide CordovaInterface via an inner class (to solidify that you
> > > can't cast the activity to CordovaInterface and expect that to work -
> > > some used to do this but I think we've cleaned it all up now)
> > >
> > done!
> >
> >
> > >
> > > I know there's a vote pending for 3.7.1, and we still need people to
> > > vote on that (I'll get around to it before the voting period ends),
> > > but I'm wondering how close we are to getting a 4.0.0 vote happening?
> > >
> >
> > I'd like to do a bit more work with playing with third party plugins in
> > mobilespec before we vote to release. Right now many of them don't
> compile,
> > and I think the main reason is that CordovaWebView is not a view.
> Planning
> > on writing up a report of how many popular plugins break, and how bad it
> is
> > to fix them.
> >
> > Also need to update embedder's guide in docs (maybe create an
> android-4.0.0
> > branch?)
> > Also need to do a plugins release for splashscreen (will start shortly).
> >
> >
> > >
> > >
> > >
> > > On Tue Feb 03 2015 at 7:20:29 PM Fu, Junwei <ju...@intel.com>
> wrote:
> > >
> > > > Crosswalk engine have been tested in mobile-spec and owned
> > > > functionality tests with Crosswalk-11, and it was our plan to be
> > > > released. I request a PR in here
> > > > https://github.com/MobileChromeApps/cordova-
> > > > crosswalk-engine/pull/17.
> > > >
> > > > Thanks,
> > > > Junwei.
> > > >
> > > > -----Original Message-----
> > > > From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of
> > > > Andrew Grieve
> > > > Sent: Wednesday, February 04, 2015 3:53 AM
> > > > To: dev
> > > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > > >
> > > > And, of course, for your FileTransfer change :P
> > > >
> > > > I just last night finished up the fixing of <framework custom=false>
> > > > for gradle-based builds, so we're certainly nearing the finish line
> > > > for 4.0.0 known issues.
> > > >
> > > > Of the list from before, only remaining are:
> > > >
> > > > - Ian's been working on getting crosswalk 10 working and is hitting
> > > > some FileTransfer crash issues.
> > > > - Mobilespec really should be passing, let's investigate and fix
> > > > plugins
> > > /
> > > > tests if they are the issues.
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, Feb 3, 2015 at 2:46 PM, Darryl Pogue <dv...@gmail.com>
> > > wrote:
> > > >
> > > > > I just remembered that there should be a plugins release before
> > > > > Android 4.0.0 goes out because of the moving of the splashscreen
> > > > > logic out of the platform and into the plugin. As far as I can
> > > > > tell, that's still unreleased.
> > > > >
> > > > > ------------------------------------------------------------------
> > > > > --- To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > > >
> > > > >
> > > >
> > > > --------------------------------------------------------------------
> > > > - To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > >
> > >
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Ian Clelland <ic...@chromium.org>.
On Wed, Feb 4, 2015 at 7:58 PM, Fu, Junwei <ju...@intel.com> wrote:
> What are the test cases don't work for Crosswalk? I'd like to do whatever
> I can to help.
>
So, Crosswalk 10 (and, I believe, 11) work great for Cordova. There is a
failing test in File Transfer, though, that appears to be a threading issue
causing a NPE deep inside of OkHTTP.
It's very similar to a bug we solved almost a year ago:
https://issues.apache.org/jira/browse/CB-6378, except that it's happening
in a different method, and while the last time, the cause was obvious
(connections opened on one thread, and closed on another), this time
everything *should* be happening on the same thread.
I've just created https://issues.apache.org/jira/browse/CB-8431 if you want
to take a look. I haven't had the chance to really dig into where the error
is coming from yet, but I'll take a closer look tomorrow.
Ian
>
> -----Original Message-----
> From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of Andrew
> Grieve
> Sent: Thursday, February 05, 2015 3:43 AM
> To: dev
> Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
>
> On Wed, Feb 4, 2015 at 2:25 PM, Joe Bowser <bo...@gmail.com> wrote:
>
> > OK, so since we're using e-mail to do a sprint, here's where I think
> > we're at so far.
> >
> >
> > - Ian's been working on getting crosswalk 10 working and is hitting
> > some FileTransfer crash issues.
> > (Apparently Crosswalk-11 works? Ian, what's happening with this?)
> > - Mobilespec really should be passing, let's investigate and fix
> > plugins / tests if they are the issues.
> >
> > Has anyone done this yet?
> >
> Don't think so.
>
> >
> > - Android's update script is not preserving artifacts of <framework
> > type="gradleReference"/> (hoping to work on this today)
> >
> > Did you get around to doing this?
> >
> Done!
>
> >
> > - *LinearLayoutSoftKeyboardDetect - delete it!*
> >
> > It's apparently already gone on Master.
> >
> Done!
>
> >
> > - Ensure that our gradle support is to the point where plugins can
> > target android-sdk-provided libs (play services & -compat libs)
> >
> > What needs to be done here? Is there a JIRA issue for this?
> >
> Done! Needs a tools release.
> Haven't tested how bad the error messages are if you don't have them
> installed though. That seems like a can-be-done-after thing (e.g. If the
> error message sucks, we could: before build, pre-scan for existence of them
> in the SDK directly.)
>
> >
> > - Make CordovaActivity not implement CordovaInterface, but instead
> > provide CordovaInterface via an inner class (to solidify that you
> > can't cast the activity to CordovaInterface and expect that to work -
> > some used to do this but I think we've cleaned it all up now)
> >
> done!
>
>
> >
> > I know there's a vote pending for 3.7.1, and we still need people to
> > vote on that (I'll get around to it before the voting period ends),
> > but I'm wondering how close we are to getting a 4.0.0 vote happening?
> >
>
> I'd like to do a bit more work with playing with third party plugins in
> mobilespec before we vote to release. Right now many of them don't compile,
> and I think the main reason is that CordovaWebView is not a view. Planning
> on writing up a report of how many popular plugins break, and how bad it is
> to fix them.
>
> Also need to update embedder's guide in docs (maybe create an android-4.0.0
> branch?)
> Also need to do a plugins release for splashscreen (will start shortly).
>
>
> >
> >
> >
> > On Tue Feb 03 2015 at 7:20:29 PM Fu, Junwei <ju...@intel.com> wrote:
> >
> > > Crosswalk engine have been tested in mobile-spec and owned
> > > functionality tests with Crosswalk-11, and it was our plan to be
> > > released. I request a PR in here
> > > https://github.com/MobileChromeApps/cordova-
> > > crosswalk-engine/pull/17.
> > >
> > > Thanks,
> > > Junwei.
> > >
> > > -----Original Message-----
> > > From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of
> > > Andrew Grieve
> > > Sent: Wednesday, February 04, 2015 3:53 AM
> > > To: dev
> > > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> > >
> > > And, of course, for your FileTransfer change :P
> > >
> > > I just last night finished up the fixing of <framework custom=false>
> > > for gradle-based builds, so we're certainly nearing the finish line
> > > for 4.0.0 known issues.
> > >
> > > Of the list from before, only remaining are:
> > >
> > > - Ian's been working on getting crosswalk 10 working and is hitting
> > > some FileTransfer crash issues.
> > > - Mobilespec really should be passing, let's investigate and fix
> > > plugins
> > /
> > > tests if they are the issues.
> > >
> > >
> > >
> > >
> > > On Tue, Feb 3, 2015 at 2:46 PM, Darryl Pogue <dv...@gmail.com>
> > wrote:
> > >
> > > > I just remembered that there should be a plugins release before
> > > > Android 4.0.0 goes out because of the moving of the splashscreen
> > > > logic out of the platform and into the plugin. As far as I can
> > > > tell, that's still unreleased.
> > > >
> > > > ------------------------------------------------------------------
> > > > --- To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > >
> > > >
> > >
> > > --------------------------------------------------------------------
> > > - To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > For additional commands, e-mail: dev-help@cordova.apache.org
> > >
> >
>
RE: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by "Fu, Junwei" <ju...@intel.com>.
What are the test cases don't work for Crosswalk? I'd like to do whatever I can to help.
-----Original Message-----
From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of Andrew Grieve
Sent: Thursday, February 05, 2015 3:43 AM
To: dev
Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
On Wed, Feb 4, 2015 at 2:25 PM, Joe Bowser <bo...@gmail.com> wrote:
> OK, so since we're using e-mail to do a sprint, here's where I think
> we're at so far.
>
>
> - Ian's been working on getting crosswalk 10 working and is hitting
> some FileTransfer crash issues.
> (Apparently Crosswalk-11 works? Ian, what's happening with this?)
> - Mobilespec really should be passing, let's investigate and fix
> plugins / tests if they are the issues.
>
> Has anyone done this yet?
>
Don't think so.
>
> - Android's update script is not preserving artifacts of <framework
> type="gradleReference"/> (hoping to work on this today)
>
> Did you get around to doing this?
>
Done!
>
> - *LinearLayoutSoftKeyboardDetect - delete it!*
>
> It's apparently already gone on Master.
>
Done!
>
> - Ensure that our gradle support is to the point where plugins can
> target android-sdk-provided libs (play services & -compat libs)
>
> What needs to be done here? Is there a JIRA issue for this?
>
Done! Needs a tools release.
Haven't tested how bad the error messages are if you don't have them installed though. That seems like a can-be-done-after thing (e.g. If the error message sucks, we could: before build, pre-scan for existence of them in the SDK directly.)
>
> - Make CordovaActivity not implement CordovaInterface, but instead
> provide CordovaInterface via an inner class (to solidify that you
> can't cast the activity to CordovaInterface and expect that to work -
> some used to do this but I think we've cleaned it all up now)
>
done!
>
> I know there's a vote pending for 3.7.1, and we still need people to
> vote on that (I'll get around to it before the voting period ends),
> but I'm wondering how close we are to getting a 4.0.0 vote happening?
>
I'd like to do a bit more work with playing with third party plugins in mobilespec before we vote to release. Right now many of them don't compile, and I think the main reason is that CordovaWebView is not a view. Planning on writing up a report of how many popular plugins break, and how bad it is to fix them.
Also need to update embedder's guide in docs (maybe create an android-4.0.0
branch?)
Also need to do a plugins release for splashscreen (will start shortly).
>
>
>
> On Tue Feb 03 2015 at 7:20:29 PM Fu, Junwei <ju...@intel.com> wrote:
>
> > Crosswalk engine have been tested in mobile-spec and owned
> > functionality tests with Crosswalk-11, and it was our plan to be
> > released. I request a PR in here
> > https://github.com/MobileChromeApps/cordova-
> > crosswalk-engine/pull/17.
> >
> > Thanks,
> > Junwei.
> >
> > -----Original Message-----
> > From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of
> > Andrew Grieve
> > Sent: Wednesday, February 04, 2015 3:53 AM
> > To: dev
> > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> >
> > And, of course, for your FileTransfer change :P
> >
> > I just last night finished up the fixing of <framework custom=false>
> > for gradle-based builds, so we're certainly nearing the finish line
> > for 4.0.0 known issues.
> >
> > Of the list from before, only remaining are:
> >
> > - Ian's been working on getting crosswalk 10 working and is hitting
> > some FileTransfer crash issues.
> > - Mobilespec really should be passing, let's investigate and fix
> > plugins
> /
> > tests if they are the issues.
> >
> >
> >
> >
> > On Tue, Feb 3, 2015 at 2:46 PM, Darryl Pogue <dv...@gmail.com>
> wrote:
> >
> > > I just remembered that there should be a plugins release before
> > > Android 4.0.0 goes out because of the moving of the splashscreen
> > > logic out of the platform and into the plugin. As far as I can
> > > tell, that's still unreleased.
> > >
> > > ------------------------------------------------------------------
> > > --- To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > For additional commands, e-mail: dev-help@cordova.apache.org
> > >
> > >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Andrew Grieve <ag...@chromium.org>.
On Wed, Feb 4, 2015 at 2:25 PM, Joe Bowser <bo...@gmail.com> wrote:
> OK, so since we're using e-mail to do a sprint, here's where I think we're
> at so far.
>
>
> - Ian's been working on getting crosswalk 10 working and is hitting some
> FileTransfer crash issues.
> (Apparently Crosswalk-11 works? Ian, what's happening with this?)
> - Mobilespec really should be passing, let's investigate and fix plugins /
> tests if they are the issues.
>
> Has anyone done this yet?
>
Don't think so.
>
> - Android's update script is not preserving artifacts of <framework
> type="gradleReference"/> (hoping to work on this today)
>
> Did you get around to doing this?
>
Done!
>
> - *LinearLayoutSoftKeyboardDetect - delete it!*
>
> It's apparently already gone on Master.
>
Done!
>
> - Ensure that our gradle support is to the point where plugins can target
> android-sdk-provided libs (play services & -compat libs)
>
> What needs to be done here? Is there a JIRA issue for this?
>
Done! Needs a tools release.
Haven't tested how bad the error messages are if you don't have them
installed though. That seems like a can-be-done-after thing (e.g. If the
error message sucks, we could: before build, pre-scan for existence of them
in the SDK directly.)
>
> - Make CordovaActivity not implement CordovaInterface, but instead provide
> CordovaInterface via an inner class (to solidify that you can't cast the
> activity to CordovaInterface and expect that to work - some used to do this
> but I think we've cleaned it all up now)
>
done!
>
> I know there's a vote pending for 3.7.1, and we still need people to vote
> on that (I'll get around to it before the voting period ends), but I'm
> wondering how close we are to getting a 4.0.0 vote happening?
>
I'd like to do a bit more work with playing with third party plugins in
mobilespec before we vote to release. Right now many of them don't compile,
and I think the main reason is that CordovaWebView is not a view. Planning
on writing up a report of how many popular plugins break, and how bad it is
to fix them.
Also need to update embedder's guide in docs (maybe create an android-4.0.0
branch?)
Also need to do a plugins release for splashscreen (will start shortly).
>
>
>
> On Tue Feb 03 2015 at 7:20:29 PM Fu, Junwei <ju...@intel.com> wrote:
>
> > Crosswalk engine have been tested in mobile-spec and owned functionality
> > tests with Crosswalk-11, and it was our plan to be released. I request a
> > PR in here https://github.com/MobileChromeApps/cordova-
> > crosswalk-engine/pull/17.
> >
> > Thanks,
> > Junwei.
> >
> > -----Original Message-----
> > From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of Andrew
> > Grieve
> > Sent: Wednesday, February 04, 2015 3:53 AM
> > To: dev
> > Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
> >
> > And, of course, for your FileTransfer change :P
> >
> > I just last night finished up the fixing of <framework custom=false> for
> > gradle-based builds, so we're certainly nearing the finish line for 4.0.0
> > known issues.
> >
> > Of the list from before, only remaining are:
> >
> > - Ian's been working on getting crosswalk 10 working and is hitting some
> > FileTransfer crash issues.
> > - Mobilespec really should be passing, let's investigate and fix plugins
> /
> > tests if they are the issues.
> >
> >
> >
> >
> > On Tue, Feb 3, 2015 at 2:46 PM, Darryl Pogue <dv...@gmail.com>
> wrote:
> >
> > > I just remembered that there should be a plugins release before
> > > Android 4.0.0 goes out because of the moving of the splashscreen logic
> > > out of the platform and into the plugin. As far as I can tell, that's
> > > still unreleased.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > For additional commands, e-mail: dev-help@cordova.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
>
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Joe Bowser <bo...@gmail.com>.
OK, so since we're using e-mail to do a sprint, here's where I think we're
at so far.
- Ian's been working on getting crosswalk 10 working and is hitting some
FileTransfer crash issues.
(Apparently Crosswalk-11 works? Ian, what's happening with this?)
- Mobilespec really should be passing, let's investigate and fix plugins /
tests if they are the issues.
Has anyone done this yet?
- Android's update script is not preserving artifacts of <framework
type="gradleReference"/> (hoping to work on this today)
Did you get around to doing this?
- *LinearLayoutSoftKeyboardDetect - delete it!*
It's apparently already gone on Master.
- Ensure that our gradle support is to the point where plugins can target
android-sdk-provided libs (play services & -compat libs)
What needs to be done here? Is there a JIRA issue for this?
- Make CordovaActivity not implement CordovaInterface, but instead provide
CordovaInterface via an inner class (to solidify that you can't cast the
activity to CordovaInterface and expect that to work - some used to do this
but I think we've cleaned it all up now)
I know there's a vote pending for 3.7.1, and we still need people to vote
on that (I'll get around to it before the voting period ends), but I'm
wondering how close we are to getting a 4.0.0 vote happening?
On Tue Feb 03 2015 at 7:20:29 PM Fu, Junwei <ju...@intel.com> wrote:
> Crosswalk engine have been tested in mobile-spec and owned functionality
> tests with Crosswalk-11, and it was our plan to be released. I request a
> PR in here https://github.com/MobileChromeApps/cordova-
> crosswalk-engine/pull/17.
>
> Thanks,
> Junwei.
>
> -----Original Message-----
> From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of Andrew
> Grieve
> Sent: Wednesday, February 04, 2015 3:53 AM
> To: dev
> Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
>
> And, of course, for your FileTransfer change :P
>
> I just last night finished up the fixing of <framework custom=false> for
> gradle-based builds, so we're certainly nearing the finish line for 4.0.0
> known issues.
>
> Of the list from before, only remaining are:
>
> - Ian's been working on getting crosswalk 10 working and is hitting some
> FileTransfer crash issues.
> - Mobilespec really should be passing, let's investigate and fix plugins /
> tests if they are the issues.
>
>
>
>
> On Tue, Feb 3, 2015 at 2:46 PM, Darryl Pogue <dv...@gmail.com> wrote:
>
> > I just remembered that there should be a plugins release before
> > Android 4.0.0 goes out because of the moving of the splashscreen logic
> > out of the platform and into the plugin. As far as I can tell, that's
> > still unreleased.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
RE: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by "Fu, Junwei" <ju...@intel.com>.
Crosswalk engine have been tested in mobile-spec and owned functionality tests with Crosswalk-11, and it was our plan to be released. I request a PR in here https://github.com/MobileChromeApps/cordova-crosswalk-engine/pull/17.
Thanks,
Junwei.
-----Original Message-----
From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of Andrew Grieve
Sent: Wednesday, February 04, 2015 3:53 AM
To: dev
Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
And, of course, for your FileTransfer change :P
I just last night finished up the fixing of <framework custom=false> for gradle-based builds, so we're certainly nearing the finish line for 4.0.0 known issues.
Of the list from before, only remaining are:
- Ian's been working on getting crosswalk 10 working and is hitting some FileTransfer crash issues.
- Mobilespec really should be passing, let's investigate and fix plugins / tests if they are the issues.
On Tue, Feb 3, 2015 at 2:46 PM, Darryl Pogue <dv...@gmail.com> wrote:
> I just remembered that there should be a plugins release before
> Android 4.0.0 goes out because of the moving of the splashscreen logic
> out of the platform and into the plugin. As far as I can tell, that's
> still unreleased.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: [DISCUSS] Cordova-Android 4.0.0 Release
Posted by Andrew Grieve <ag...@chromium.org>.
And, of course, for your FileTransfer change :P
I just last night finished up the fixing of <framework custom=false> for
gradle-based builds, so we're certainly nearing the finish line for 4.0.0
known issues.
Of the list from before, only remaining are:
- Ian's been working on getting crosswalk 10 working and is hitting some
FileTransfer crash issues.
- Mobilespec really should be passing, let's investigate and fix plugins /
tests if they are the issues.
On Tue, Feb 3, 2015 at 2:46 PM, Darryl Pogue <dv...@gmail.com> wrote:
> I just remembered that there should be a plugins release before
> Android 4.0.0 goes out because of the moving of the splashscreen logic
> out of the platform and into the plugin. As far as I can tell, that's
> still unreleased.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>