Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 735DC17C30 for ; Thu, 9 Apr 2015 02:09:08 +0000 (UTC) Received: (qmail 69637 invoked by uid 500); 9 Apr 2015 02:09:08 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 69597 invoked by uid 500); 9 Apr 2015 02:09:08 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 69583 invoked by uid 99); 9 Apr 2015 02:09:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Apr 2015 02:09:07 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of agrieve@google.com designates 209.85.213.173 as permitted sender) Received: from [209.85.213.173] (HELO mail-ig0-f173.google.com) (209.85.213.173) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Apr 2015 02:08:41 +0000 Received: by ignm3 with SMTP id m3so40501149ign.0 for ; Wed, 08 Apr 2015 19:07:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=nJfeBlKn8rXdABu+nvyd4tp1AbHKoY5B5p8Zummbs0o=; b=ff5v/w9FNFYdXP2GF8yUvTXs1lOQsfLKXPJLEn9nDUszLw/vjjqfoDLUpvpk/36Gb3 uWDMkcGNAgtl/qAoBtqDo9S77WHsD/UQ5MRGl1faH2uFvlHg3FDiQaimgjkheJqTGwXT 6/9ThBXeaPywvyrpi0TqNFy31vV1+r7VzM+29tBjYVJkCUwQE48FvomQo899+8pGA9Tc XXrySFPXtzTd2ExK9hFYl2vlJQsSfF5z11Q1YWEVOKRi2Wz+6R037M1I9kMBwoshOul4 zYnx5ms8s2hBfoXIBiLiziRCBXqsgLoRC/l+3WQzU0GFpYzVe1Z5kS6DAngh+1SHmWgW OzZg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=nJfeBlKn8rXdABu+nvyd4tp1AbHKoY5B5p8Zummbs0o=; b=K3Vp7J0AxtPtod8SrCCbjuhz8R4a47S/4Hma2gbicFi+s5i1/euE3xq5l4L+SalY9z C8E2B5gJ+BE8N219eL9jHt3/MkgikTFKMz0nNryr7D4wqfpL/hVeGVNuLerGQJLkrAoq aqybBTRl9YLiKhCt3JjAj7EmgBoYF+5dtxlc8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type; bh=nJfeBlKn8rXdABu+nvyd4tp1AbHKoY5B5p8Zummbs0o=; b=ZDrYnR0N1N1cT/mwdR10j6N2KvJJmFYrEJ0UCet2UU5IaSbcEAhxa57JtRUOnykCid NkpbWV/enyWceUMM+A9tPd9QHL1GwTG58Vo3OLarHWSb9gabYOE+6iyoDjinuAqoysC+ 4dS13D0dzRYzxoLch+EBzlNbxtHt6HJyM0v1H/JDv65bOTX61xyxoW0rKoByKVq5PAHp zyNQKBXfjc4lL8vkK14y7wcq9SvOCNdR4TobQPkxfgCKf0X/M4zKp8Jye5hJwp6G9Hgn K4pBm0UfcaMRf9mqRd199jrWmiRfwFZCqqT7Zlnn/VldCuLtOqJvBO6DvinrdXsJxaTO iDZA== X-Gm-Message-State: ALoCoQnQifuXlk2uZeHENa2M+041+0wPT/i5E1l/yB34BbeAOsM10oU/0/PfhmZ9r8a6qppWbpSl X-Received: by 10.42.129.73 with SMTP id p9mr20488933ics.48.1428545274672; Wed, 08 Apr 2015 19:07:54 -0700 (PDT) MIME-Version: 1.0 Sender: agrieve@google.com Received: by 10.36.3.14 with HTTP; Wed, 8 Apr 2015 19:07:34 -0700 (PDT) In-Reply-To: References: From: Andrew Grieve Date: Wed, 8 Apr 2015 22:07:34 -0400 X-Google-Sender-Auth: Idj2B1W63jjGX_yLvri8vVUUPHk Message-ID: Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release To: Andrew Grieve Cc: dev , "Homer, Tony" Content-Type: multipart/alternative; boundary=20cf301af6d9a49c730513411da6 X-Virus-Checked: Checked by ClamAV on apache.org --20cf301af6d9a49c730513411da6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 wrote: > I'll start on it once CB-8684 lands (Tony - assuming you'll have this don= e > shortly and would prefer it lands?) > > On Tue, Apr 7, 2015 at 1:33 PM, Jesse wrote: > >> Sweet! >> >> @purplecabbage >> risingj.com >> >> On Tue, Apr 7, 2015 at 8:35 AM, Andrew Grieve >> wrote: >> >> > Let's do it! >> > >> > On Mon, Apr 6, 2015 at 7:33 PM, Joe Bowser 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 shoul= d >> 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 votin= g >> on >> > an >> > > RC for this? What do people think? >> > > >> > > >> > > >> > > On Thu, Mar 19, 2015 at 10:31 AM Andrew Grieve >> > > 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 >> > > > > > name=3D"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, i= f >> > 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 >> > > > > > >> ). 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 b= e >> > > > awesome. >> > > > > > >> >> > > > > > >> On Mon, Mar 16, 2015 at 4:57 PM, Shazron >> > > 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 g= o >> 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 w= e >> > > 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 implementin= g >> 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=E2=80=99t think that thread closed with any conc= lusions. >> > > > > > >> > >> >> > > > > > >> > >> 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 (ak= a >> > > > > 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 poli= cy >> > 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 t= he >> > > > release, >> > > > > > >> it's >> > > > > > >> > >> > > us making sure that we've implemented the core hoo= ks >> > > > > 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 tha= t >> it >> > > > > compiles >> > > > > > >> on >> > > > > > >> > >> > > > > cordova-ios@3.8.0. It shouldn't be a problem t= o >> > 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 >> > > > > > >> > >> > > > > >> > > > > > >> > >> > > > 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 t= o >> > > > 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.or= g >> > > > > > >> > For additional commands, e-mail: >> dev-help@cordova.apache.org >> > > > > > >> > >> > > > > > >> > >> > > > > > >> >> > > > > > > >> > > > > > > >> > > > > > >> > > > > >> > > > > >> > > > > >> > > > > -- >> > > > > Carlos Santana >> > > > > >> > > > > >> > > > >> > > >> > >> > > --20cf301af6d9a49c730513411da6--